Cisco CloudCenter 22.214.171.124 Release Notes
September 15, 2017
January 9, 2018 (added a known issue about ACL APIs)
August 1, 2018 (added details on the Upgrade Path)
CloudCenter 126.96.36.199 is available as installer for ALL components for all supported clouds. Contact the CloudCenter Support team for additional details.
You can only upgrade to CloudCenter 188.8.131.52 from CloudCenter 4.6.0 and later releases.
To upgrade to CloudCenter 184.108.40.206, see Upgrade Overview.
The recommended upgrade path if you are using CloudCenter 220.127.116.11 is to upgrade to CloudCenter 4.8.2.
Effective CloudCenter 18.104.22.168, Cisco provides support for Ubuntu 16.04 for Package Store installations.
Applications and Services
Administration and Governance
End of Life Notices
Browser Compatibility: Cisco supports the two latest versions of each browser. See Browser Compatibility for a list of compatible browsers.
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.
CloudCenter 126.96.36.199 has the following known issues:
When an application running a public CentOS image on AWS is terminated, the volume attached to the instance is not cleaned up. To work around this issue, add the volume size in the Root Disk field (Deployments page) depending on the image and cloud (see Manage Instance Types > Root Disk Size).
When you Update ACL Resource Details API does not support the delete permission for Extensions. To work around remove the delete permission from the response of API, before using it in the Update ACL Resource Details API.for an Extension resource, the API returns the delete permission if the user has administrative permission for it. However, the
The following issues were resolved/addressed in CloudCenter 188.8.131.52:
Issue: Managed Disk are not supported for Azure Gov Cloud and resulted in deployment failures (Managed Disk are supported for Azure Gov Cloud from CloudCenter 4.8.1 and later releases).
Resolution: Azure Gov cloud does not support managed disks. A fix included in CloudCenter 184.108.40.206 ensures that only unmanaged disks are used when configuring CloudCenter for Azure Gov Clouds.
Issue: The latest suffix in the image path no longer works in CloudCenter 4.8.1.
Resolution: CloudCenter 220.127.116.11 includes a fix to ensure that this feature works as designed when using the latest suffix in the image path.
Issue: The ipamDealloc script was not being called and it did not contain some parameters when a VM fails deployment. These parameters are required to deprovision the VM. See Callout Scripts for additional context.
Resolution: The CloudCenter platform re-injects the variables and the output from the IPAM script to the IPAM dealloc script in CloudCenter 18.104.22.168 and this feature functions as designed.
Issue: Some users automatically sign in using SSO and may only have email addresses. The owner component used in the VMs page issues a JS error when trying to access these accounts using the first and last name.
Resolution: CloudCenter 22.214.171.124 includes a fix to address this JS error and the VM page loads as designed.
Issue: If a user has exceeded the budget limit, the system still allows this user to attach a storage disk to a running deployment.
Resolution: Effective CloudCenter 126.96.36.199, the Actions Library Attach Volumes action is prevented if a user on a Budget Bundle plan user has exceeded the budget limit quota.
Issue: When the user deploys a job, the cloud cost is not deducted from the user credit if the user is on a budget bundle plan.
Resolution: Effective CloudCenter 188.8.131.52, the cloud cost will be deducted from the user credit for the on a budget bundle plan.
Issue: If a user has a small balance on the budget credit and the hourly cost of the current deployment exceeds this balance, then the current deployment is allowed to proceed.
Resolution: Effective CloudCenter 184.108.40.206, if any deployment results in the budget credit being depleted beyond the hourly cost required, then the CloudCenter platform will not allow that deployment to proceed.
Issue: When upgrading to CloudCenter 4.8.1, the upgrade errored out for a customer as the Node ID was duplicated and as a result the unique index could not be created for this resource.
Resolution: CloudCenter 220.127.116.11 includes a fix to remove the file that caused this error and include another file that drops the Node ID index check, if it exists.
Issue: When using Azure RM on Linux, AgentLite fails to install if using password authentication.
Resolution: CloudCenter 18.104.22.168 includes a fix to correct inject the password into the agent installation script.
- No labels