Cisco CloudCenter 184.108.40.206 Release Notes
First Published: March 24, 2021
CloudCenter 220.127.116.11 is only available as an upgrade for existing customers from CloudCenter 18.104.22.168, CloudCenter 22.214.171.124, CloudCenter 126.96.36.199, CloudCenter 188.8.131.52, CloudCenter 184.108.40.206, CloudCenter 220.127.116.11, CloudCenter 18.104.22.168, CloudCenter 22.214.171.124, CloudCenter 126.96.36.199, or CloudCenter 188.8.131.52. Contact the CloudCenter Support team for additional details.
You must be at a minimum version of CloudCenter 184.108.40.206 to upgrade to CloudCenter 220.127.116.11.
Effective CloudCenter 18.104.22.168 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, you must setup a local CentOS mirror and configure the CloudCenter components (CCM, CCO etc) to use the local mirror.
If you are upgrading directly to CloudCenter 22.214.171.124 from CloudCenter 126.96.36.199 or earlier release, be sure to review the CloudCenter 188.8.131.52 documentation.
See the Upgrade Overview page and the following table for additional details.
|Upgrading CentOS CloudCenter Components to CloudCenter 184.108.40.206|
|Appliance Jar Files?||Notes|
|220.127.116.11 or earlier||Yes||Yes (for CCO only)||Yes||Yes|
|18.104.22.168||No||Yes (for CCO only)||Yes||Yes||You should have already run os_upgrade when you upgraded to 22.214.171.124 – if you have not, you can run this upgrade now!|
|126.96.36.199 or later||No||No||No||Yes||Applicable to CloudCenter 188.8.131.52 or later|
|Upgrading Non-CentOS CloudCenter Components (RHEL) to CloudCenter 184.108.40.206|
|220.127.116.11 or earlier||No||Yes||Yes||Yes|
1 The os_upgrade command is not required when upgrading the REPO or Bundle store.
The following documentation change was implemented in
- Install Worker on a Windows Image (added a step to reboot the worker VM after installation)
The following issue was resolved/addressed in CloudCenter 18.104.22.168:
CSCvx21547: After upgrading from CloudCenter 4.9.1 to CloudCenter 22.214.171.124, a customer was unable to launch Linux deployments using CloudCenter 126.96.36.199 workers as they were security hardened.
Resolution: CloudCenter 188.8.131.52 includes a fix to address this issue and deployments launch as designed.
CSCvx21543: After upgrading from CloudCenter 184.108.40.206 to CloudCenter 220.127.116.11, a customer was unable to launch Windows deployments.
Resolution: CloudCenter 18.104.22.168 includes a fix to address this issue and deployments launch as designed. This issue was caused by special characters being used in the URL.
CSCvx21546: A user found that a particular service was unable to find the extracted directory from the zip file at run time.
Resolution: Multiple, varied deployments were submitted and they ran successfully in the same and similar environments when using CloudCenter 22.214.171.124.
CSCvx21544: After upgrading from CloudCenter 126.96.36.199 to CloudCenter 188.8.131.52, a customer found that the Agent Lifecycle Actions Clean Up script was not being called.
Resolution: CloudCenter 184.108.40.206 includes a fix to address this issue and the node cleanup process completed successfully.
CSCvx79689: Deployment variables with an overridden value was saved in the application profile and was reset to the default value after upgrading to CloudCenter 4.10.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that overridden values are saved in the application profile even after upgrading to 4.10.
CSCvx79704: A customer reported that the Services APIs, the Images APIs, and the Repository APIs had degraded between after upgrading to CloudCenter 4.10.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that the timings for all three APIs matched the timings in CloudCenter 4.9.1.
CSCvx79714: Additional changes in the worker.sh scripts. affected the Action params for the action script and /script was additionally prepended to service script path.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that the changes were reversed in CloudCenter 126.96.36.199.
- No labels