Cisco CloudCenter 126.96.36.199 Release Notes
Release Date: February 7, 2018
February 9, 2018: Added additional known issues and addressed redundancy in the Administration and Governance section.
February 13, 2018: Updated additional pages with additional information as identified in the Documentation section, added details on the Spectre and Meltdown impact on CentOS7 and RHEL7 systems in the Security section.
March 16, 2018: Updated additional pages with additional information as identified in the Documentation section
August 1, 2018: Added details on the Upgrade Path.
CloudCenter 188.8.131.52 is available as installer for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.
To upgrade to CloudCenter 184.108.40.206, see Upgrade Overview for additional context.
The recommended upgrade path if you are using CloudCenter 220.127.116.11 is to upgrade to CloudCenter 4.9.0.
Google Cloud's Cross-Project Networking (XPN) is now referred to as Shared VPC.
CloudCenter documentation has changed all textual XPN references to Shared VPC effective this release.
You may see some instances of the older XPN reference – Shared VPC is sometimes abbreviated as XPN in some images.
Replacement instructions to login using Azure UI when registering the required Azure providers.
See Configure an AzureRM Cloud for additional context
Applications and Services
Administration and Governance
(Script execution changes are included in the Resolved Issues section below.)
The Spectre and Meltdown vulnerability can impact CentOS7 and RHEL7 systems. Be sure to run the security patches on the affected CCM servers in your environment.
To verify and/or update a system on which you have installed CloudCenter 4.8.2, follow this procedure.
Identify if the kernel has the following patches installed by issuing these commands.
If the above commands do not output any response, then update the kernel as follows.
Once the kernel is updated, restart the CCM server by executing the following commands.
The restart sequence is important for HA environments. See the HA Mode Backup and Recovery > CCM section for additional details.
Verify that the patches are available in the new kernel by re-issuing the commands specified in Step 1
End of Life Notices
The Payment Profiles feature is deprecated and the corresponding documentation is removed effective CloudCenter 18.104.22.168.
Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.
Support for the following APIC releases:
Cisco APIC, Release 3.0
Cisco APIC, Release 3.1
In addition to the tier name, the firewall rule for an application can be configured to expose that port to any endpoint in the ACI context (VRF). See Security and Firewall Rules for additional details.
This section lists the documentation changes implemented in.
CloudCenter 22.214.171.124 Changes: See the links provided in this section for additional context on documentation for this release.
All pages referring to Tomcat service start, stop, or restart
Upgrade/Migrate (updated based on process changes)
Cloud Nuances (added Azure Pack nuances)
Virtual Appliances (removed CCM SA column)
Backup and Recovery (updated based on process changes)
Policies (changed blackout to blockout)
Configure an OpenStack Cloud (added the Bootable Volume Mapping Required field details)
Enterprise Marketplace (removed reference to hundred applications in the public marketplace section)
Jenkins (updated the file download step)
Database (Required) (updated the wizard path to reflect .sh)
Install Worker on a Linux Image (updated VNC environment variable usage to skip module installation)
Cloud Mapping for Images (updated the cloud mapping screenshot)
Image Permissions (updated the cloud mapping screenshot)
External Service (added Best Practice section)
Update Log Elements (added load balancer note for HA CCO instances)
End of Support Notices (merged the End of Life page with this page)
Configure Image IDs (updated VM template to template as a secondary option for VMware)
VMware Network Settings (added details on datastore requirement for snapshots)
Upgrade Overview (added a note about the core upgrade file not being required for particular upgrades)
Upgrade CCM (added a note about the core upgrade file not being required for particular upgrades)
Worker (Conditional) (added out-of-box service details for Docker and added the FAQ section)
Other Firewall Rules (added Application VM Services section)
Upgrade CCO (Specified the use of HTTP for the agent bundle URL)
CCO - Configure Wizard Properties (Specified the use of HTTP for the agent bundle URL)
Image Launch Permissions (added additional introductory information)
Deployment and VM States (added details on the deploymentMinClusterPercentage parameter)
Application Tier Properties (changed the title from Service Properties to reflect the right context)
Certificate Authentication (removed references to the monitor certificate file as it is no longer used)
Upgrade Monitor/Log Collector (changed the title to include Log Collector and added upgrade note)
Certificate Authentication (removed monitor certificate details)
Deployment Environment Defaults (added Auto Select Cluster and Auto Select Zone details)
Deployments (added Auto Select Cluster and Auto Select Zone details)
CloudCenter-Defined Parameters (added CliqrTier_<job_name>_PUBLIC_IP to the Environment Variables for N-Tier deployments row)
Capacity Management (updated to ensure technical accuracy)
CCO Troubleshooting (added the section)
MongoDB Troubleshooting (added page)
Permission Control (modified the Marketplace section)
Enterprise Marketplace (updated permissions references)
Application Tier Properties (updated for technical accuracy)
Log Collector (Required) (updated to include the first step)
Sub-Tenants (removed payment profile and credit card details)
Financial Overview (removed payment profile and credit card details)
SAML SSO (added list of supported Secure hash algorithms)
AMQP Firewall Rules (modified egress firewall rules for Ports 443 and 8443)
CCO (updated CCO dependency on a Bundle store)
Worker (updated CCO dependency on a Bundle store)
ServiceNow Extensions (updated to CloudCenter 126.96.36.199 release dependency)
CloudCenter 188.8.131.52 has the following known issues:
After upgrading to CloudCenter 184.108.40.206, if the user terminates deployments launched in a previous CloudCenter version, then contracts and filters created by previous deployments are not cleaned up. However, the EPG and the Dynamically created BD/VRF are cleaned up.
The Virtual Machines UI page fails to list the VMs as soon as a deployment is launched. The VMs launched by CloudCenter will show up once the deployment is complete or ends in error.
While creating usage plans, the Plan type dropdown selection in the CCM UI does not change the selection value. To workaround this issue you must disable WalkMe.
Executing any custom action on a VM after CloudCenter is upgraded, may result in a timeout. This issue occurs if RabbitMQ is not completely up and running after the upgrade. Try executing the action again.
The Docker container crashes when deploying a Windows 2016 VM. When the external service script dumps a lot of information, the platform tries to download the execution output, which causes docker container to crash when the output is beyond 50MB. It is recommended to redirect the execution output to a file or suppress it completely, so that the content to be downloaded is less and might not crash the Docker container.
The following issues were resolved/addressed in CloudCenter 220.127.116.11:
Issue: When exporting an application where the name contained a / (slash) character the export ended in an error.
Resolution: CloudCenter 18.104.22.168 provides a fix to accept the / character in exported application names.
Issue: When trying to provision an OpenStack VM, the provisioning may stall if the OpenStack setup is integrated with third-party infrastructure that is not visible to the CloudCenter platform.
Resolution: If your native OpenStack configuration does not support the Create Servers OpenStack API (with bootable volume mapping), then you must select the No Blocked Device Mapping Required for Launch option. You can configure this option in the Bootable Volume Mapping Required field in the CloudCenter Configure Cloud Settings. See Configure an OpenStack Cloud for additional context.
Issue: When using a HA CCO set up if the cloud is deleted on the CCM and re-added with different settings, then the /usr/local/osmosix/etc/gateway_config.properties file is only updated on one of the three CCOs.
Resolution: Effective CloudCenter 4.8.2, the gateway_config.properties is no longer used to store region and CCM information. Instead, this information is stored in the MongoDB cluster which is available in all 3 CCOs.
Issue: If you view the Health Monitor Logs after deleting a cloud, the monitor continues to probe the deleted cloud even if it is not displayed on the CCM.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that the monitor no longer attempts to check on a cloud after it is deleted from the CCM.
Issue: The Tenant ID is required to login to the CloudCenter platform even if the Tenant Domain Name is set for a subtenant.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that the tenant is able to login to the CloudCenter platform without a Tenant ID -- if the Tenant domain name is provided.
Resolution:Effective CloudCenter 188.8.131.52, the entries are stored in the database and this feature functions as designed.
Issue: After a user's admin role is revoked and the user re-logs into the CloudCenter platform, the user continues to have admin privileges and can perform admin tasks.
Resolution: CloudCenter 184.108.40.206 includes a fix to revoke role permissions after this user is removed from a role/group.
Issue: Initial SSO activation of a tenant group requires a CCM reboot.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that the creation of metadata files does not require restarting of CCM while activating SSO for a tenant. The maximum turnaround time for the creation of metadata files is 5 minutes.
Issue: The editing/creating of an application displays images that are not shared with the user but are added to the service being used.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that custom images are not listed for a tenant when creating/editing application profiles or services – if they are not shared with that tenant.
Issue: The password becomes incorrect after deploying a cloned application profile.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that the password is preserved in cloned application profiles.
Issue: Resource placement scripts error out with an invalid JSON format. However the same script works well when using CloudCenter 4.8.0.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that the output of the resource placement scripts specified in functions correctly.
Issue: When launching multi-node deployments, VM cloning takes place at the same time for all nodes. Hence, the IPAM callout scripts trigger at the same time and sends multiple requests to the Infoblox application to request a single IP address for each node. This results in the same IP address being assigned for all nodes.
Resolution: Based on the synchronization assumption for the Infoblox integration, the CloudCenter platform acts as a client, and Infoblox acts as a server. Infoblox server issues cannot be resolved from the CloudCenter client side. This issue can also occur when multiple users submit jobs at the same time.
Issue: The Post VM Stop lifecycle action is not displayed in the cloud region page.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that this action displays as designed in the cloud region configuration.
Issue: Unexpected exception encountered while updating the user balance.
Resolution: CloudCenter 184.108.40.206 includes a fix to correct the timestamp problem that caused this issue in earlier release.
Issue: CCM failed to migrate the vendor properties to the database.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that the vendor properties migration to the CCM database database successfully updates the property values.
Issue: Windows and Linux VMs fail to deploy when using a custom image in AzureRM.
Resolution: CloudCenter 18.104.22.168 includes a fix to ensure that a custom image deploys as designed for AzureRM.
Issue: Windows 2012 application deployment fails when using a NodeInit script present in an application package zip file.
Resolution: CloudCenter 22.214.171.124 includes a fix to ensure that the NodeInit script is honored when referenced from the package.
Issue: Values set from the Configure CCO Wizard Properties for the External Script Executor parameter does not overwrite the default value.
Resolution: CloudCenter 126.96.36.199 includes a fix to ensure that the default value for the External Script Executor parameter is overwritten when configured from the CCO wizard.
Issue: External Service script is not executed from the package folder when using a bundle.
Resolution: CloudCenter 188.8.131.52 includes a fix to ensure that the External Service script is executed from the package folder.
Issue: Docker service parameters change from optional to required when saved.
Resolution: CloudCenter 184.108.40.206 includes a fix to ensure that an edit to the Docker service does not overwrite previously-configured changes.
- No labels