Cisco CloudCenter 4.8.0x Release Notes

Release Date

CloudCenter 4.8.0 – May 15, 2017

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


CloudCenter 4.8.0x is available as virtual appliances. See Virtual Appliance Overview for additional context.

Upgrade Instructions

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

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


  • Monitor: The Monitor component is now a requirement as you cannot download log files without installing this component. See Monitor (Required) for additional details.
  • Upgrade Worker: You can upgrade the management agent (worker) for an existing deployment. This functionality was not supported in earlier CloudCenter releases.
  • Repository Appliance: The Repo virtual appliance contains virtual appliances for multiple components – dedicated bundle store, dedicated package store, and dedicated Docker registry. Once you download the Repo appliance, all these files become available to you and you can configure the properties when required. See Repo (Conditional) for additional details.
  • Custom Certificates:

    • Effective CloudCenter 4.8.0, you can generate and update the certificate for the CCM server.

    • You can additionally update the certificate for the CCO, Monitor, Guacamole, and ESB components for each deployment.

    • Use the configuration wizards (*_config.wizard) for each component to generate or update the certificates when required.

    • See Certificate Authentication for additional context.
  • Federated CCM Infrastructure:

    • The CloudCenter platform supports a Federated CCM Management infrastructure to enable information sharing, reduce complexity, and improve management flexibility within a private cloud infrastructure.

    • See Federated CCM Management for additional context.


  • VMware:
  • SoftLayer:
    • Dallas (DAL05, DAL06, DAL10, DAL12 (DAL13)Houston ( HOU02), Seattle (SEA01), Washington DC (WDC01, WDC04, WDC06, WDC07), Montreal (MON01), Toronto (TOR01), Amsterdam (AMS01, AMS03), Frankfurt (FRA02), Milan (MIL01), Oslo (OSL01), Paris (PAR01), London (LON02), Chennai (CHE01), Hong Kong (HKG02), Seoul (SEO01), Singapore (SNG01), Tokyo (TOK02), Sydney (SYD01), Melbourne (MEL01), and Queretaro (MEX01) regions are added to the list of supported clouds.
    • See Public Clouds for additional details.
  • OpenStack:
  • Google Cloud:
    • Western US, Eastern US, Western Europe, Eastern Asia-Pacific (Taiwan), and Northeastern Asia-Pacific (Tokyo, Japan) regions are added to the list of supported clouds.
    • See Public Clouds for additional details.
  • Azure RM
    • Canada East, Canada Central, Korea Central, Korea South, US West 2, and US West Central regions are added to the list of supported clouds. See Public Clouds for additional details. 

    • 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.
  • AWS:
    • Asia Pacific (Mumbai) and EU (London) regions are added to the list of supported clouds.
    • See Public Clouds for additional details.
  • Alibaba:
    • You can configure a VM Naming Callout Script for Alibaba.
    • The China North 3 (Zhangjiakou) region is added to the list of supported clouds. See Public Clouds for additional details.
  • New Images provided by Cisco: Application VM (worker) images:
    • New worker images are available for Google Cloud to support different OS types.
    • The worker images for SoftLayer (Bluemix) were private in earlier CloudCenter releases and have been made public to support dynamic bootstrapping.
    • See Base OS Images for a complete list for each cloud.

Applications and Services

  • The default enable.appstore.publishToPublic settting in the file has been changed from false to true (enable.appstore.publishToPublic=true) to ensure that a tenant is able to publish applications to the Marketplace by default.
  •  The Suspend script, introduced in CloudCenter 4.8.0 is similar to the existing hook for the Resume script. The Suspend script is triggered when the node is suspended. See Deployment Lifecycle Scripts for additional context.
  • While modeling applications or services, multi-select option can be enabled for parameters of type list. This addition makes it possible for users to select multiple values for a parameter from a list of values.

  • 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

  • Virtual Machine Management:
    • Datacenters can contain thousands of Virtual Machines (VMs) that are not launched from CloudCenter. These VMs are referred to as Brownfield VMs. Starting from CloudCenter 4.8.0, you have the option to use the VM management feature to bring Brownfield VMs under CloudCenter management.

    • This feature allows you to import VMs into the CloudCenter platform and manage them directly from the CCM.

    • A lightweight agent, called AgentLite, can be installed on VMs that have been imported into CloudCenter. This agent enables the CloudCenter platform actions for Brownfield VMs.
    • See VM Management for additional context.
  • Custom Actions Management:
    • Custom Actions that were configurable in the Policies tab prior to CloudCenter 4.8.0 are now integrated in the Actions Library functions.

    • Actions Library is an asynchronous framework that extends the CloudCenter platform capabilities by enabling you to create, manage, and execute actions for VM management. This framework allows users to define actions and execute them on different CloudCenter resources such a VMs, Deployments, or Application profiles.
    • Actions library provides the ability to define Day 2 operations as VM actions and execute them on the VMs in your datacenter.
    • See Actions Library for additional context.

Administration and Governance

  • Deleting Security Profiles: This is a change!

    • Effective CloudCenter 4.8, when you try to delete a security profile, the CloudCenter platform deletes the firewall rules on all configured clouds.
    • Be sure to make the CCOs on the required clouds functional and delete the cloud regions that are not in use.
    • See Security Profiles for additional context.
  • Reports: 


  • Access Control Lists (ACLs): on Federated CCMs and Virtual Machines...
    • Actions: Permissions define certain actions that users can perform. You can control the permissions for a custom action. See Permission Control > Custom Actions for additional context.

    • Virtual Machines: By default, imported VMs are not shared/visible to other users. Permissions and visibility to other users are derived based on the tenant administrator's invitation(s) when importing the VM.
    • Federated CCMs: Users are restricted to operations based on:
      • The Permission Control (Federated CCM Permissions) level assigned to them on the Subordinate CCM.
      • Operations allowed by the Parent CCM on the Subordinate CCM.

End of Life Notices

See End of Life Notices for additional details.


The following features are deprecated effective CloudCenter 4.8.0:

  • Following Microsoft's end-of support announcement for IE10, the CloudCenter platform support for Internet Explorer now starts from IE11. See Browser Compatibility for additional context.

  • The Managed VM Inventory Report and the Unmanaged Inventory Report are deprecated and replaced by the Virtual Machines tab in the CCM UI.

  • The VMware NSX feature is no longer supported by CloudCenter and all references are removed from documentation.

  • Cisco no longer provides support for NTT (managed private) clouds and all references are removed from documentation. 

  • The auto upgrade of the CloudCenter Management Agent is removed. Instead, it is supported as a CloudCenter platform action – to upgrade the agent on a running VM. See VM Management for additional context.


  • New UI:
    • The CloudCenter Navigation menu has changed – the Admin tasks are now displayed in its own area to accommodate the long list of tasks!
    • The new server Details page is available for VMs and contains logs for the orchestration tasks and a history of actions.

    • The Search and filter functionalities are enhanced to provide an enhanced user experience.
      • See UI Behavior for additional context on common icons and
      • See VM Management for additional context based on filtering favorites, search strings, time period considerations, and custom filters.
    • The Dashboard details now include:
      • Imported VM information (see VM Management for additional context)
      • My Data information by Cloud and by Application
      • See The Dashboard for additional context.
  • New Menu Items:
    • Deployments: You now see a separate menu item called Deployments.
    • Deployment Environments: You now see a separate menu item called Environments.
    • Virtual Machines: This new menu item provides a list of Managed (user and admin access to CloudCenter managed VMs) and Unmanaged VMs (admin access to VMs discovered in your cloud) along with new VM management capabilities. See Virtual Machine Management for additional context. It is now easy to identify the VMs that are most important to you using advanced filters.
    • Actions Library: This new menu item provides capabilities to configure VM management actions that are displayed based on cloud, operating system, VM state, user permissions, and configured actions. You no longer need to access the cloud console to perform re-configuring actions like adding and removing storage disks. Multiple action types like Scripts, Commands, UCSD workflow, Puppet, Chef, and Ansible can be defined for execution on VMs. A Preview button allows you to view the action before your release it for use. See Actions Library for additional context.
    • More: The less frequently accessed areas of the CloudCenter platform are grouped under the More section.
  • Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.
  • Localization: Effective CloudCenter 4.8.0, Cisco provides three additional language options besides English – French, Japanese, and Simplified Chinese. See UI Behavior for additional context.


CloudCenter 4.6.0 introduces v2 APIs, where applicable. If a new API is introduced for the first time, it continues to use v1 as it is still the first version of that particular API. The following list differentiates between the New and Updated APIs for CloudCenter 4.8.0.


  • SAML: CloudCenter 4.8.0 supports SAML settings to redirect users to a custom logout page instead of the global logout – if configured by the enterprise in the Logout URL field. See SAML SSO for additional context.
  • ACI: When selecting a new EPG as the NIC network type, you have the choice to select pre-existing contracts from this tenant or the common tenant. You can also choose contract interfaces (imported contracts) from the selected tenant. The CloudCenter platform configures the newly created EPGs to consume these contracts. See ACI > Using Extensions for additional context.
  • 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 4.8.0.

  • New look and feel that adheres to Cisco's brand requirements for the CloudCenter Documentation 4.8 website and addresses the following changes:
    • The use of containers that go beyond the display canvas – proper wrapping of content within the canvas. This problem was especially visible in the API pages if the code line exceeded the page width.
    • A limited page refresh with every click of a menu item now reduces the page loading time.
    • Anchored pages display visible titles if you click a Table of Contents (TOC) item in the display page. Earlier, the title was not visibly displayed.
    • A maintained scroll position that displays the selected item in the left pane so you do not have to scroll down to see the page level in the documentation structure.
    • The CliQr logo is replaced by the Cisco logo in the main frame.
    • The URL is replaced by the URL in all cross-references.
    • The CloudCenter CLI tab is removed from CloudCenter versions that no longer support the CLI option. The CLI tab continues to display in the left pane for the CloudCenter 4.2 to 4.5 documentation space.
  • The easiest way to setup CloudCenter components is to use Virtual Appliances. A majority of CloudCenter customers use Virtual Appliances to setup all CloudCenter components. Cisco provides the virtual appliance instructions for all CloudCenter components. If you have unique installation requirements (for example, custom OS images), contact the CloudCenter Support team.
  • CloudCenter 4.8.0 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 4.8.0 has the following known issues:

  • When running benchmarks for legacy applications on VMware or OpenStack clouds, you must wait till the data is loaded. If you enter any information before the data is loaded then the Submit button is disabled.  
  • When configuring Federated Certificate Management, you must use custom certificates. However, once you configure the certificates and Federated CCM Management, then you cannot change the certificates as it results in a link communication break between the parent and subordinate CCMs.

  • Ability to establish a VNC session with CloudCenter application VMs only functions if the VMs are launched from images that already have VNC installed. Otherwise, users will not be able to connect to those VMs using VNC and will see a connection error.

  • On Google Cloud, dynamic bootstrapping does not work on the default public images for Windows as the administrative user is not present. As a result, Cloud-Init (bootstrap) scripts are not executed on these instances.

  • The CloudCenter platform schedules application deployment in UTC and not in the local time zone. If it needs to be scheduled in a different time zone, manually convert the time zone to UTC and then configure the scheduling.  

  • The Running VMs count in the Virtual Machines tab includes VMs that display the ERROR / NOT REACHABLE status. Due to this display, the value of the Total VMs is less than the value of the Running VMs in the Managed Virtual Machines section. See the VM Management page for additional context  

  • CloudCenter 4.8.0 does not support the use of Artifactory repository for the AgentLite feature. This prevents you from using the Artifactory repository for actions executed on Brownfield VMs.  

  • Downloading CCM/CCO logs does not work as designed when using the Non-HA or Non-HA Standalone modes. To workaround this issue set the {component}.log.haHostIdentifierList with the value of the {component} property as follows:

    • CCM: Set the ccm.log.haHostIdentifierList with the value of property in the /usr/local/tomcat/webapps/ROOT/WEB-INF/ file on the CCM server.

    • CCO: Set the cco.log.haHostIdentifierList with the value of property in the /usr/local/tomcat/webapps/ROOT/WEB-INF/ file on the CCO server.

    • These changes require a restart of CCM/CCO.

  • Running Puppet actions on Ubuntu VMs is not supported in Cloud Center 4.8.0.

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

 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 4.8.0:

  • Issue: VM's are launched even if the plan quota for the number of VMs has been exhausted and exceeded.
    Resolution:The VM count behavior was changed in CloudCenter 4.8.0 to include the minimum number of VMs in the tier, the running VMs, and the total VMs when you submit a job. This fix prevents second time submissions if the VM count is greater than the plan limit.

  • Issue: When the Tenant ID of a vendor is changed, the authentication settings of the vendor changed from SAML to Default. 
    Resolution: In CloudCenter 4.8.0, whenever the Tenant ID of a vendor is changed, the new ID is updated in the authentication settings details of the vendor.

  • Issue: If the value of a custom parameter or a global parameter contains the $ character, then you cannot use this parameter in macros. To use special characters in parameters and avoid deployment errors, use the escape sequence with these characters.
    Resolution: While this issue was initially found in CloudCenter 4.7.0, CloudCenter 4.8.0 includes a fix to allow you to submit parameters with special characters without using the escape sequence.
  • Issue: The CloudCenter Management Agent tools should not update JAVA_HOME system wide.   
    Resolution: The CloudCenter Management Agent no longer uses or updates system-level JAVA_HOME setting. Instead, it has its own JRE in its workspace.  
  • Issue: Issue with stopping Jetty on worker VMs.
    Resolution: When the
    jetty stop process is called it shuts down gracefully and if it fails, then then process is killed.
  • Issue: The cco_config_wizard should create MongoDB folder if missing while configuring HA 
    Resolution: The
    cco_config_wizard creates and sets permissions for the MongoDB folder on all three HA VMs.

  • Issue: When upgrading from CloudCenter 4.2x, the Azure CCO's /etc/profile is not updated to point to Java 8. 
    : Recent installs have Java 8 set in and /etc/profile.d/ This issue was specific to CloudCenter 4.2x.

  • Issue: When deploying a Linux-based OS to the Dimension Data cloud, the required parameter administratorPassword was missing which results in deployment failure.
    Resolution: The CloudCenter 4.8.0 software includes the missing administratorPassword parameter which now allows deployments on Dimension Data to complete successfully.

  • Issue: When an external service uses an environment variable, the value is cached in memory and not persisted across CCO restarts in HA configurations.
    Resolution: CloudCenter 4.8.0 includes a fix to ensure that environment data is persisted across CCO restarts.
  • Issue: Some CloudCenter APIs return null values inconsistently.
    The Resource URL field is correctly populated for nested users, groups, and roles for v1/tenants APIs. The v1/jobs API has been deprecated and you can use the v2/jobs API for the same purpose.
  • Issue:  When modelling N-tier applications with user parameters defined with system parameters names like minClusterSize, numClusterNodes, numSeedNodes, maxClusterSize, then these values are overwritten by the default value provided in the user parameters.
    CloudCenter 4.8.0 includes a fix to ensure that the system issues an error if you try to define user parameters at a tier or global level by using the same name as system parameters. 
  • Issue: Disabled tenants are still displayed in the CCM UI as the sysadmin. 
    Resolution: CloudCenter 4.8.0 includes a fix to ensure that disabled tenants are no longer displayed in the vendors list.  
  • Issue: Every time you update a SAML authentication settings, if plain metadata file is used instead of URL it's not correctly updating the same setting in the database. URL will always take precedence.
    If both URL and the flat file are provided, the URL is assigned the precedence as designed. If you want to use the flat file, empty the field that corresponds to this URL. Be aware that this change can take several minutes to take effect.
  • Issue: Application deployments on VMware into port groups that use Nexus 1000v Distributed Virtual Switch (DVS) results in an error.
    : CloudCenter 4.8.0 includes a fix to ensure it is possible to successfully deploy to port groups that use Nexus 1000v DVS.
  • Issue: Security groups are not deleted on AWS after jobs launched by a user are terminated and the user is deleted from the CloudCenter platform.   
     Resolution: CloudCenter 4.8.0 includes a fix to ensure that the security group pertaining to the user gets deleted on AWS once the user is deleted from the CloudCenter platform.  
  • Issue: Even if specified in the Topology Modeler, the option to make the ELB public does not work. 
    For an external ELB configuration, you must choose a public subnet in the same VPC where VMs being load balanced are present. Then, the ELB can access VMs through the local VPC network and have a public IP as well.
  •  Issue: When you log into the CCM UI, the cloud status is displayed accurately. When you visit a different page (Deployments or Admin) and return to the Dashboard, the cloud status displays a spinning wheel.
     CloudCenter 4.8.0 includes a fix to ensure that the Cloud Status displays as designed regardless of the user's navigation.
  • Issue: The appCategories field is not populated when making an API call to CloudCenter for an application profile that has been placed into several categories.
    : CloudCenter 4.8.0 includes a fix to ensure that the appCategories field is populated when making an API call to fetch an application profile.
  • Issue: When using a VM that has CloudCenter 4.7.0 on a Dimension Data cloud, you may not be able to register the CCO.
    For Dimension Data clouds, IPv6 address of the CCO server was used to post CCO node metadata. The CloudCenter 4.8.0 software provides a fix to ensure that the CCO does not wait for the node metadata information.    
  • Issue: When a multiple service parameters of type textarea and text are added to a service definition, then the service was not saved when using the CCM UI.
    Resolution: CloudCenter 4.8.0 includes a fix to save a service definition when multiple service parameters of types textarea and text were added and this feature now works as designed..
  • Issue: The CloudCenter account on Windows is created without a way to retrieve the password from the CloudCenter platform.
    Resolution: The dynamically-generated password is injected as part of the lifecycle action and made available for use inside External scripts. See Deployment Lifecycle Scripts for additional context.

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.
  • Issue: When 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.)
  • Issue: When 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