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

CloudCenter – July 4, 2017


  • July 11, 2017 (added ServiceNow Integration – CloudCenter, v1.4)

  • July 17, 2017 (added Downloading CCM/CCO logs, a known issue in 4.8.0, to the Resolved issues List in

  • August 1, 2018 (added details on the Upgrade Path)


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

Upgrade Instructions

You can only upgrade to CloudCenter from CloudCenter 4.6.0 and later releases.

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

Upgrade Path

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


No updates


  • OpenStack
  • Azure RM
    • Support for Managed Disks in Azure – Prior to CloudCenter, you could create a storage account and create storage for instances under that account. With the introduction of the Managed Disks feature in Azure,  you can select one of three pre-defined disk sizes in the CloudCenter platform during deployment: 

      • Premium (Managed)
      • Standard (Managed)
      • Unmanaged

    • See Multiple Volumes > Azure Type Nuances for additional context.

Applications and Services

  • CloudCenter includes an improvement to allow service parameters to be displayed to end users during deployments. Users can define parameters as deployment parameters and set preferences for them. These preferences govern if the parameters should be visible, editable, and optional during a deployment. See Deployment Parameters for additional context.

CloudCenter Management

No updates

Administration and Governance

No updates


No updates

End of Life Notices

See End of Life Notices for additional details.


No updates


  • 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..


No updates


  • ServiceNow:Integration – CloudCenter, v1.4 is available for the following ServiceNow releases (added to release notes on July 11, 2017):
    • ServiceNow, Istanbul

    • ServiceNow, Helsinki

    See Release Notes for v1.4 and Install and Configure v1.4 for additional context.


This section lists the documentation changes implemented in CloudCenter

  • CloudCenter Changes: See the links provided in this section for additional context on documentation for this release.

  • The following bullets identify the documentation changes implemented in CloudCenter

Known Issues

CloudCenter has the following known issues:  

  • Python modules cannot be installed on the CloudCenter platform with cliqruser privileges – Administrators must provide explicit privileges to cliqruser in order to install additional software on the CloudCenter platform.
  • To launch custom Azure RM images, you must select one of the Managed Storage options as described in the Multiple Volumes > Azure Type Nuance section.

  • You cannot deploy Azure Classic Images to deploy VMs in Azure RM from the CloudCenter platform. You must first migrate them to Azure RM. See Configure Image IDs > Azure RM Image ID for additional context.

  • The Docker network may have intermittent network failures. The CloudCenter team has not been able to reproduce these failure scenarios. To workaround this issue, restart the Docker service.

  • CloudCenter 4.8.0 allows you to configure special characters that need to be excluded while generating the Windows Password in the Cloud Configuration page. While this field is available for AWS, OpenStack, VMware, and Azure Classic cloud configurations, it is currently not available for other cloud configurations. (Added on July 6, 2017)

Resolved Issues

The following issues were resolved/addressed in CloudCenter

  • Issue: The custom parameters in the Services page do not all display every time. A simple page reload will usually fix it. 
    Resolution: CloudCenter includes a fix to address this issue and the custom parameters display as designed.
  • Issue: Inability to identify the IP address of a particular VM in a deployed application – while you can use the parsed output of the Get Job Details API to retrieve any IP address based on the Node ID, the tier-level runtime environment variable may not be available via this API to retrieve (for scaling purposes) the IP address on which the external script runs. 
    : CloudCenter includes the following new environment variables in the external initialization scripts (Docker container) to identify the current node when a scaling operation is completed:
    • cliqrNodeId : The Node ID of the VM for which the external initialization script is executed.
    • cliqrNodeHostname : The hostname of the VM for which the external initialization script is  executed.
    • cliqrNodePublicIp : The Public IP of the VM for which the external initialization script is executed.
    • cliqrNodePrivateIp : The Private IP of the VM for which the external initialization script is executed.
    See CloudCenter-Defined Parameters for additional context.
  • IssueWhen deploying applications on VMware, you may see the datastore cluster list displaying duplicate values if you have multiple datastores within the cluster. As a result, you may not be able to deploy to the desired datastore when DRS is disabled for that datastore cluster.  
    : While this was a known issue in CloudCenter 4.8.0, CloudCenter includes a fix to address this issue. If DRS is disabled when the CloudCenter platform encounters a datastore cluster with multiple datastores, only one correct entry of each datastore cluster (regardless of the number of existing datastores) is displayed. Additionally, the correct number of datastores for each datastore cluster is displayed even when DRS is disabled.
  • Issue: When a user deploys a custom Windows2012 image on a VMware cloud, the VM was deployed successfully and the IPAM callout log displays the correct information. However, the VM was assigned a DHCP address even though a static IP was assigned for the IPAM callout script, as the guest OS customization occurs after the initialization scripts are executed. 
    : CloudCenter includes a fix to successfully retain the same IP as the IPAM callout script even after a reboot during the node initialization phase.
  • Issue: The Bundle Store configuration works when using a HTTP URL. However, when configuring the Bundle Store using a secure HTTPS URL, the configuration times out with the instance bootstrapping is timed out error message.
    : CloudCenter includes support for the HTTPS protocol being used to configure Bundle Stores. To use the HTTPS protocol, see Management Agent Worker (Conditional).
  • Issue: The database is open to the world if you use the HA setup process. 
    : CloudCenter includes a fix for the CloudCenter installer process to authenticate the database using a password. To use this method, you may need to manually patch PostgreSQL and MongoDB servers. Contact CloudCenter Support to obtain patch instructions. See CCM and Database HA Upgrade > CloudCenter Version-Specific Patch and CCO HA Upgrade > CloudCenter Version-Specific Patch for additional context.
  • Issue: While scheduling a deployment, if you provide the same name for two different deployments then the system accepts the same name for both deployments. 
    Resolution: CloudCenter includes a validation to address this issue in both normal and scheduled deployments.
  • Issue: API and UI don’t really provide useful error messages. For example, when making calls to update users in a group, leaving out what could be considered an optional, if empty, field returns a 500 response.
    : CloudCenter provides a fix to address error messages while updating users for a group. 
    Issue: Some users require the ability to use macros in the URL for a webservice.
    : The CloudCenter implementation uses %userExternalId% as a macro that is replaced by the user's external ID in the URL for webservice (see CloudCenter-Defined Parameters > Other Macros – Input Parameters for Script  for additional context.)
  • IssueWhen configuring web service parameters (see Using Parameters > Granular Control for User-Defined Parameters), and the parameter is: 
    • Marked Optional – The default value shown to the user is not provided if the user does not change it. If the user change the default, then the value is passed.
    • Marked Required – Even though a valid selection is made based on the default value, the user still receives a warning.
    Resolution: CloudCenter includes the following fixes for this issue:
    • Marked Optional – The Cloud Center platform accepts the provided default values if any.
    • Marked Required – If a default value is not provided, then the user must select one of the values returned by the web service.
  • Issue: When VMs are created for CloudCenter deployments, numerous files are downloaded as part of installation and left behind after the installation/upgrade is complete. These files should not be exposed to end users. 
    : CloudCenter includes a fix to clean up unwanted files after an installation or upgrade. However, the application and service bundles continue to remain.
  • Issue: When launching a VM, there is a latency (30 – 60 seconds) between CloudCenter components when performing actions on a VM. This is most notably seen when creating a VM, watching it on the console, and the amount of time before it is displayed as deployed in CloudCenter. The user has to wait to long before the job is submitted and there is any indication in the UI. 
    Resolution: CloudCenter includes a fix to display the Node booting up.. message that displays for about 4 minutes before any other message is displayed.
  • Issue: The Windows-generated password is a random string of characters that includes special characters that can cause programmatic issues. Excluding the programmatically-challenging characters (single and double quotes, back slashes, and so forth) can ease the cloud configuration process. 
    Resolution: CloudCenter includes an enhancement where you can specify the characters to be dropped when a Windows image is launched. See Cloud Configuration for additional context.
  • Issue: Some users were unable to launch deployments if they used uppercase characters in the Azure Cloud when using the Callout Script Name Strategy. 
    Resolution: The CloudCenter Team was able to successfully to launch deployments even when using uppercase characters in the Azure Cloud.
  • Issue: Some users wanted installer support for Firewalld as an option.
    Resolution: – CloudCenter includes a fix to allow fresh CloudCenter installations to configure Firewalld by default. Existing customers can Contact CloudCenter Support to obtain migration instructions.
  • Issue: Failed Jobs left VMs behind as a result of the terminate logic on a node creation failure. 
    Resolution: CloudCenter includes a fix to terminate the VMs for failed jobs.
  • Issue: Deleting a cloud region requires a manual DB cleanup. The UI messages are generic and does not clearly state the specific resources that cause an environment deletion to fail. So the user does not know what action to take.  
     CloudCenter includes a fix to display specific messages to let the user know if the environment deletion depends on active deployments or activation profiles or both.  It also provides a list of active deployments under the Environment tab. You can view these deployments by clicking View Details next to the error message.  The activation profile(s) is(are) also displayed in the message. Se Cloud Region Configuration for additional details.
  • Issue: Scale up and Down actions should pass information about which VMs are added/removed to the tiers (example Load balancer). 
    Resolution: CloudCenter includes a fix to pass environment variable for scaling scenarios. See CloudCenter-Defined Parameters > Environment Variables for N-Tier deployments for additional details on the added environment variables.
  • Issue: Disabling Termination protection fails when the Job information is not found in the CCO. 
    Resolution: CloudCenter includes a fix to log a warning/error and give users the option to disable terminate protection, when the job info is not found (deployment hasn't progressed to a state where the job information was added into CCO DB).
  • Issue: Add CloudFamily as an environment variable in the Docker container for external services and resource placement/validation callouts. 
    Resolution: CloudCenter includes the Cloud_Setting_CloudFamily variable in the Docker container. See CloudCenter-Defined Parameters > Docker Container Environment Variables for a complete list of environment variables provided in Docker containers by the CloudCenter platform.
  • Issue: Downloading CCM/CCO logs does not work as designed when using the Non-HA or Non-HA Standalone modes.
    Resolution: CloudCenter includes a fix to address this issue and downloading CCM/CCO logs works as designed in Non-HA and Non-HA Standalone environments.

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved