Cisco CloudCenter 4.10.0.6 Release Notes

Release Date

First Published: February 11, 2020

Updated:

  • March 13, 2020: Updated the Documentation section to include changed pages.

  • June 10, 2020: Added content to the Applications and Services section.

Installation

CloudCenter 4.10.0.6 is only available as an upgrade for existing customers from CloudCenter 4.10.0.3, CloudCenter 4.10.0.4, or CloudCenter 4.10.0.5. Contact the CloudCenter Support team for additional details.

Upgrade Path

The required upgrade path to use CloudCenter 4.10.0.6 is to first upgrade to CloudCenter 4.10.0.3, CloudCenter 4.10.0.4, or CloudCenter 4.10.0.5.

CloudCenter 4.10.0.6 includes updates to the operating system to address some security vulnerabilities that were found in older version of CentOS 7 Linux kernel (that are currently shipped for CloudCenter 4.10.0 releases). 

  • You  must update these OS/kernels using the new core-upgrade binary files (downloadable from software.cisco.com) to address these vulnerabilities.

  • CloudCenter 4.10.0.6 includes a new os_upgrade option for the core_upgrade.bin file.

  • Use the os_upgrade option option each time you upgrade to CloudCenter 4.10.0.6.

  • You must run the following command to complete any upgrade to CloudCenter 4.10.0.x.

    ./core_upgrade.bin centos7 vmware os_upgrade
  • See Upgrade Overview > CentOS Linux Security Vulnerabilities Addressed in CloudCenter 4.10.0.6 for additional details.

Architecture

You have the option to upgrade to RabbitMQ Version 3.6.16 from 3.6.12.

Clouds

No updates

Applications and Services

You must add the following variable to the /etc/sysconfig/gateway.conf file:

LIFECYCLE_TIER_TERMINATIONINPARALLEL=false 
  • When set to false, then at the time of deployment termination the STOP script is implemented using a top-down approach – the top tier script is called followed by the dependent tier.

  • When set to true (default) the STOP scripts for all the tiers are called in parallel.

CloudCenter Management

The time for the suspend script is now configurable.

  • Prior to CloudCenter 4.10.0.6, the CloudCenter platform only waited for 30 seconds for a suspend script to run, even if the script did not finish, and suspended the node. To address this issue, CloudCenter 4.10.0.6 introduces a new property called max.suspend.script.run.time in the cloudcenter-orchestrator.properties file. This property identifies the time in minutes (default = 1 minute) that the CloudCenter platform waits before initiating the suspend action on that node. Using the max.suspend.script.run.time property, you can configure the time according to how long the suspend script needs to run.

  • As soon as the script completes, the CloudCenter platform detects the suspend script completion and proceeds with suspending the node. A new status NodeSuspendExecuted is introduced in the Agent to communicate the successful execution of the suspend script for a node. Irrespective of which occurs first, either the script completion or the timeout, the nodes will be suspended post that event.

  • See Deployment Lifecycle Scripts for additional details on the suspend script.

Administration and Governance

No updates

Security

No updates

End of Life Notices

See End of Support Notices for additional details.

Deprecated

No updates

CCM UI

No updates

API

No updates

Integrations

No updates. 

Documentation

The following documentation changes were implemented in Workload Manager 4.1.0.0.6:

Known Issues

No updates

Resolved Issues

The following issue was resolved/addressed in CloudCenter 4.10.0.6:

  • CSCvs53037: Fixes for some security vulnerabilities were announced as updates for CentOS 7 Linux kernel that are currently shipped for CloudCenter 4.10.0x releases. 
    Resolution
    : CloudCenter 4.10.0.6, provides core-upgrade binary files that update the CentOS 7  kernel to address these vulnerabilities. You can continue to upgrade components in the same order mentioned in Upgrade Overview > Component Upgrade Order.

  • CSCvs57243: CloudCenter 4.10.0.x does not support deployment of applications running on Ubuntu 18 operating systems.
    Resolution: CloudCenter 4.10.0.6 includes an enhancement to support Ubuntu 18.04. See Operating Systems for an updated list.

  • CSCvr18349: CloudCenter 4.10.0.x does not support deployment of applications running on RedHat 8 operating systems.
    Resolution: CloudCenter 4.10.0.6 includes an enhancement to support RedHat RHEL8. See Operating Systems for an updated list.

  • CSCvr18340: CloudCenter 4.10.0.x does not support deployment of applications running on Windows 2019 Operating systems.
    Resolution: CloudCenter 4.10.0.6 includes an enhancement to support Windows 2019. See Operating Systems for an updated list. This support was available in 4.10.0.5 and is the related documentation pages are being updated in this release.

  • CSCvs71257: The node is suspended even though the node's suspend script is not completely executed. The node was eventually suspended before the script completely finished.
    Resolution: The time for the suspend script is now configurable. Prior to CloudCenter 4.10.0.6, the CloudCenter platform only waited for 30 seconds for a suspend script to run, even if the script did not finish, and suspended the node. To address this dependency, CloudCenter 4.10.0.6 introduces a new property called max.suspend.script.run.time in the cloudcenter-orchestrator.properties file. This property identifies the time in minutes (default = 1 minute) that the CloudCenter platform waits before initiating the suspend action on that node. This procedure requires a CCO restart and a sequential restart for HA environments.

  • CSCvs54058: A service parameter can overwrite an application profile's global parameter if a service parameter has the same name.
    Resolution: CloudCenter 4.10.0.6 includes a UI validation change to prevent global parameters that conflict with service parameters from being configured.

  • CSCvs46717: When a 3-tier (web, application, and database) application uses an auto scaling policy in the web tier and a job is triggered through the Jenkins plugin, the web server is deployed but responds with an error about the scaling policy dependency in the application tier. The application deployment succeeds if the auto scaling policy is removed.
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and 3-tiered applications that use auto scaling policy now deploy successfully when using the Jenkins plugin.

  • CSCvs52571: Make the forwarding logic in the CloudCenter platform robust enough to mark the deployment a failure if it encounters any failures in forward. 
    Resolution: CloudCenter 4.10.0.6 retries the forward after a time interval, the failure of which will result in the deployment being marked a failure.

  • CSCvs53718: When a deployment is terminated in multiple stacks (deployed across multiple regions), the Stop script is not being executed for one of the tiers.
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and the Stop script is now executed as designed.

  • CSCvs31076When the number of applications are high, close to 1000, then the applications listing page fails to load. If the number of services is close to 1000, then service listing and application edit pages fail to load. 
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and the pages in question load as designed.

  • CSCvs47457: The Applications and Services pages do not load if the number of applications and services are more than 800. 
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and the pages in question load as designed.

  • CSCvs47461: Cloning an application issues an error indicating that the upgrade type must be NONE for an external service tier.
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and the application can be cloned as designed.

  • CSCvs25836: When exporting an application profile that uses modified inherited deployment parameter values, the override values are not included in the zip archive. When importing the ZIP bundle, the previously changed deployment parameter values are reset to their original values.
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and exporting application profiles work as designed.

  • CSCvs25438: Parameters passed from a dependent external service are sometimes not available in hybrid cloud deployments.
    Resolution
    : CloudCenter 4.10.0.6 includes a fix to address this issue and the parameter is being passed as designed.

  • CSCvs18698: The CloudCenter Tenant Summary page gets stuck in the loading state when the number of deployments exceed 32000. 
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and the Tenant Summary page loads as designed.

  • CSCvs47458: Request to support the RHEL 8 operating system for worker installers.
    Resolution: CloudCenter 4.10.0.6 includes worker installer support for RHEL8 so that worker1 and worker_full types can be installed.

  • CSCvs47469: Deployments of applications using Windows and IPAM callouts fail with a bootstrap timeout error.
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and deployments of applications using Windows with IPAM callouts deploy successfully.

  • CSCvp56558: When using an external service, the variables passed from start lifecycle action are not available in stop lifecycle action, if the start lifecycle script exits with error
    Resolution: CloudCenter 4.10.0.6 includes a fix to address this issue and variables passed during start lifecycle action are available in stop life cycle action even if start lifecycle action exits with error.



  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks