Workload Manager 5.1.3 Release Notes
First Published: December 20, 2019
December 23, 2019: Updated for technical accuracy.
January 6, 2020: Added the Documentation section to list the modified pages.
January 27, 2020: Updated the Security section for technical accuracy.
February 7, 2020: Included Ubuntu 18.04 support.
February 11, 2020: Updated the Documentation section to include recently-modified pages.
March 31, 2020: Additional support for Windows Server 2019
CloudCenter Suite 5.1.3 is available as an upgrade for existing customers from Workload Manager 5.1.0, Workload Manager 5.1.1, or Workload Manager 5.1.2.
CloudCenter 5.1.3 includes an enhancement to support Ubuntu 18.04. See OOB Logical Images for an updated list.
Backup and Restore
Workload Manager: You can upgrade to Workload Manager 5.1.3 via the Suite Admin UI. See Update Module for additional details.
If you upgrade the Workload Manager, you must also upgrade the Cost Optimizer and vice versa as both modules use shared components.
The recommended upgrade path is from CloudCenter Suite 5.0.3 to CloudCenter Suite 5.1.0. You can then upgrade Workload Manager to Workload Manager 5.1.1, Workload Manager 5.1.2, or directly to Workload Manager 5.1.3 as identified in the Update Module section.
There are no architecture changes for Workload Manager 5.1.3.
Workload Manager 5.1.3 includes support to launch applications on Windows 2019 servers. See OOB Logical Images for additional details.
Services, Applications, and Deployments
Workload Manager 5.1.3 includes support to launch applications on Windows 2019 for AWS, AzureRM, GCP, and VMWare clouds.
Administration and Governance
This release addresses security vulnerabilities by upgrading OS libraries and disabling the following protocols in the Workload Manager pages:
TLS v1.0 usage
The Cloud Remote 5.1.2 component will continue to work with Workload Manager 5.1.3. However, to avoid security issues, it is best to upgrade Cloud Remote to this latest Workload Manager 5.1.3 release.
End of Life Notices
You may be using Python 2.7 for any of the following tasks:
To write external service scripts
To dynamically bootstrap a VM
To customize Docker images for scripts
To write callout scripts for VM naming or IPAM address allocation
If you are using Python 2.7, be aware that support officially stops on January 1, 2020. See https://www.python.org/dev/peps/pep-0373/ for additional details.
As a result, consider migrating the above scripts and code to Python 3.4 before the deadline. CloudCenter Suite will deprecate Python 2.7 in an impending release.
The following sections were updated for technical accuracy:
Deployment Parameters (added the Understanding Service and Deployment Parameters section)
Using Parameters (added a reference to the Deployment Parameters page due to the related content)
Cloud Remote (Conditional) (added a troubleshooting tip on network usage and new sections for Static IP Usage and Using Non-Conflicting Networks)
ServiceNow Extensions (added the list of events that trigger CMDB updates)
When you zip a script to a package and use that package for an application profile, then the node init script does not work if it reboots the VM. The workaround, for now, would be to specify the Node Init script using a Repo or URL (File in Package).
The following issues were resolved in Workload Manager 5.1.3:
CSCvr11316: Windows Server provisioning 2019 is not supported in Workload Manager 5.1.x.
Resolution: Windows Server 2019 provisioning support is available on AWS, Azure RM, GCP, and VMware clouds.
CSCvr28436: Support for Windows 2019 worker.
Resolution: Workload Manager 5.1.3 includes support for Windows 2019 worker.
CSCvr37709: Global parameters drop-down menu in App deployment flow does not allow typing to filter the parameters.
Resolution: Workload Manager 5.1.3 includes a fix that allows typing to filter the parameters.
CSCvr94955: When you zip your script to package and refer to that package from node initialization script, the script execution fails.
Resolution: The node initialization custom script is deleted after the script is used due to security reasons. So, when the package is used during a reboot, the node initialization fails as the custom script is not available. Workload Manager 5.1.3 includes a fix that deletes the custom script after the node initialization phase is complete.
CSCvr96014: In the Global Parameters tab for an application profile, the range for the Parameter Type field of type number must be increased from 6 digits to accommodate 12 to 16 digits to enter use phones numbers and account numbers.
Resolution: In Workload Manager 5.1.3, the field has been updated to accommodate 15 digits for all parameter types.
CSCvs04138: When migrating from CloudCenter 4.10.0.x to Workload Manager 5.1.1 or Workload Manager 5.1.2, the Agent service upgrade fails on workers that are installed with McAfee Antivirus.
Resolution: The Agent's service name is similar to the McAfee Antivirus service name. Effective with Workload Manager 5.1.3, the agent name has been renamed to ccc_agentd.
CSCvs16061: Download from a repository fails if the repository access is username and password-based and if the username and password contains special characters.
Resolution: Workload Manager 5.1.3 has a fix that allows using a repository configured with a username and password having special characters.
CSCvs42251: Unable to create a docker-based container profile on CloudCenter Suite.
Resolution: When adding an Application Profile to a docker tier, the dropdown does not show the corresponding docker repositories. Workload Manager 5.1.3 contains a fix that displays the docker repositories.
- No labels