Cisco Cisco Intelligent Automation for Cloud 4.2 Release Notes
3
Cisco Intelligent Automation for Cloud 4.2 Release Notes
Known Issues
Known Issues
Overwriting of Standards
Problem
When installing or upgrading Cisco IAC4.2, the SC_Common_4-2_Overwrite package overwrites a number of
standards. This is not a problem unless these standards are in use already.
standards. This is not a problem unless these standards are in use already.
Solution
If you have already defined the following standards, you will need to redefine them after installing Cisco Intelligent
Automation for Cloud 4.2.
Automation for Cloud 4.2.
Cloudsync Discover Interval
Discover
Platform Element Types
UCS Director Time Zone
VDC Network Description
VDC Network Topology
VDC Sizes
Potential For OpenStack to Overwrite Path Entered When Managing Volumes
When managing volumes in Cisco IAC 4.2, you enter the physical device path in the Attach Volume to an OpenStack
Instance field. If you leave this field blank, the OpenStack auto-assign feature, if supported, will provide the next
available device automatically. In addition, if you fill in a value which is not the next available device location on an
Instance, the auto-assign feature might use the next available physical device location and not what you actually entered.
It will look correct from the OpenStack UI, but using fdisk -l on the Instance may show a different physical device path.
Instance field. If you leave this field blank, the OpenStack auto-assign feature, if supported, will provide the next
available device automatically. In addition, if you fill in a value which is not the next available device location on an
Instance, the auto-assign feature might use the next available physical device location and not what you actually entered.
It will look correct from the OpenStack UI, but using fdisk -l on the Instance may show a different physical device path.
Problem
The physical device which ultimately is attached to your instance is dependent on OpenStack’s interpretation and might
not be what you actually entered when attaching volumes. In other words, even if you provide a value in the Attach
Volume to an OpenStack Instance field, it is still possible that OpenStack might overwrite your value with next available
device (just as if you’d left the field blank). But in so doing, OpenStack will continue to show the value as you originally
entered it, as if nothing had changed.
not be what you actually entered when attaching volumes. In other words, even if you provide a value in the Attach
Volume to an OpenStack Instance field, it is still possible that OpenStack might overwrite your value with next available
device (just as if you’d left the field blank). But in so doing, OpenStack will continue to show the value as you originally
entered it, as if nothing had changed.
Tip:
To view the actual assigned value, use the fdisk -l command on a Linux Instance.
Solution
No solution is currently available. You need to be aware of this as a possible problem. For more information, see
. Once there, refer to the section on volume attachments
(os-volume_attachments), specifically:
expand Attach Volume ‘detail’
“Name of the device such as, /dev/vdb. Omit this parameter or set it to null for auto-assignment, if
supported. If you specify this parameter, the device must not exist in Guest OS”