Cisco CloudCenter 4.10.0.7 Release Notes

Release Date

First Published: March 27, 2020

Updated:

  • April 30, 2020: Updated the Documentation section to include a list of pages that were updated.

  • May 4, 2020: Added an upgrade issue to the Upgrade Path section. 

Installation

CloudCenter 4.10.0.7 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 or CloudCenter 4.10.0.6. Contact the CloudCenter Support team for additional details.

Upgrade Path

You must be in a minimum version of CloudCenter 4.10.0.3 to upgrade to CloudCenter 4.10.0.7.

After an OS upgrade, a database replication process may fail. As result, if the master goes down, the slave node will not be able to become the master.

To workaround this issue, see Database Replication Failure.

Architecture

No updates

Clouds

No updates

Applications and Services

No updates

CloudCenter Management

No updates

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.7:

Known Issues

When upgrading from CloudCenter 4.10.0.6 to CloudCenter 4.10.0.7, you may encounter the following error:

cannot create regular file '/usr/lib/jvm/java-8-sun/lib/security/nss.cfg': No such file or directory
Error copying nss.cfg file.

To work around this issue, follow this procedure.

  1. Navigate to the /usr/lib/jvm/ directory.

    # cd   /usr/lib/jvm/
    # ls -la /usr/lib/jvm/
    total 8
    drwxr-xr-x   3 root root 4096 Apr 30 21:18 .
    dr-xr-xr-x. 46 root root 4096 Apr 30 21:18 ..
    drwxr-xr-x   3 root root   16 Apr 30 21:18 java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64
    lrwxrwxrwx   1 root root   64 Apr 30 21:18 java-8-sun -> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/jre
    lrwxrwxrwx   1 root root   21 Apr 30 21:18 jre -> /etc/alternatives/jre
    lrwxrwxrwx   1 root root   27 Apr 30 21:18 jre-1.8.0 -> /etc/alternatives/jre_1.8.0
    lrwxrwxrwx   1 root root   35 Apr 30 21:18 jre-1.8.0-openjdk -> /etc/alternatives/jre_1.8.0_openjdk
    lrwxrwxrwx   1 root root   51 Apr 30 21:18 jre-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64 -> java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64/jre
    lrwxrwxrwx   1 root root   29 Apr 30 21:18 jre-openjdk -> /etc/alternatives/jre_openjdk
  2. Verify the the currently available JDK version and create soft link for it.

    # ln -s java-1.8.0-openjdk-1.8.0.252.b09-2.el7_8.x86_64 java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64
  3. Once jdk8 starts referring to an existing JDK version for the CloudCenter platform, the core_upgrade procedure continues as designed.

    # ./core_upgrade.bin centos7 vmware ccm
    Verifying archive integrity... All good.
    Uncompressing Core Upgrade V 4.10.0.7-SNAPSHOT.............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
    Installing Module: preccm
    Module already installed: preccm
    Installing Module: jdk8
    Installing Module: mgmtpostgres
    Installing Module: mgmttomcatapr 
    Installing Module: unison      
  4. Edit this file to accurately set the PATH variable (if it is incorrect).

    [root@cliqr-centos7-base-image jvm]# cat /etc/profile.d/jdk.sh
     export PATH=$PATH:/usr/lib/jvm/java-8-sun/bin
     export JAVA_HOME=/usr/lib/jvm/java-8-sun

Resolved Issues

The following issue was resolved/addressed in CloudCenter 4.10.0.7:

  • CSCvs81750: The event policy that is supposed to be triggered on job cancellation (termination), gets triggered even when jobs are suspended. This results in a customer receiving a large number of emails as the events are triggered by suspension policy as well.
    Resolution: CloudCenter 4.10.0.7 has a fix that sends an email notification only when jobs are terminated for On Event type is Cancelled.

  • CSCvt31853: Agent creates thousands of connections after it loses the original connection to AMQP.
    Resolution: CloudCenter 4.10.0.7 contains a fix to address this issue and attempted connections that failed are cleaned up.

  • CSCvt59203: The Virtual Machines listing page fails to load at 9k deployments (14k VMs).
    Resolution: CloudCenter 4.10.0.7 contains a fix to address this issue and the Virtual machines listing page loads as designed even when there is a huge number of deployments.


  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks