Cisco CloudCenter Release Notes

Release Date

First Published: June 17, 2020


  • August 18, 2020: Updated the Documentation section to include modified pages.


CloudCenter is only available as an upgrade for existing customers from CloudCenter, CloudCenter, CloudCenter,  CloudCenter, CloudCenter, or CloudCenter Contact the CloudCenter Support team for additional details.

Upgrade Path

You must be at a minimum version of CloudCenter to upgrade to CloudCenter

Effective CloudCenter and later, the CloudCenter upgrade process downloads packages from a CentOS base and the extras repository via the internet. If you do not have internet connectivity, they must setup a local CentOS mirror and configure the CloudCenter components (CCM, CCO etc) to use the local mirror.

See the Upgrade Overview page and the following table for additional details. 

Upgrading CentOS CloudCenter Components to CloudCenter


Appliance Jar Files?Notes


Component? or earlierYesYes (for CCO only)YesYes (for CCO only)YesYesYou should have already run os_upgrade when you upgraded to or laterNoNoNoYesApplicable to CloudCenter or later
Upgrading Non-CentOS CloudCenter Components (RHEL) to CloudCenter or earlierNoNoNoYes

1 The os_upgrade command is not required when upgrading the REPO or Bundle store.


No updates


No updates

Applications and Services

The terminate behavior for non-VM tiers and VM tiers is different when compared to CloudCenter if you have set the cliqrIgnoreAppFailure flag to true.  

You must add the following variable to the /etc/sysconfig/gateway.conf file:

  • When set to false, then at the time of deployment termination the STOP script is implemented using a top-down approach – the top tier script is called followed by the dependent tier.

  • When set to true (default) the STOP scripts for all the tiers are called in parallel.

CloudCenter Management

No updates

Administration and Governance

No updates


No updates

End of Life Notices

See End of Support Notices for additional details.


The worker1 and worker_full modes are not supported effective CloudCenter The worker_basic mode is the only supported mode when installing the worker. 


No updates


No updates


No updates


The following documentation changes were implemented in Workload Manager

Known Issues

The following issue was identified in Workload Manager

At any time the number of users accessing a Job Details page should not exceed 30 users. Additional job details pages may not load completely if the number of users accessing Job Detail resources exceeds this number. 

Resolved Issues

The following issues were resolved/addressed in CloudCenter

  • CSCvu55475: A customer found the SDRS automation level for some VMs (VMs with multiple disks) had been disabled after attaching a volume from the CCM – this resulted in an enhancement request to  avoid changing the SDRS automation level for VMs. 
    Resolution: CloudCenter includes a fix to ensure that the SDRS automation level of the VM is preserved when an Attach Volume action is performed.

  • CSCvu51239: When creating a worker for RHEL6, Ubuntu 16, or CentOS 7 using the worker installer (worker-installer.bin, worker_basic mode), the gcc / nfs / bash / openssl / dialog / lsof packages are not installed with the worker. 
    : CloudCenter includes a fix to ensure that the gcc / nfs / bash / openssl / dialog / lsof packages are not installed with the worker installer and that rhel5 / centos5 / ubuntu10 / suse10 image mappings are not listed in the cloud region.

  • CSCvt83081: CloudCenter 4.9 does not assign proper tags to VM deployments that run on VMware 6.x. 
    Resolution: CloudCenter includes a fix to ensure that tags are assigned as designed to VM deployments that run on VMware 6.x.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks