CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Cisco CloudCenter Release Notes

Release Date

Release Date: May 29, 2018

Updated on:

  • May 31, 2018: Addressed screenshots display issue as identified in the Documentation section. Additionally, most pages continue to be updated as we work on our accessibility requirements.

  • June 6, 2018: Addressed the REPO/bundle component upgrade order and conditions and policy time zone details.

  • June 28, 2018: Added Docker service explicit re(start) as a known issue.

  • August 1, 2018: Added details on the Upgrade Path.

  • August 3, 2018: Added details on the security hardening requirements for CURL/WGET.

  • February 25, 2019: Clarified the process when configuring CCM on a FIPS System.


CloudCenter is available as installer files for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.

Upgrade Instructions

To upgrade to CloudCenter, see Upgrade Overview for additional context.

Upgrading to CloudCenter in HA Mode

When upgrading CCOs in HA mode, you MUST stop all the CCOs and then start them again. See Upgrade CCO for additional context.

Upgrade Path

The recommended upgrade path if you are using CloudCenter is to upgrade to CloudCenter 4.9.1.


No updates


No updates

Applications and Services

  • Deleting Additional Volumes at Deployment Time:

    • The number of additional volumes that was initially configured by the application owner can now be deleted by end users, if not required, at deployment time.

    • To delete the unwanted volume(s) click the delete icon next to that additional volume. 

    • See Application Tier Properties > General Settings for configuring additional volumes

    • See Multiple Volumes for configuring volume attributes.

    • See Deploying an Application for deployment details.

  • Special characters in the usrenv file:

    • In earlier releases, users were able to use special characters in the usrenv file. However, sourcing files with these special characters caused issues in scripts that used the usrenv file.

    • Effective CloudCenter, special characters like pipe or double quotes  " | " are configured with escape sequences that use single quotes instead of double quotes. This is a change!

    • An example:

      #CloudCenter 4.9.0 and earlier uses double quotes
      export nameOfVar = "ExampleABC"
      #CloudCenter and later uses single quotes
      export nameOfVar = 'ExampleABC'
    • You can successfully source userenv files that contain these special characters.

    • See Deployment Lifecycle Scripts for additional script sourcing details.

CloudCenter Management

No updates

Administration and Governance

No updates


Due to security hardening requirements, the following changes apply to application VMs (Worker):


  • If scripts in your application VMs require curl and/or wget, please install these utilities using your OS-specific package manager (apt-get/yum) in your application VM scripts. 

  • See CURL and WGET Utilities for additional details.

  • This is a change!

End of Life Notices

See End of Support Notices for additional details.


  • The Network menu item is removed from the CCM Wizard as it was not used for any configuration. See CCM Wizard for additional context.


  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.

  • Localization: See UI Behavior for additional context.


The Upload File API was introduced in CloudCenter 4.8.2 and recently documented as part of the File Management APIs.


The CloudCenter Jenkins plugin requires the Jenkins server to use Jenkins 2.107.2 and Java 8 going forward. See Jenkins for additional context.


For security and compliance reasons, Cisco CloudCenter documentation is accessible on browsers that support the Transport Layer Security (TLS) 1.2 protocol defined in RFC 5246. See your browser documentation for compliance details. In general, the following browser versions are compatible by default when viewing Cisco CloudCenter documentation.

  • Firefox 27 and higher

  • Google Chrome 38 and higher

  • Desktop Safari versions 7 and higher for OS X 10.9 (Mavericks) and higher

This section lists the documentation changes implemented in CloudCenter

Additional Documentation Updates:

  • The CloudCenter 4.6 has reached End of Life (EOL) as of April 1, 2018 and CloudCenter 4.7 will reach EOL on July 6, 2018. See End of Life Notices for additional context.

  • CloudCenter 4.5 has reached End of Support as of October 23, 2017 and this section is now archived.

Known Issues

CloudCenter has the following known issues:

  • If you deploy an Azure Pack VM with more than one additional volume, the CloudCenter platform only attaches one disk to the VM using the region-level data disk information that was configured with the default size at the time of data disk creation. All other disk creation requests will be ignored. This limitation applies to deployments that use either Generation 1 or Generation 2 images.

  • A deployment name that contains more than 63 characters fails to deploy – This is due to a Kubernetes limitation that does not allow metadata values to be longer than 63 characters. As a workaround, use deployment names that are less than 50 characters as the CloudCenter platform requires the additional 13 characters to ensure a unique cluster name. 

  • You may find the following warning message in the Kubernetes CCO logs – you can safely ignore this message as it does not impact product functionality.

    WARNING!!! The linux bootstrap URL might be valid: If the CCO cannot access the file, all deployments would fail!
  • The Docker (docker) service must be explicitly (re)started after the CCO sever is (re)started. See Certificate Authentication > Dedicated Components for process details (added on June 28, 2018).

Resolved Issues

The following issues were resolved/addressed in CloudCenter

  • CSCvf86406: An enhancement request to allow a value of 0GB to be specified for volume size during deployment.
    See the Applications and Services > Deleting Additional Volumes at Deployment Time section for additional details.

  • CSCvf98414: The Instance Type descriptions displayed during a deployment and VM details currently display the size of the additional storage that is configured, but not the size of the root disk.
    Resolution: The additional storage concept is applicable to AWS, Azure RM, Azure Stack, Alibaba and OpenStack while the other clouds would not display this field. The storage type description is fixed to reflect the correct type. See Manage Instance Types > Overview for additional context.

  • CSCvi59400: In the job details screen of a child job, the End Time column in the nodes table is mislabeled.
    : CloudCenter includes a fix to reflect the correct column name.

  • CSCvi74806: For VMware deployments, regardless of which datastore is selected for root storage, the additional storage is always placed on the first available datastore.
    Resolution: CloudCenter includes a fix to ensure that the right datastore and host are used based on whether DRS is enabled for Datastore.

  • CSCvj10970: The Application Profile > Deploy page loads slowly in a HA environment with around 2000 users.
    Resolution: CloudCenter includes a fix to address this issue and the Deploy page in the same HA environment loads faster.

  • CSCvj12646: If any ESXi host is not reachable or has an issue during a scale up, vCenter reports an error and the scale up job in CloudCenter remains stuck in the Scaling state.
    Resolution: CloudCenter includes a fix to ensure that when a VM creation fails on the cloud during scaling operation, the job status is set back to Deployed and all VM(s) launched during scaling are deleted.

  • CSCvj12865: Inconsistent SSH connectivity was encountered by a customer in VMs that were deployed in an AWS HA environment.
    Resolution: This issue was caused by the Load Balancer IP address not being updated in the CCM after the upgrade. The High Availability Best Practices > Load Balancer Requirements section specifies this requirement: If you are upgrading a component from non-HA standalone mode to HA mode, you may sometimes add new VMs to an existing CloudCenter deployment. In this case, replace the previously-configured component IP address with the IP address of the load balancer for this component.

  • CSCvj23102: VMware deployments fail with IPAM in Full Clone mode when the template being cloned does not have additional NICs.
    : CloudCenter includes a fix for this issue and deployments function as designed.

  • CSCvj27701: When using CloudCenter, an application deployment using IPAM callouts fails if the network name contained special characters.
    : CloudCenter includes a fix to accept special characters in the network name.

  • CSCvj29227: When a user has locked the cloud settings (in the Default Tier Cloud settings of the Deployment environment) to prevent it from being viewed by end users, it also prevented other users' ability to change the root disk size at deployment time and blocked the deployment from being submitted.
    : CloudCenter includes a fix to allow the root disk size to be changed by end users even if the owner locks the cloud settings. This allows end users to proceed with the deployment submission.

  • CSCvj29333: Some Azure Pack deployments fail if the application contains additional volumes and uses Generation 2 images. The failed VMs are not cleaned up.
    Resolution: While this was a known issue in CloudCenter 4.9.0, it is also a current limitation for Azure Pack configurations – At the region level, you can configure only one data disk. If you deploy a VM with more than one additional volume, only one disk will be attached to the VM with the data disk information available at region level with the default size specified at the time of data disk creation. All other disk creation requests are ignored. This limitation applies to deployments that use either Generation 1 or Generation 2 images. CloudCenter contains a fix to ensure that the failed VMs are cleaned up.

  • CSCvj70873: Failed to dynamically bootstrap when public internet access is not available.
    Resolution: As a side-effect of this fix, wget/curl are no longer installed as part of the application VM bootstrapping process. This might have implications when new deployments might fail if the image being used does not have the wget/curl utilities installed. See the Securities section above for additional context.

  • CSCvj71503:Unable to deploy in Azure when diagnostics info is not provided in Deploy.
    Resolution: CloudCenter contains a fix for this issue and deployments on Azure work as designed.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks