Cisco UCS Director Release Notes, Release 5.5
Available Languages
Contents
- Cisco UCS Director
- Revision History
- System Requirements
- Installation and Upgrade Notes
- Supported Upgrade Paths to Cisco UCS Director, Release 5.5
- Supported Upgrade Paths to Cisco UCS Director, Release 5.5 (0.1)
- Supported Upgrade Paths to Cisco UCS Director, Release 5.5 (0.2)
- New and Changed Features
- New and Changed Features in Release 5.5
- New and Changed Features in Release 5.5(0.1)
- Updated Support in Release 5.5
- Deprecation Announcement
- Deprecation Announcement for Cisco UCS Invicta
- Workflow-Related Changes
- Workflow Task Changes in Release 5.5
- Open and Resolved Bugs
- Open and Resolved Bugs in Release 5.5
- Open Bugs in Release 5.5
- CSCva11002 - Restriction on Success Link of a Workflow Task
- Resolved Bugs in Release 5.5
- Open and Resolved Bugs in Patch Release 5.5(0.1)
- Open Bugs in Release 5.5(0.1)
- Resolved Bugs in Release 5.5(0.1)
- Open and Resolved Bugs in Patch Release 5.5(0.2)
- Open Bugs in Release 5.5(0.2)
- Resolved Bugs in Release 5.5(0.2)
- Related Documentation
- Obtaining Documentation and Submitting a Service Request
First Published:
Last Updated:
Text Part Number:
Cisco UCS Director
Cisco UCS Director delivers unified, highly secure management for supported compute, network, storage, and virtualization platforms and for the industry's leading converged infrastructure solutions, which are based on the Cisco Unified Computing System (Cisco UCS) and Cisco Nexus platforms. Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to provide data center administrators with comprehensive visibility and management capabilities for compute, network, storage, and virtualization. For more information, see Cisco UCS Director on Cisco.com.
Revision History
System Requirements
The system requirements for this release are available in the Cisco UCS Director installation and upgrade guides for the following:
Supported Browser Versions
Cisco UCS Director supports the following browsers:
For HTML-5
Internet Explorer 8 or higher
Firefox 12 or higher (PC and Apple MAC)
Safari 6 or higher
Google Chrome 18 or higher
Opera 12 or higher (PC and Apple MAC)
For Classic View - all browsers must have Adobe Flash Player 11 plug-in or higher
Installation and Upgrade Notes
Cisco UCS Director uses a standard virtual machine that is delivered in OVF format for VMware, and in VHD format for Microsoft Hyper-V. It can be hosted on VMware vSphere or vCenter, or on Microsoft Hyper-V Manager. For installation instructions, see the appropriate Cisco UCS Director installation guide.
Cisco UCS Director, Release 6.5 is installed on two disks in the virtual machine (VM). The primary disk (Hard Disk 1) hosts the operating system and the Cisco UCS Director application. The secondary disk (Hard Disk 2) hosts the Cisco UCS Director database. For information on the system requirements for both these disks, see the Cisco UCS Director installation guide or the Cisco UCS Director Upgrade Guide.
Note
Cisco UCS Director OVF and VHD zip files are created using zip 3.x in CentOS 6.x. For Linux systems, you can extract the zip files with unzip 6.x or higher or with the latest version of the 7-Zip archiving tool. For Windows systems, you can extract the zip files with the native Extract All in Windows Explorer for Windows 10 and Windows Server 2012 or with the latest versions of archiving tools such as 7-Zip or WinRAR.
Note
After you apply the upgrade patch and complete that installation, choose the Start Services option of ShellAdmin to start/restart the Cisco UCS Director services and complete the patch process. The patch process is not complete or successful until the services have started, Cisco UCS Director is available, the login screen is displayed, and the admin user can log in.
All Cisco UCS Director services must be stopped before you perform other ShellAdmin procedures, such as apply additional patches, take a database backup, or restore a database from a backup.
Supported Upgrade Paths to Cisco UCS Director, Release 5.5
The following are the supported upgrade paths for Cisco UCS Director, Release 5.5:
Upgrade Paths from Release 5.4(x.x) Platform
From Release 5.4 to Release 5.5
From Release 5.4(0.1) to Release 5.5
From Release 5.4(0.2) to Release 5.5
From Release 5.4(0.3) to Release 5.5
From Release 5.4(0.4) to Release 5.5
Important:Upgrading Cisco UCS Director to release 5.5 from versions prior to release 5.4 is not supported.
Supported Upgrade Paths to Cisco UCS Director, Release 5.5 (0.1)
The following are the supported upgrade paths for Cisco UCS Director, Release 5.5 (0.1):
Important:Upgrading Cisco UCS Director to release 5.5(x.x) from versions prior to Release 5.4 is not supported.
Supported Upgrade Paths to Cisco UCS Director, Release 5.5 (0.2)
The following are the supported upgrade paths for Cisco UCS Director, Release 5.5 (0.2):
Important:Upgrading Cisco UCS Director to release 5.5(x.x) from versions prior to Release 5.4 is not supported. You must first upgrade to the most recent Release 5.4 patch.
Upgrade Paths from Release 5.5(x.x) Platform
From Release 5.5 to Release 5.5(0.2)
From Release 5.5(0.1) to Release 5.5(0.2)
Upgrade Paths from Release 5.4(x.x) Platform
From Release 5.4 to Release 5.5(0.2)
From Release 5.4(0.1) to Release 5.5(0.2)
From Release 5.4(0.2) to Release 5.5(0.2)
From Release 5.4(0.3) to Release 5.5(0.2)
From Release 5.4(0.4) to Release 5.5(0.2)
Important:When you upgrade from Cisco UCS Director version 5.3 or a prior version to version 5.5 or later, all tasks that previously took input from the VMware Provision Inputs task will fail. The failure occurs because the VMware Provision Inputs task been deprecated and replaced by the VMware VM Provision Inputs task. This change also affects the VMware VM Provision task, which previously worked in conjunction with the VMware Provision Inputs task. To avoid this failure, you must use the VMware VM Provision Inputs tasks as input after the upgrade.
Although the VMWare Provision Inputs task is deprecated, it is available in the Obsolete Tasks folder in the user interface.
New and Changed Features
This section provides an overview of the significant new and changed features in this release. This section does not provide an exhaustive list of all enhancements included in this release.
Note
For information about the physical and virtual devices and software supported by Cisco UCS Director in this release, see the Compatibility Matrix for this release.
New and Changed Features in Release 5.5
Enhancements to Cisco UCS Manager Support
The following changes were added to Cisco UCS Manager support in this release:
Support for up to 10 vNICs and 10 vHBAs for Create UCS Service Profile, Create UCS Service Profile from Template and Select UCS Service Profile task outputs.
Documented in the Cisco UCS Director Management Guide for Cisco UCS Manager, Release 5.5.
Enhancements to Cisco UCS Central Support
The following changes were added to Cisco UCS Central support in this release:
Add VLAN to Global Service profile
Delete VLAN from Global Service profile
Add vHBA to Global Service profile
Delete vHBA from Global Service profile
Modify VLAN Org permissions
Delete VLAN from Global vNIC Template
Add vNIC to Global Service Profile
Bind Global Service Profile vNIC to Template
UnBind Global Service Profile vNIC from Template
Support for up to 10 vNICs and 10 vHBAs for global service profile.
Documented in the Cisco UCS Director Management Guide for Cisco UCS Central Release 5.5.
Enhancements to VMAX Management
The enhancements to VMAX management include support for the following:
Support for EMC XtremeIO Connector
The XtremIO connector allows you to monitor and manage the XtremIO volumes, initiator groups, LUN mappings, snapshots, and basic network configurations. It connects through the HTTPS protocol. In order to manage XtremIO in Cisco UCS Director, the XMS Host IP is used when adding a physical account.
Documented in the Cisco UCS Director EMC XtremIO Management Guide, Release 5.5.
Enhancements to NetApp Management
The enhancements to managing NetApp accounts in Cisco UCS Director include support for the following:
Managing SnapVault Relationships
SnapVault is a backup solution that is exclusively used to archive data. Cisco UCS Director allows you to manage the SnapVault relationships for both cluster-mode and ONTAP accounts.
Documented in the Cisco UCS Director NetApp Management Guide, Release 5.5.
Enhancements to VMware Management
The enhancements to VMware management in Cisco UCS Director include support for the following:
Support for multiple datacenter and clusters when adding a VMware vCenter account—You can discover and add multiple VMware vCenter datacenter and associated clusters when adding a VMware vCenter account. Cisco UCS Director does not support the creation of clouds that use the same vCenter account. If there are duplicate accounts, you cannot create a VMware Cloud. In addition, if there are duplicate accounts, VM provisioning fails and an error appears in the status for the virtual account. The Test Connectivity function also fails with the error message. This error also occurs if the same server with the same combination of clusters is used in different clouds.
ISO Image Inventory Report—Cisco UCS Director provides the ability to view collective information about ISO image inventory through the ISO image inventory report.
USB device support through VMRC console—Cisco UCS Director provides the ability to connect and disconnect a USB device through the VMRC console.
Support for standalone VMRC plug-in—System administrators can launch a VMRC enabled web browser from a standalone VMRC plug-in.
Ability to unconfigure the VNC console—Cisco UCS Director provides the ability to unconfigure the VNC console on a VM. This action disables VNC on the selected VM and releases the assigned port.
Ability to enable DRS and HA on a Virtual SAN Cluster—Cisco UCS Director provides the ability to enable HA and VMware Distributed Resource Scheduler on a new or existing Virtual SAN Cluster
Support for expanding Virtual SAN Clusters from Baremetal inherits RAID Mode and MTU size from the initial cluster configuration—By default, the RAID mode and MTU size values are automatically populated from the values selected during the initial cluster configuration.
Virtual SAN VDC creation wizard supports selection of existing or creation of new policies —In the Virtual SAN VDC creation wizard, you can now select an existing or create a new system, computing, and networking policy for the Virtual SAN cluster.
Changes to the UCS Service Profile Template Compliance Report—The Create Virtual SAN Cluster dialog provides a compliance report in the summary to verify if all UCS service profile template pre-requisites are configured properly.
Support for Virtual SAN UCS Service Profile Template Reports—Cisco UCS Director provides the ability to view Virtual SAN UCS Service Profile Template information, as well as local disk configuration policy, boot policy, vNIC, scrub policy and BIOS policy details.
Documented in the Cisco UCS Director Administration Guide, Release 5.5 and the Cisco UCS Director VMware vSphere Management Guide, Release 5.5
Enhancements to Microsoft Virtualization Support
The enhancements to Microsoft virtualization support in Cisco UCS Director include support for the following:
Application Profile and Application Container Support for Hyper-V—You can provision an application container in an Hyper–V or ACI environment.
Resource group support for Hyper-V account—Choose a Hyper-V account and set the environment variable, capabilities, and capacities according to the chosen Hyper-V account.
Clone VM action—You can use the Cisco UCS Director application to clone a VM to make a new VM with similar qualities.
Addition of the HyperV Basic VM Provision task—You can use this task to provision a VM in a container environment.
Adding and Editing a vNIC for a Hyper-V VM—You can add or edit a vNIC for a VM.
Hyper-V deployment policy provides the option to use previously provisioned VM names and host names—When adding a Hyper-V deployment policy, you can choose to recycle VM names and host names. By default the check boxes are selected and Cisco UCS Director reuses previously used VN names and host names if the VM has been decommissioned.
Enhancements to RedHat KVM Virtualization Support
The enhancements to RedHat KVM management in Cisco UCS Director include support for the following:
Enhancements to F5 Load Balancer Support
The enhancements to F5 Load Balancer management in Cisco UCS Director include support for the following:
Support for F5 BIG-IP load balancer traffic groups and enhanced device reports—Cisco UCS Director provides the ability to view F5 BIG-IP load balancer device group, device information, traffic group, virtual address, and HA group reports. You can create, modify, and delete device groups and traffic groups. You can also force a traffic group into a standby state. You can update the traffic group for an existing virtual address by selecting the traffic group, or inheriting the traffic group from the current partition or path. When creating or modifying application services, you can specify the device group and traffic group.
Documented in Cisco UCS Director F5 Management Guide, Release 5.5.
Enhancements to Orchestration Capabilities
The following changes were made to the orchestration capabilities:
Rollback can be disabled for a task in a workflow—When creating or editing a workflow, you can disable rollback of any or all tasks in the workflow.
A cancelled service request can be resubmitted—You can now resubmit a service request that was cancelled in the same manner that you can resubmit a failed service request.
Define default values for task user inputs— While editing or creating a workflow, when defining a user input you can supply a default value. The user chooses at runtime whether to override or accept the default.
Delete multiple user inputs— While you are editing or cloning a workflow, more than one user input can be deleted at a time.
You can view deleted service requests.
Documented in Cisco UCS Director Orchestration Guide, Release 5.5.
Support for Cisco UCS Director Express for Big Data in Cisco UCS Director
The enhancements to Cisco UCS Director Express for Big Data in Cisco UCS Director include the following:
Updated menus and options for navigation.
Changes to configuring and deploying a Hadoop cluster deployment template.
Support for adding a Splunk account
Changes to configuring Cisco UCS Service Profile Templates for Big Data
Changes to the Hadoop Cluster configuration settings
Documented in the Cisco UCS Director Express for Big Data Management Guide, Release 2.1.
Enhancements to APIC Management
The following changes were introduced to APIC management in this release:
Addition of the Hyper-V related object in the Tenant Resource Allocation task—helps with populating a vPOD.
Support for generic tenant onboarding—You can create your own tenant onboarding workflow based on the topology configuration by adding the mandatory tasks - Create UCSD Tenant, Tenant Resource Allocation, and Tenant Container Association.
Resource group support for Hyper-V account—Choose a Hyper-V account and set the environment variable, capabilities, and capacities according to the chosen Hyper-V account.
Shared Layer 3 Outside (L3Out) support—Configure shared L3Out support. Shared L3Out can be configured with both VMware and Hyper-V generic tenants. This includes support for unique IP pools.
Custom environment variable support—Define an environment variable that can be used in resource groups and workflows.
Support for multiple context Cisco ASA device—Add multiple context Cisco ASA device.
Support for choosing multiple tag values while adding datastore tags in the virtual storage service class level.
Update private tenant—Update the vPOD information with multiple data stores and multiple data store clusters for a tenant using the Update Tenant vPOD with Existing Resources workflow.
Overlapping IP address support—Enable the IP address overlapping for the tiers.
Automatic data store selection in the tenant onboarding with private networks workflow—Choose data stores and data store clusters based on the generic VMware cluster.
Documented in the Cisco UCS Director APIC Management Guide, Release 5.5.
Enhancements to Application Containers
The enhancements to application containers in Cisco UCS Director include support for the following:
Support for Hyper-V—You can perform container provisioning in the Hyper–V environment.
Loadbalancer vServer Support—The application container has the ability to view, add, or delete the load balancer L4-L7 services. The newly created VMs are added as real servers to the L4-L7 service. This support is available for VMware and Hyper-V application containers.
Introduction of VM names—Specific naming convention is followed for VM names when an application is provisioned for a private network or when adding VMs to an APIC container.
Support for Multi-Context Configuration—Layer 4 to Layer 7 policy accommodates multiple contexts configurations on the ASA devices.
Support for advanced load balancer parameters—Network device system parameter policy sets the NTP and SNMP parameters that are needed to be configured on a load balancer device.
Dynamic Subnet Size per Tier—The maximum number of VM instances per tier allows you to determine the subnet size for each tier.
Support for Tags in Datastore—You can choose tag values for each tier. During container provisioning, resources are selected based on the tag associated with the tier.
Shared L3Out Feature—To integrate the ACI fabric with shared external Layer 3 network. The network must be tagged and updated on Tenant vPOD in advance and the same tag must be selected for the external network in case of shared L3Out. Shared L3Out can be configured with both VMware and Hyper-V generic tenants.
Support for viewing and adding contracts between different containers—You can view and add the contract between tiers of different containers in Cisco UCS Director. You need to drill down each contract to view all the security rules created for each application container in Cisco UCS Director.
Adding a vNIC to a Container VM—You can add a vNIC to the container VM for private network communication between VMs belonging to same network zone.
Container shows the Virtual Routing and Forwarding instance—Added the Virtual Routing and Forwarding (VRF) instance in the Tier summary of the Container report.
Documented in the Cisco UCS Director Application Container Guide, Release 5.5.
Enhancements to Network Devices Support
The following changes were introduced to network devices management in this release:
Support for Smart Zoning—Allows you to enable smart zoning for network devices that run Cisco NX-OS. You can tag the device type that serves as labels for smart zoning.
Support for Device Aliases in the Add SAN zone task.
Addition of the FCNS database into inventory report.
New workflow tasks
Documented in the Cisco UCS Director Network Devices Management Guide, Release 5.5.
Enhancements to REST APIs
The following changes were introduced to REST APIs in this release:
Capability to download the REST API SDK bundle from Cisco UCS Director.
Support for retrieving VDC resource limits with the addition of the userAPIGetVDCResourceLimits API.
Support for retrieving the cost model with the addition of the userAPIGetCostModel API.
Support for managing virtual infrastructure policy with the following APIs:
Support for managing APIC virtual infrastructure policy with the following APIs:
Support for adding a Virtual Network Interface Card (vNIC) to a VM with the userAPIAddVMNICs API.
Support for managing VMware system policy with the following APIs:
Support for retrieving output of a service request with the userAPIGetServiceRequestOutputDetails API.
Support for retrieving the input and output fields of a workflow with the following APIs:
Support for toggling the MSP mode with the userAPIToggleMspMode API.
Support for viewing resource usage report with the userAPIGetResourceUsageCostSummary API.
Support for viewing tabular reports with the userAPIFilterTabularReport API.
Documented in the Cisco UCS Director REST API Getting Started Guide, Release 5.5 and the Cisco UCS Director REST API Cookbook, Release 5.5.
Enhancements to Open Automation
The following changes were introduced to Open Automation in this release:
Support for downloading the open automation SDK bundle from Cisco UCS Director.
Support for importing the open automation SDK bundle into Eclipse from the Git repository.
Documented in the Cisco UCS Director Open Automation Getting Started Guide, Release 5.5.
Support for Cisco IMC Supervisor
For C-Series standalone servers, native support is now available for Cisco IMC Supervisor 2.0 features.
Documented in the Cisco UCS Director Management Guide for Rack Servers, Release 5.5.
Changes to Bare Metal Agent Installation and Configuration
The changes to the Bare Metal Agent (BMA) installation and configuration includes the following:
The Additional Parameters text box has now been changed to specify tabular inputs for the parameter name and its corresponding single-line value. You now have the option to add multiple parameters for a PXE task. You also have the options to edit, modify, or delete the parameters.
The Network Configuration field has been removed from the PXE boot tasks, as the network configurations can now be added using the Additional Parameters field.
Documented in the Cisco UCS Director Bare Metal Agent Installation and Configuration Guide, Release 5.5.
Enhancements to NetApp Support
The following change was made to NetApp support:
Documented in the Cisco UCS Director NetApp Management Guide, Release 5.5.
Changes to Multi-Node Configuration Options
The changes to the multi-node configuration includes the following:
The multi-node configuration shelladmin options now include the deployment type option as well. You can directly chose the deployment type: small, medium, or large. This eliminates the need for administrators to manually configure the system settings whenever small, medium, or large multi-node deployments are added.
Documented in the Cisco UCS Director Multi-Node Installation and Configuration Guide, Release 5.5.
Additional Enhancements to Cisco UCS Director
Other enhancements to Cisco UCS Director include the following:
Support for setting language preference for users
Introduction of the Create Service Request option for users
Support for viewing user role information
Support for full-length and half-length physical servers in resource limits
Support for multiple profiles for LDAP users
Introduction of a tree view that depicts hierarchical structure of organizational units, groups and users.
New navigation to access LDAP information in user interface
Support for generating API logs
Support for overlapping IP addresses in pool policies
Addition of the following fields in the VM Management policy:
Changes while assigning an application category to multiple VDCs
Support for cloning a VM from a selected image.
Ability to control service end users from configuring lease time and VM provisioning.
Ability to conduct an assessment before creating a service request with a standard catalog.
Support for specifying the number of physical disks to be created during VM provisioning while creating a storage policy
Support for unconfiguring the VNC Console on a VM. This action disables VNC on the selected VM and releases the assigned VNC port.
Documented in the Cisco UCS Director Administration Guide, Release 5.5.
Updated Support in Release 5.5
This section provides a summary of the updated support in Release 5.5. For more information, see the Cisco UCS Director Compatibility Matrix, Release 5.5.
VMware Virtualization Support
The following changes were added to VMware virtualization support in this release:
Microsoft Virtualization Support
The following changes were added to Microsoft virtualization support in this release:
Baremetal Operating System Support
The following changes were added to baremetal operating system support in this release:
Cisco Network and Fabric Support
The following changes were added to Cisco network and fabric support in this release:
Cisco Nexus 1000V for VMware vSphere: NX-OS, Release 5.2(1)SV3(1.6), 5.2(1)SV3(1.10), and 5.2(1)SV3(1.15)
Cisco Nexus 3172: NX-OS, Release 7.0(3)I2(2a)
Cisco Nexus 5648Q: NX-OS, Release 5.2(1)N1(8b), 5.2(1)N1(9), and 7.2(1)N1(1)
Cisco Nexus C5624Q, 5672UP and 5696Q: NX-OS, Release 7.2(1)N1(1)
Cisco Nexus 7010 and Supervisor 1: NX-OS, Release 6.2(14)
Cisco Nexus C9516, 9396PX, and 9504: NX-OS, Release 7.0(3)I2(2a)
Cisco Nexus 93120: NX-OS, Release 7.0(3)I2(2)
Cisco Nexus 93128: NX-OS, Release 7.0(3)I2(1a)
Cisco MDS 9148 and 9148S: NX-OS, Release 6.2(13a)
Cisco MDS 9706: NX-OS, Release 6.2(9a)
Cisco Application Centric Infrastructure Support
The following changes were added to Cisco Application Centric Infrastructure support in this release:
Brocade Network and Fabric Support
The following changes were added to Brocade network and fabric support in this release:
F5 Network and Load Balancer Support
The following changes were added to F5 network and load balancer support in this release:
Cisco Security and Firewall Support
The following changes were added to Cisco security and firewall support in this release:
Deprecation Announcement
Workflow-Related Changes
Workflow Task Changes in Release 5.5
The following describes the workflow task changes in this release and the impact they may have, if any, on your existing workflows.
Workflow Task
What Has Changed
Workaround to Resolve Issue
Identify Virtual Network Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
Identify Physical Network Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
Identify Virtual Compute Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
Identify Physical Compute Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
Identify Virtual Storage Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
ResourceGroupFieldLable Constants.
RG_RESOURCE_ALLOCATION_TO
_TENANT
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
Identify Physical Storage Resources
For this workflow task, the user-input identity type has been modified from Generic-text-input to Resource Group Service Offering.
Open the task and change the input field
ResourceGroupFieldLableConstants.
RG_TENANT_CREATION
In release 5.4, this workflow task was named as Mapping Tenant with Tenant Profile. After upgrading to this release, this workflow task is no longer available. In release 5.5, this workflow task is renamed as Create UCSD Tenant.
No workaround
Get Free IP Subnet From Subnet Pool Policy
This task is deprecated in this release.
No workaround
VMware Provision Inputs
This task is deprecated in this release.
Use the VMware VM Provision Inputs task
Open and Resolved Bugs
The open and resolved bugs for this release are accessible through the Cisco Bug Search Tool. This web-based tool provides you with access to the Cisco bug tracking system, which maintains information about bugs and vulnerabilities in this product and other Cisco hardware and software products.
Note
You must have a Cisco.com account to log in and access the Cisco Bug Search Tool. If you do not have one, you can register for an account.
For more information about the Cisco Bug Search Tool, see the Bug Search Tool Help & FAQ.
Open and Resolved Bugs in Release 5.5
Open Bugs in Release 5.5
You can find detailed information about all open bugs in Release 5.5 through the open bug search for Release 5.5. This search uses the following parameters:
CSCva11002 - Restriction on Success Link of a Workflow Task
CSCva11002 is an open bug in Cisco UCS Director, Release 5.5 that is caused by a new restriction in orchestration, as follows:
New Restriction Added
In Release 5.5, a new restriction/limitation has been introduced that impacts orchestration workflows. In the Workflow Designer, you cannot map the Success link of a workflow task to Completed(Failure).
Issues Caused by this Restriction
This restriction causes the following issues with workflows:
After an upgrade, workflows show as invalid if they include one or more tasks with the Success link of a workflow task mapped to Completed(Failure).
Imported workflows show as invalid if they include one or more tasks with the Success link of a workflow task mapped to Completed(Failure).
In new workflows, you cannot map the Success link of a workflow task to Completed(Failure).
Impact
This restriction has the following impact on workflows:
You will see the following validation error: OnSuccess link cannot be connected to Completed (Failed)
There is no functionality impact. Although you see this validation error, you can still execute the workflows.
Due to this validation error, if you delete these links, you cannot restore them in Release 5.5.
Note
Even though you see this validation error when you open the workflow in Workflow Designer, the link from Success to Completed(Failure)) still exists. Please DO NOT remove that link to make the workflow valid.
Workaround
If you delete the links to fix the validation issue, you can add a custom task that will always result in a failure and place it after the task that was pointing to the Completed(Failure) and caused the validation error. You can map this custom task according to the current behavior of pointing it to Completed(Success) for the success link and Completed(Failure) for the failure link.
Resolved Bugs in Release 5.5
You can find detailed information about all resolved bugs in Release 5.5 through the resolved bug search for Release 5.5. This search uses the following parameters:
Open and Resolved Bugs in Patch Release 5.5(0.1)
Open Bugs in Release 5.5(0.1)
You can find detailed information about all open bugs in Release 5.5(0.1) through the open bug search for Release 5.5(0.1). This search uses the following parameters:
Resolved Bugs in Release 5.5(0.1)
You can find detailed information about all resolved bugs in Release 5.5(0.1) through the resolved bug search for Release 5.5(0.1). This search uses the following parameters:
Open and Resolved Bugs in Patch Release 5.5(0.2)
Open Bugs in Release 5.5(0.2)
You can find detailed information about all open bugs in Release 5.5(0.2) through the open bug search for Release 5.5(0.2). This search uses the following parameters:
Field
Parameter
Product drop-down list
Choose Series/Model and enter Cisco UCS Director 5.5.
Releases drop-down list
Choose Affecting or Fixed in these Releases and enter 5.5(0.2).
Filter
Choose Open from the Status drop-down list.
Resolved Bugs in Release 5.5(0.2)
You can find detailed information about all resolved bugs in Release 5.5(0.2) through the resolved bug search for Release 5.5(0.2). This search uses the following parameters:
Related Documentation
In addition to these release notes, you can find documentation for Cisco UCS Director in the following locations on Cisco.com:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation.
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What's New in Cisco Product Documentation RSS feed. RSS feeds are a free service.
Copyright © 2016-2017, Cisco Systems, Inc. All rights reserved.
Feedback