Cisco CloudCenter 4.10.0.13 Release Notes

Release Date

First Published: March 24, 2021

Installation

CloudCenter 4.10.0.13 is only available as an upgrade for existing customers from CloudCenter 4.10.0.3, CloudCenter 4.10.0.4, CloudCenter 4.10.0.5,  CloudCenter 4.10.0.6, CloudCenter 4.10.0.7, CloudCenter 4.10.0.8, CloudCenter 4.10.0.9, CloudCenter 4.10.0.10, CloudCenter 4.10.0.11, or CloudCenter 4.10.0.12. Contact the CloudCenter Support team for additional details.

Upgrade Path

You must be at a minimum version of CloudCenter 4.10.0.3 to upgrade to CloudCenter 4.10.0.13.

Effective CloudCenter 4.10.0.7 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 4.10.0.13 from CloudCenter 4.10.0.10 or earlier release, be sure to review the CloudCenter 4.10.0.10 documentation.


See the Upgrade Overview page and the following table for additional details. 

Upgrading CentOS CloudCenter Components to CloudCenter 4.10.0.13
From

core_upgrade

Appliance Jar Files?Notes
 os_upgrade1?

MongoDB?

Component?
4.10.0.5 or earlierYesYes (for CCO only)YesYes
4.10.0.6NoYes (for CCO only)YesYesYou should have already run os_upgrade when you upgraded to 4.10.0.6 – if you have not, you can run this upgrade now!
4.10.0.7 or laterNoNoNoYesApplicable to CloudCenter 4.10.0.7 or later
Upgrading Non-CentOS CloudCenter Components (RHEL) to CloudCenter 4.10.0.13
4.10.0.12 or earlierNoYesYesYes

1 The os_upgrade command is not required when upgrading the REPO or Bundle store.

Documentation

The following documentation change was implemented in CloudCenter 4.10.0.13:

Resolved Issues

The following issue was resolved/addressed in CloudCenter 4.10.0.13:

  • CSCvx21547After upgrading from CloudCenter 4.9.1 to CloudCenter 4.10.0.12, a customer was unable to launch Linux deployments using CloudCenter 4.10.0.12 workers as they were security hardened.  
    Resolution:  CloudCenter 4.10.0.13 includes a fix to address this issue and deployments launch as designed. 

  • CSCvx21543: After upgrading from CloudCenter 4.9.1.1 to CloudCenter 4.10.0.12, a customer was unable to launch Windows deployments.
    ResolutionCloudCenter 4.10.0.13 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 4.10.0.13.

  • CSCvx21544: After upgrading from CloudCenter 4.9.1.1 to CloudCenter 4.10.0.12, a customer found that the Agent Lifecycle Actions Clean Up script was not being called.  
    ResolutionCloudCenter 4.10.0.13 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 4.10.0.13 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. 
    ResolutionCloudCenter 4.10.0.13 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.  
    ResolutionCloudCenter 4.10.0.13 includes a fix to ensure that the changes were reversed in CloudCenter 4.10.0.13.





  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks