Skip to content

Control Center 2.0.2

This page describes the changes in Control Center since release 1.11.0.

Beginning with version 1.4.0, Docker images for Control Center are no longer available on Docker Hub. The images are included in self-installing archive files that you download from Virtana. Likewise, the RPM packages that installations and upgrades require are no longer available from internet repositories, and you must download them.

Downloads for Zenoss Service Dynamics customers are available on delivery.zenoss.io.

For more information about Control Center operating environments, see Tested operating environments.

Releases since 1.11.0

Release 2.0.2 is the first release in the 2.0.x series available for on-premises deployments. Releases 2.0.0 and 2.0.1 were not made available to on-premises customers. This page lists the cumulative set of changes across all three releases, so that you can see everything that changed between 1.11.0 and 2.0.2 in one place.

Release Date Availability
2.0.0 May 2026 Not released to on-premises customers
2.0.1 August 2026 Not released to on-premises customers
2.0.2 August 19, 2026 Available for on-premises deployments

The supported update path is from release 1.11.0 to release 2.0.2. For the procedure, see Updating Control Center to release 2.0.2.

Update considerations

Review the following items before you update. The update procedure includes steps that earlier Control Center updates didn't require.

  • Back up before you update: There's no downgrade path. Release 2.0.2 migrates the internal Docker registry forward and records it as migrated, and the internal data stores move forward with it. Returning to release 1.11.0 requires restoring a backup taken before the update.
  • Docker registry authentication: The internal Docker registry now requires a user name and password. You create a registry password file on the master host and log in to the registry on every host as part of the update. A host that isn't logged in can't download images, and the failure doesn't identify itself as an authentication problem.
  • Internal services image: The first start after the update pulls the serviced-isvcs:v76 image, which is approximately 2.2 GB. For an air-gapped installation, load the image from the offline installer before you start the update.
  • Package name: Zenoss Service Dynamics deployments install the serviced-zsd package. The serviced package is compiled for a newer Linux release and doesn't start on a ZSD host. Installing serviced-zsd satisfies other Zenoss packages that require serviced.
  • Repository metadata caching: The stable repository can serve cached metadata for a period after a release is published. If yum doesn't find release 2.0.2 immediately, retry after the cache expires.
  • Tested update path: Updates from 1.11.0 to 2.0.2 have been tested. Updates from earlier releases have not been tested. Update to 1.11.0 before updating to 2.0.2.

Historical Control Center metrics are deleted

Release 2.0.2 upgrades HBase from version 0.99.2 to version 2.6.4. The new version can't read data written by the old one, and nothing migrates it, so the update clears the embedded HBase data that stores Control Center internal metrics. Graphs for internal services start from an empty data set after the update, and metrics collected before the update can't be recovered. Application data is not affected.

Security fixes

The following security fixes are included in this release.

Issue ID Description
CC-4588 The internal Docker registry requires a user name and password. Earlier releases exposed the Docker Registry HTTP API v2 without authentication. Encrypting registry traffic remains optional and is controlled by the SERVICED_DOCKER_CERT_FILE and SERVICED_DOCKER_KEY_FILE variables.
CC-4590 The ElasticSearch and ELK components were updated to address reported vulnerabilities.
CC-4593 The HBase component was updated to address reported vulnerabilities.
CC-4616 The expired default TLS certificate was regenerated.
CC-4622 The Control Center REST API supports a read-only access level. A read-only session can run the v2 metrics query without gaining the ability to change state.
ZEN-35598 NFS exports are restricted to validated cluster hosts.

The following table lists the component versions before and after the update.

Component Release 1.11.0 Release 2.0.2
ElasticSearch and ELK 7.16.3 7.17.29
HBase 0.99.2 2.6.4

Fixed issues

The following issues were fixed in this release.

Issue ID Description
CC-4204 Delegate key and token file watches now retry and recover instead of failing silently, so a transient error no longer leaves a delegate unable to refresh its identity until you restart it.
CC-4539 Hosts in different resource pools that share a physical IP address no longer resolve to the wrong host, and valid IP assignments are no longer deleted during a read. Host registration also detects secondary network interfaces automatically.
CC-4573 The serviced host add-private command no longer drops the NAT IP address. The new serviced host set-nat command updates the NAT IP address of a registered host.
CC-4595 A public endpoint proxy that has no IP address configured no longer fails with an invalid TCP address error.
CC-4596 Services no longer remain in the stopping state and unstoppable from the command line or the browser interface.
CC-4613 An RPC pool slot leak was fixed, and health checks that previously reported only as unknown are now reported accurately.
CC-4614 serviced no longer stops responding when Docker sends duplicate container termination events.
CC-4624 HBase no longer fails to start when the hostname of the container resolves to a loopback address. This failure silently stopped metric collection and left graphs blank.
CC-4626 The serviced service status command reports actual RAM values instead of 0B for every instance.
CC-4628 The offline installer for air-gapped installations is built and published again.
ZEN-35577 HBase replication is disabled, which prevents unbounded growth of the oldWALs directory. Unchecked growth fills the DFS volume.

Improvements

The following changes are new in this release.

  • Memory statistics on cgroup v2 hosts: Control Center detects the cgroup version of the host at runtime and collects CPU and memory statistics correctly whether the host runs in cgroup v1 or cgroup v2 mode. Release 1.11.0 collected no statistics on hosts running in cgroup v2 mode (CC-4575 and CC-4617).

Known issues

The following known issues apply to this release.

  • Offline installer location: The offline installer for the internal services image is published under a delivery location named for Control Center 1.11.0 and Resource Manager 6.9, which predates the 2.0.x releases. Searching for a location named for release 2.0.2 doesn't find it.
  • Repository metadata caching: The stable repository can serve cached metadata for a period after publication. If yum doesn't find release 2.0.2, retry after the cache expires, or read the packages directly from the storage location.