Cisco CloudCenter 220.127.116.11 Release Notes
First Published: September 3, 2019
September 12, 2019: Added a new section, Manually Enabling Strong Passwords for Existing Instances, based on the Security updates below.
September 29, 2019: Extended date for long-term support release.
October 17, 2019: Updated the Documentation section include the pages that were updated.
CloudCenter 18.104.22.168 is only available as an upgrade for existing customers from CloudCenter 22.214.171.124. Contact the CloudCenter Support team for additional details.
The required upgrade path to use CloudCenter 126.96.36.199 is to first upgrade to CloudCenter 188.8.131.52.
Applications and Services
To print logs and error messages from External Initialization scripts, you can use print_log or print_error functions. See External Service > External Script Specification for additional context.
Before you upgrade the agent on an imported Linux VM with the CloudCenter 184.108.40.206 agent, you must perform the additional pre-upgrade steps provided in the VM Management > Upgrade Agent section to ensure that an CloudCenter 4.10.0 agent upgrade completes as designed.
Administration and Governance
You can set up a Mongo replica in your legacy CloudCenter system. See Setup Mongo Replica for additional details.
PostgreSQL password checks are available to help prevent users from entering a weak password. For existing installations, you can manually enable strong passwords. See PostgreSQL Password > Manually Enabling Strong Passwords for Existing Instances.
End of Life Notices
This section identifies the documentation changes implemented for CloudCenter 220.127.116.11:
End of Support Notices (extended support for long-term support release)
Install Worker on a Windows Image (added details on the AgentLite option)
To schedule jobs from the deploy flow, verify that the clock on the CCM is synced with the NTP server so that the request is scheduled at the applicable time. See Application Tasks > Deploy Applications for additional details
The following issues were resolved/addressed in CloudCenter 18.104.22.168:
CSCvq70481: CloudCenter needs to support adding tags to volumes on Azure RM and AWS clouds
Resolution: CloudCenter Platform 22.214.171.124 provides a fix to include tags that have been added at the VM instance-level to any volume that is attached to the VM. This fix applies to managed VMs in AWS and Azure cloud environments.
CSCvq82788: A standard user was unable to view VM details from the deployment page even if they belonged to a group that had manage access for the underlying deployment environment.
Resolution: CloudCenter Platform 126.96.36.199 provides a fix to address this issue and the VM details link functions as designed for standard users as well.
CSCvq68986: Parameters for External Services are not being passed to dependent tiers in hybrid deployments.
Resolution: CloudCenter Platform 188.8.131.52 provides a fix to address this issue and the parameter is being passed to dependent tiers in hybrid deployments
CSCvq47689: Under certain situations, when CloudCenter deploys a VM without an agent, the IP address of the VM is not reported correctly in the CloudCenter platform.
Resolution: CloudCenter Platform 184.108.40.206 includes changes to address this issue and ensure that the IP address is reported accurately.
CSCvq60907: Resource placement callouts should have a mechanism (a variable that is part of the userenv file) to return data and pass them as part of post-service/pre-service scripts.
Resolution: CloudCenter Platform 220.127.116.11 provides a fix to ensure that the external_action for post_vm_start scripts is also retrieved to ensure that results of resource placement callouts are available as environment variables in the post-service/pre-service scripts.
CSCvq60909: Resizing a virtual machine of a deployed application removes the old instance type from image mapping and replaces it with new instance type. A resize operation should not modify the image mapping.
Resolution: CloudCenter Platform 18.104.22.168 provides a fix to address this issue and the resized operation works as designed.
CSCvq19849: Some instance types in AzureRM are incorrect or not supported in CloudCenter 22.214.171.124.
Resolution: CloudCenter Platform 126.96.36.199 provides a fix to include the supported instance types for supported AzureRM regions.
CSCvq07374: Adding a deleted version of an application, gives a version loop error.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that the version of an application that has been deleted can be added again.
CSCvp95768: Save parameters generated by external services during deployment for use during termination phase.
Resolution: CloudCenter 184.108.40.206 includes a fix to ensure that parameters generated by external services during a deployment are available during termination of multi-tier hybrid cloud deployments.
CSCvp85891: When attempting to clone a VMware VM and the VM name already exists, then the cloning operation fails, and the job goes into an error state. As part of the clean up, the pre-existing VM with the same name is also deleted.
Resolution: CloudCenter Platform 220.127.116.11 provides a fix to ensure that two different VMs on a VMware datacenter cannot have the same name if they are deployed in the same folder.
CSCvp53840: Parameters from external service are not passed to dependent tiers in hybrid cloud deployments.
Resolution: CloudCenter Platform 18.104.22.168 provides a fix to address this issue and the parameters are passed as designed for hybrid deployments.
CSCvp42558: When terminating a multi-tiers deployment, the tier/service that started last must be terminated first. That is, the termination actions must be executed in a reverse order of the deployment actions; otherwise, some termination scripts fail and/or the resources are not cleaned up.
Resolution: CloudCenter Platform 22.214.171.124 provides a fix to ensure that the termination actions function in the applicable order.
CSCvo81642: The groups with which an application profile is shared are not displayed during sharing operation for a subtenant user with Manage privileges on the application profile.
Resolution: CloudCenter Platform 126.96.36.199 provides a fix to ensure that when logged in as a sub-tenant, the application sharing dialog lists the groups with which the application is shared.
CSCvn69265: Google cloud is missing the FINLAND (europe-north1) and NETHERLANDS (europe-west4) regions.
Resolution: CloudCenter Platform 188.8.131.52 includes the supported instance types for these supported regions on Google Cloud Platform.
CSCvr00696: CloudCenter should support the Azure India regions.
Resolution: CloudCenter Platform 184.108.40.206 provides a fix to include the supported instance types for supported India regions for AzureRM.
- No labels