Cisco CloudCenter 220.127.116.11 Release Notes
First Published: December 12, 2019
December 13, 2019: Updated for technical accuracy
January 7, 2020: Added the Documentation section to include a list of pages that were updated.
May 1, 2020: Updated the second bullet for the CSCvq67564 issue below
CloudCenter 18.104.22.168 is only available as an upgrade for existing customers from CloudCenter 22.214.171.124 or CloudCenter 126.96.36.199. Contact the CloudCenter Support team for additional details.
The required upgrade path to use CloudCenter 188.8.131.52 is to first upgrade to CloudCenter 184.108.40.206 or CloudCenter 220.127.116.11.
Applications and Services
CloudCenter 18.104.22.168 supports the use of Windows 2019 operating systems for deployments.
Administration and Governance
End of Life Notices
Effective 22.214.171.124, WalkMe is not available in the CloudCenter UI. The CloudCenter documentation provides the required details for procedures and workflows.
The following documentation changes were implemented in Workload Manager
The following issue was resolved/addressed in CloudCenter 126.96.36.199:
CSCvq67564: During suspend or resume action some jobs get stuck in the JobSuspending or JobResuming states even when the nodes are appropriately suspended or resumed.
Resolution: To avoid this issue, CloudCenter 188.8.131.52 introduces a new scheduler which automatically changes the job status based on the node status. This new scheduler runs at 3:00 am each day and uses the DEPLOYMENT_STATUS_STUCK_TIME parameter:
The scheduler, by default, picks jobs that are stuck in the JobSuspending or JobResuming states for more than or equal to 24 hours.
You can add/edit the /etc/sysconfig/mgmtserver.conf file and add this value. The value for this parameter is, by default, set to DEPLOYMENT_STATUS_STUCK_TIME=24 and this parameter accepts values greater than or equal to 2.
If you provide a value that is less than 2, then by default 2 is assigned by the system.
The node status of the jobs should be the same – otherwise, the automatic status update is not executed by this scheduler. For example, if a job has two nodes and the job is stuck with a JobSuspending state, but the nodes are not in same state, that is – one node is in a NodeReady state and another node is in a NodeSuspended state, then the system skips this situation and informs the user with a log message.
CSCvr94941: In some circumstances, after a deployment is suspended and resumed several times, the resume will fail and the deployed VM is terminated.
Resolution: CloudCenter platform 184.108.40.206 provides a fix to only display the error in the resume script if any, within the task logs. For errors in the resume script, it does not move the job to the JobError state. Additionally, if a job is in an error state then it will not be cleaned up by the scheduled purge that runs every 24 hours.
CSCvr98760: In some circumstances, after a deployment is suspended and resumed multiple times, the resume operation fails and the deployed VM is terminated.
Resolution: CloudCenter platform 220.127.116.11 includes a fix to send an error message for each NodeUpdated status even if some failures occur on Resume action execution by agent on the worker.
CSCvr74273: The CloudCenter platform was hitting condition where two complete events coming from different regions are hitting the dependent tier at the same time. Which was causing the top tier script to be executed twice.
Resolution: CloudCenter platform 18.104.22.168 includes a fix to ensure that the top tier script is only executed once in such scenarios.
CSCvr67014: For VMs in deployments on VMware cloud, attaching a new volume, changes the SDRS Automation Level from Fully Automated to Disabled state.
Resolution: CloudCenter platform 22.214.171.124 includes a fix to ensure that the SDRS Automation Level of the VM is preserved when an Attach Volume action is performed.
- No labels