Cisco CloudCenter 22.214.171.124 Release Notes
First Published: January 18, 2019
- February 20, 2019: Added the Documentation section to include updated pages.
- February 25, 2019: Clarified the process when configuring CCM on a FIPS System.
- March 8, 2019: Clarified the running VM requirement when importing VMs as part of VM Management.
- April 16, 2019: Updated the Documentation section.
CloudCenter 126.96.36.199 is available as installer for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.
You can only upgrade to CloudCenter 188.8.131.52 from CloudCenter 4.7 and later releases.
To upgrade to CloudCenter 184.108.40.206, see Upgrade Overview.
If you are upgrading your environment to use tagless governance, you must use the latest CloudCenter 220.127.116.11 ccm-response.xml file to upgrade to CloudCenter 18.104.22.168. See Migrate to Tagless Governance for additional context.
When you upgrade the CCM, you will see an additional warning if the ccm-response.xml file is not edited as mentioned in the migration procedure, you can dismiss the warning if this change does not affect your environment.
The recommended upgrade path to use CloudCenter 22.214.171.124 is to first upgrade to CloudCenter 4.10.0.
Applications and Services
Administration and Governance
End of Life Notices
The following documentation change was implemented in CloudCenter 126.96.36.199
- Deployment Lifecycle Scripts (added note on HTTP/S protocol requirement for request utility)
- VM Management (added the running VM requirement when importing VMs)
- Deployment Lifecycle Scripts (added a new line to the code block in The #!CliQrReboot: Header section)
- Configure an Azure Stack Cloud (updated how to obtain the Tenant ID, Client ID and Client Key)
- Install Worker on a Windows Image (changed Linux to Windows in the note)
The following issues were resolved/addressed in CloudCenter 188.8.131.52:
CSCvn66297: If your CloudCenter 4.10.0 environment does not use Azure RM or Azure Stack cloud accounts, and you later add them to the CCM and subsequently upgraded to a later version of CloudCenter (for example, 184.108.40.206 or later), then the client key, certificate password, certificate content will be re-encrypted by the CloudCenter platform.
Prior to CloudCenter 4.10.0, the client key, certificate password, certificate content were stored as decrypted fields in the database.
Effective CloudCenter 4.10.0 they are stored as encrypted fields.
If your environment uses CloudCenter 4.10 or earlier versions and you have already configured Azure RM or Azure Stack cloud accounts, then they work as designed even after the upgrade.
If you added any Azure RM or Azure Stack cloud account after upgrading to CloudCenter 4.10.0, the suggested workaround is to delete these cloud accounts – and either restart the CCM or upgrade to CloudCenter 220.127.116.11.
CSCvn54384: After a user upgraded from CloudCenter 4.9.1 to CloudCenter 4.10.0, the web service global parameter did not work with proxy authentication which was set using the CCM configuration wizard.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that web service calls are routed through the proxy. CloudCenter 22.214.171.124 includes a fix to ensure that the CCM-CCO communication functions as designed.
CSCvn74882: In CloudCenter 4.10, when executing external services, if the external service calls the print_log function from util.sh, the log messages are not displayed in the UI until the external service finishes running.
Resolution: CloudCenter 126.96.36.199 includes a fix to populate task details even for external service deployments.
CSCvn95685: When you deploy a Kubernetes application and select an environment that has more than one Kubernetes cloud with a storage class type that is the default for this Kubernetes environment; and later change the cloud type, the instance type changes but the storage type still displays the same choices from the older cloud instead of the newly changed cloud.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that the cloud type updates to display the changed cloud settings.
CSCvn95703: When you click Configure Cloud, the region page is not rendered and the spinner continues spinning. However, when you click the region name/logo the region page opens.
Resolution: CloudCenter 184.108.40.206 includes a fix to ensure that the region page displays as designed.
CSCvn95716: In some scenarios, when trying to deploy hybrid applications on the second page of the deploy form, the instance types do not load for tiers.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that the instance type loads as designed.
CSCvn56461: When you use the action library with the custom field type as Password under Action definition the password is not decrypted in the scripts on Windows and Linux VMs.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that the password is decrypted as designed.
CSCvn95742: When deploying an application with lifecycle actions on demand and the action had password parameters which were passed as command line argument to a script in the action definition, then the password parameter is being printed to the agent.log in plain text.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that the password is redacted in the log file.
CSCvn83136: Deploying a Windows Data Science VM fails.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that this feature works as designed.
- No labels