Cisco Blog » The Platform

2016年6月1日星期三

Cisco Notification Alert -Cisco UCS Director - For Large Scale DC-01-Jun-2016 16:44 GMT

 

 

 

 

 

 

 


Known Bugs - UCS Director

Alert Type:
New
Bug Id:
CSCuz52386
Title:
Evaluation of cloupia-cuic for OpenSSL May 2016
Status:
Fixed
Severity:
2 Severe
Description:


Symptom:
This product includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs:

CVE-2016-2108 CVE-2016-2107 CVE-2016-2105 CVE-2016-2106 CVE-2016-2109 CVE-2016-2176

And disclosed in https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160504-openssl

This bug has been opened to address the potential impact on this product.

Cisco has analyzed the vulnerabilities and concluded that this product may be affected by the following vulnerabilities:


EVP_EncryptUpdate overflow CVE-2016-2106
ASN.1 BIO excessive memory allocation CVE-2016-2109


This product is not affected by the following vulnerability:
EBCDIC overread CVE-2016-2176
Memory corruption in the ASN.1 encoder CVE-2016-2108
Padding oracle in AES-NI CBC MAC check CVE-2016-2107
EVP_EncodeUpdate overflow CVE-2016-2105

Conditions:
Exposure is not configuration dependent.

Workaround:
None

Further Problem Description:
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base CVSS score as of the time of evaluation is: 5.1

https://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:H/Au:N/C:P/I:P/A:P/E:ND/RL:ND/RC:ND

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.
The score reflects the maximum score for all the vulnerabilities mentioned in this bug information

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/web/about/security/psirt/security_vulnerability_policy.html

Last Modified:
11-MAY-2016
Known Affected Releases:
5.4(0.3)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuy54478
Title:
Evaluation of cloupia-cuic for OpenSSL March 2016
Status:
Fixed
Severity:
2 Severe
Description: *

Symptom:
Cisco Cloupia Unified Infrastructure Controller includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs:

CVE-2016-0800 CVE-2016-0705 CVE-2016-0798 CVE-2016-0797 CVE-2016-0799 CVE-2016-0702 CVE-2016-0703 CVE-2016-0704

And disclosed in https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160302-openssl

This bug has been opened to address the potential impact on this product.

Conditions:
Exposure is not configuration dependent.

Cisco has reviewed and concluded that this product is affected by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2016-0797 - BN_hex2bn/BN_dec2bn NULL pointer deref/heap corruption
CVE-2016-0799 - Fix memory issues in BIO_*printf functions
CVE-2016-0702 - Side channel attack on modular exponentiation

This product is not affected by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2016-0800 - Cross-protocol attack on TLS using SSLv2 (DROWN)
CVE-2016-0703 - Divide-and-conquer session key recovery in SSLv2
CVE-2016-0704 - Bleichenbacher oracle in SSLv2
CVE-2016-0705 - Double-free in DSA code
CVE-2016-0798 - Memory leak in SRP database lookups

Workaround:
Not available.

Further Problem Description:
Additional details about those vulnerabilities can be found at http://cve.mitre.org/cve/cve.html

PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base CVSS score as of the time of evaluation is: 4.3

https://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:M/Au:N/C:P/I:N/A:N/E:ND/RL:ND/RC:ND

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/web/about/security/psirt/security_vulnerability_policy.html

Last Modified:
19-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuy07267
Title:
Evaluation of cloupia-cuic for OpenSSL January 2016
Status:
Fixed
Severity:
2 Severe
Description: *

Symptom:
Cisco Cloupia Unified Infrastructure Controller includes a version of OpenSSL that is affected by the vulnerability identified by one or more of the following Common Vulnerability and Exposures (CVE) IDs:

CVE-2016-0701 CVE-2015-3197

And disclosed in http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160129-openssl

This bug has been opened to address the potential impact on this product.

Conditions:
Exposure is not configuration dependent.

Cisco has reviewed and concluded that this product is affected by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2016-0701

This product is not affected by the following Common Vulnerability and Exposures (CVE) IDs:
CVE-2015-3197

Workaround:
Not available.

Further Problem Description:
Additional details about those vulnerabilities can be found at http://cve.mitre.org/cve/cve.html

PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are: 5.8/4.5

http://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AAV:N/AC:M/Au:N/C:P/I:P/A:N/E:POC/RL:OF/RC:C

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/web/about/security/psirt/security_vulnerability_policy.html

Last Modified:
27-MAY-2016
Known Affected Releases:
7.3(0)ZN(0.99)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuy09881
Title:
Deletion of group having 2K+ users & not associated with VM/VDC timesout
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
Deletion of a large group shows a blank pop UI that eventually times out.

Conditions:
Group being deleted has 2K+ users and not associated with any VM or VDC. This is applicable for both local and LDAP groups.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2), 5.5(0.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy44636
Title:
IP Subnet Pool Policy does not re-use subnet after roll back
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
When executing "Get IP Subnet Pool From IP Subnet Pool Policy", an IP Subnet is generated from the IP Subnet Pool Policy. After roll back, it's returned to the pool. However, it cannot be used again, and eventually, the pool runs dry and fail to provision another IP Subnet even if there are available IP Subnet in the pool.

Conditions:
The subnet must have been provisioned once, and rolled back. It then will be unavailable for provisioning even though it's marked as available.

Workaround:
None.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux55427
Title:
LUN sized incorrectly when using TB configuration on 7 mode filer
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
UCSD incorrectly applied the LUN size. During resizing LUN size from 1TB to 2TB, UCSD converted the LUN to 2GB.

Conditions:
Resizing a LUN from GB to TB

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux33567
Title:
IBM Storwize datastore task should support for all product type
Status:
Fixed
Severity:
2 Severe
Description: *

This issue is fixed after UCSD 5.4 release and available in latest 5.5 code base .

Symptom:
IBM Storwize Create Datastore Task is not mounting LUN volume into the remote host . Its logging the error message like ,"Waiting for LUN Path..." and finally the task is failed .

Conditions:
This is only for some Hardware /machine type . This task is working fine for IBM Storwize V7000 with machine type 2076-124 (product_mtm 2076-124) but not working for customer's machine types .

Workaround:
No workaround

Further Problem Description:
For the machine type product_mtm 2076-124 , the WWNN format should be 50:05:07:68:02:0x:xx:xx . Based on this format , WWPN is converted into WWNN for mounting storage volume into host over FC adapter . But the customer machine WWNN format is 50:05:07:68:0b:00:xx:xx , so issue occurred while converting WWPN into WWNN.

Customer's machine WWPN is 50:05:07:68:0b:23:41:1e and if we convert this WWPN into WWNN with our exiting logic based on the format 50:05:07:68:02:0x:xx:xx , then result of the WWNN will be 50:05:07:68:0b:03:41:1e . This is not correct as per the machine type . It should be 50:05:07:68:0b:00:41:1e .


while mounting the datatore into host , Vmware will check WWNN mappings of target and host , if WWNN is mapped in the Zone , then datastore will be mounted on that selected host node , otherwise it will check for suitable WWNN mappings in the target . During this search time , system will print message like , "Waiting for LUN path" , if not finding any suitable WWNN in target then task will fail . In this case , WWNN will never match due to the WWNN conversion logic .

The conversion logic should be supported for all machine type or Task should collect the WWNN from the IBM device directly . This issue is fixed by collecting the WWNN from IBM device directly using generic inventory collections , hence there is no need of WWNN conversion logic and now Task will support for any type of IBM machine , since WWNN will be directly collected form the selected IBM device .

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux99901
Title:
UCSD default Zoneset Activate Rollback causes Outage
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
While making any changes to zoning, the ZoneSet for that VSAN needs to be activated for changes to take into effect. However if user decides to undo the modification it calls rollback feature of the workflow.
The issue with the rollback is it will not only removed the modification but also deactivates the entire ZoneSet for the VSAN causing SAN outage

Conditions:
Zoneset exists and is activated

Workaround:
Both steps are mandatory

Dont rollback Zoneset Activate task.
Reactivate the Zoneset either from fabric or from UCSD

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
7.3(0)ZN(0.99)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux22982
Title:
Dashboard disable not applied, subsequent login portlets replicated
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
- When disabling use dashboard, on next login dashboard is back enabled
- If you try to disable it again, on next login portlets doubles
- If you try to remove unnecessary portlets, on next login there are even more

Conditions:
Dashboard is enabled, populated with portlets and then disabled

Workaround:
none

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy39538
Title:
VM resize option for vDC should derive values from the compute policy
Status:
Fixed
Severity:
2 Severe
Description:

Symptom:
During VM resize for container VM's, values are not derived from computing policy.

Conditions:
During VM Resize on container VM's

Workaround:
User has to provide proper values manually.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.3), 5.4STV3.0, 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw98892
Title:
After modifying task input into user input, can't change policy type
Status:
Fixed
Severity:
3 Moderate
Description: *

Symptom:
Not able to edit the policy type in the configure rack server task while changing the input type from task input into user input.

Conditions:
1. Add the configure rack server task with profile name as task input.
2. Chosen profile has only one policy which was chosen as policy type.
3. Edit the task.
4. Change the policy type into user input and go to next page and change the policy type.

It is not moving to next page when the already saved profile does not have newly selected policy type.

Workaround:
Delete the task and Add the task again with profile name as user input.

Above is the straight forward option.
Here another option is before making the changes to user input type, UnSelect the Rack-Server profile then click back button and select the user input type.

It is the correct way of editing the task from manual input type to User Input type.

Further Problem Description:

Last Modified:
02-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuz44142
Title:
Evaluation of cloupia-cuic for NTP_April_2016
Status:
Open
Severity: *
3 Moderate
Description:

Symptom:

Cisco UCS Director includes a version of ntpd that is affected by the vulnerabilities identified by the Common Vulnerability and Exposures (CVE) IDs:

CVE-2016-1551, CVE-2016-2516, CVE-2016-2517, CVE-2016-2518, CVE-2016-2519, CVE-2015-8138, CVE-2016-1550, CVE-2015-7704, CVE-2016-1547, CVE-2016-1548, CVE-2016-1549

And disclosed in http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20160428-ntpd

This product is affected by one or more of the listed CVE ids.


Conditions:

Device configured with NTP.

Cisco has reviewed and concluded that this product is affected by the following Common Vulnerability and Exposures (CVE) IDs:

* CVE-2016-2518 - Network Time Protocol Crafted addpeer With hmode > 7 Causes Array Wraparound With MATCH_ASSOC
* CVE-2015-8138 - Network Time Protocol Zero Origin Timestamp Bypass
* CVE-2016-1550 - Network Time Protocol Improve NTP Security Against Buffer Comparison Timing Attacks
* CVE-2015-7704 - Network Time Protocol Original Fix For NTP Bug 2901 Broke Peer Associations
* CVE-2016-1548 - Network Time Protocol Interleave-pivot Denial Of Service Vulnerability
* CVE-2016-1549 - Network Time Protocol Sybil Vulnerability: Ephemeral Association Attack
* CVE-2016-1551: Network Time Protocol Refclock Impersonation Vulnerability
* CVE-2016-2516: Network Time Protocol Duplicate IPs On Unconfig Directives Will Cause An Assertion Botch In ntpd
* CVE-2016-2519 - Network Time Protocol Remote ctl_getitem() Return Value Not Always Checked
* CVE-2016-2517: Network Time Protocol Remote Configuration Trustedkey/Requestkey/Controlkey Values Are Not Properly Validated

This product is not affected by the following Common Vulnerability and Exposures (CVE) IDs:

* CVE-2016-1547 - Network Time Protocol CRYPTO-NAK Denial Of Service Vulnerability


Workaround:




Not available.

Further Problem Description:



Additional details about those vulnerabilities can be found at http://cve.mitre.org/cve/cve.html

PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are: 6.4/5.3

http://tools.cisco.com/security/center/cvssCalculator.x?version=2&vector=AV:N/AC:L/Au:N/C:N/I:P/A:P/E:F/RL:OF/RC:C/CDP:N/TD:N/CR:L/IR:L/AR:

The Cisco PSIRT has assigned this score based on information obtained from multiple sources. This includes the CVSS score assigned by the third-party vendor when available. The CVSS score assigned may not reflect the actual impact on the Cisco Product.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/web/about/security/psirt/security_vulnerability_policy.html

Last Modified:
12-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuw73244
Title:
AfterUpgrade UserApproval WorkFlow EmailTemplate need to "Reset to default" in GUI
Status:
Terminated
Severity:
3 Moderate
Description:

Symptom:
On Upgrade and Migrated appliance:
While executing user Approval and Multi User Approval tasks, exception is throwing in the log and Email is not received to the user approval configured users .In the OVF Appliance it is working fine.

Conditions:
On Upgrade and Migrated appliance:
1. Create a User and give the correct email address under Administration - Users and Groups - Users tab.
2. Navigate to Policies - Orchestration
3. Create a Work flow for User Approval or Multi user approval - Execute the work flow.
4. Email is not received and Exception is throwing in the log.

Workaround:
Select the Reset to default Subject and Reset to default body check boxes for the User Approval workflow email template:
1. Navigate to Administration - System - Email Templates - User Approval Work flow email template - Edit .
2. Select the Reset to default Subject and Reset to default body check boxes. and submit it
3. Repeat the above for Multi user approval task as well.
4. After reset, task will be executed successfully and Email will be received to the specified email address.

Further Problem Description:

Last Modified:
20-MAY-2016
Known Affected Releases: *
5.4(0.0), 5.5(0.0)
Known Fixed Releases:
Alert Type:
New
Bug Id:
CSCuz10884
Title:
Tenant Rollback is not unmounting the datastores properly.
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
When a tenant is rolled back, during deleting storage phase it does not properly unmount and delete datastore from vCenter. However the storage is pulled from vCenter directly as it is deleted on Array level.

vCenter shows alarms that the datastore are not unmounted properly

Conditions:
When both tenant & container SR rolls back at the same time, datastore which are used by container do not get removed & in vCenter

Workaround:
None

Further Problem Description:

Last Modified:
27-MAY-2016
Known Affected Releases:
5.3(2.1)
Known Fixed Releases:
Alert Type:
New
Bug Id:
CSCus11614
Title:
EMC Recovery Point Parsing issue
Status:
Fixed
Severity:
3 Moderate
Description:

This issue is found if RP environment is other than IP. With IP it is working fine

Symptom:
Not able to perform RP cluster Inventory

Conditions:
if RP uses other than IP, we face this in inventory collection.

Workaround:
No Workaround available.

Further Problem Description:
Issue is resolved in ZC. need to wait for the reply from field after ZC upgrade

Last Modified:
27-MAY-2016
Known Affected Releases:
5.1(0.0)
Known Fixed Releases:
Alert Type:
New
Bug Id:
CSCuz86766
Title:
Cancelled SR's not Re-submitting properly as expected
Status:
Open
Severity:
3 Moderate
Description:

Symptom:
Cancelled SR's(WF with Nested Compound Tasks) not Re-submitting properly as expected

Conditions:
Cancelled SR's are not Resubmitting properly if we resubmit the WF in middle of nested compound tasks after cancel the WF

Workaround:
Design WF with only one compound tasks- Resubmit will properly works for cancelled WF's

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCux61497
Title:
Add PNIC to DVSwitch task random failures
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Add PNIC to DVSwitch task fail randomly.

Conditions:
Last host node of VMware account is passed as an user input to "Host Node" task input.

Workaround:
None.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux50100
Title:
New minor version of cloudera cluster creation failing
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Cloudera 5.4.8 cluster creation fails

Conditions:
Newer minor version of already supported cloudera 5.4.x cluster fail . This version is something thats not validated officially within already released UCSD 5.4

Workaround:
All file entries need to be made for new 5.4.8 version in the file : /opt/cnsaroot/bigdata_templates/common_templates/HadoopDistributionRPM.txt of BMA .

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz23899
Title:
Task ID off by one in SR logs and Inframgr logs
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
In SR logs, the "Executing workflow item number " at the start of a task shows the correct item number but the "Completed workflow item number , with status " log message when the task ends, shows a wrong item number, one less than the actual number.

e.g.
Feb 11, 2016 04:37:37 EST Executing workflow item number 5
Feb 11, 2016 04:37:38 EST Completed workflow item number 4, with status Completed


Also, in the inframgr logfile, the item numbers are off by one in the following log messages:
016-02-11 04:19:42,974 [WFExec-473-0] INFO run(WorkFlowExecutor.java:78) - Executing Step 0 of 5 for SR 473
2016-02-11 04:19:43,003 [WFExec-473-0] INFO run(WorkFlowExecutor.java:120) - Completed workflow Step 0 of 5 for SR 473
...
2016-02-11 04:37:37,652 [WFExec-473-4] INFO run(WorkFlowExecutor.java:78) - Executing Step 4 of 5 for SR 473
2016-02-11 04:37:38,776 [WFExec-473-4] INFO run(WorkFlowExecutor.java:120) - Completed workflow Step 4 of 5 for SR 473

Note that therefor, in the above example, "Completed workflow Step 4 of 5" indicates that the 5th and last step has completed.

Conditions:
n/a

Workaround:
None. This is a cosmetic issue only.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux33640
Title:
SAN Zone Task inventory collection synchronization
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
SAN Zone tasks in a provisioning workflow fail at random times.

Conditions:
SAN Zone task spawned inventory collection thread doesn't get a SSH session with MDS device as there is no free SSH session available in the device.

Workaround:
Add a "Wait for Specified Duration" task with 2/3 minutes delay after each of the following tasks.
- Create SAN Zone
- Add Member to SAN Zone
- Create Zone Set (Customer do not have this task in the WF, using an existing zone set)
- Add SAN Zone to Zone set
- Activate Zone Set

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy22773
Title:
Addng a new condtion to Conditional Task do not save existing conditions
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Addng a new condtion to Conditional Task do not save existing conditions

Conditions:
Adding new condition to the task

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw76487
Title:
HyperV Networking Policy Status changes to Error after 5.3 upgrade
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VM Provisioning will fail due to missing VM network in the network policy. This is due to existing HyperV Network Policies lose VM Network association after upgrade.

Conditions:
UCSD upgrade from 5.1 to 5.3.

Workaround:
Reattach VMNetworks by editing the HyperV network policy and creating a VM NIC.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(0.0)
Known Fixed Releases: *
5.3(2.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz45709
Title:
VMAX Storage Devices report API is not working
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VMAX Storage Devices report API throws error

Conditions:
Use VMAX Storage Device API used from Metadata of UCSD.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz13456
Title:
Resource Allocation fails - vCenter 6.0 with ESXi type and version 6.0
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Resource allocation fails on vCenter 6.0 while provisioning VM.

Conditions:
If computing policy has below conditions

"ESX Type" = "ESXi Only"
"ESX Version" = "4.0 and Above"

Workaround:
Remove the conditions

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz12422
Title:
Illegal character in workflow name causes workflow screen to be empty
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
In the UCS Director GUI, under Policies -> Orchestration -> Workflows, no workflows are shown.

Conditions:
This can occur if the workflow database contains a workflow with an illegal name, i.e. a name with one or more non-alfanumeric characters.
At the time of this writing it is not clear how exactly this condition can occur since an error check is in place when creating or cloning a workflow which should prevent an illegal name to be used.

Workaround:
Restore the DB from a backup, or contact Cisco TAC to have the workflow deleted from the database.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux79489
Title:
Vm Resource allocation selecting the wrong datastore
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Wrong datastore selection though conditions are specified in storage policy.

Conditions:
Multi VM provisioning, the issue happens at random.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy08435
Title:
Workflows fail validation if changes ever made to Powershell Agent
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
If a change is made to the Powershell Agent in a UCS Director 5.3.2.0 environment, any workflow that uses that PS agent subsequently fails validation after clicking the "Validate Workflow" button in "Workflow Designer", with a "Missing mandatory entry for: PowerShell Agent" red error message referring to an issue with the PS Agent for each task using it.

Conditions:
I reproduced the issue in my own UCS Director 5.3.2.0 environment by following all of the same steps as the customer with the same result.

Workaround:
Each workflow then has to be opened up followed by opening up the tasks and then clicking next through the task and submit for everything to work appropriately. Note: its not as if the PS Agent in the task needs to be reset as that had been tried with no different result.

Further Problem Description:
The customer views the issue as an annoyance that slows down work productivity.

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy09378
Title:
New-sclogicalnetowrk&new-sclogicalnetworkdefinition cmdlets are failing
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
New-sclogicalnetowrk & new-sclogicalnetworkdefinition cmdlets are failing due to lack of ?VMMserver option in syntax even they it is not require for actual execution

Conditions:

Workaround:
have the following line description of the task will help... dummy desc" -VMMServer "localhost

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.1), 5.4(0.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy08379
Title:
UCS Service Profile Rollback does not delete renamed profile
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
UCS Director targets the original name of a UCS Service Profile that has been created via workflow when attempting to utilize the "Rollback Request" feature and, therefore, will not delete a Service Profile that has been created and subsequently renamed.

Conditions:
(1) Using the "Rollback Request" function on an SR with (2) a UCS Profile that has been renamed

Workaround:
To achieve desired result (deleting Service Profile):
-Go into UCS Manager and manually delete the created service profile.
-Create a workflow that will delete service profiles based on user input.

To utilize "Rollback Request" functionally
-No known

Further Problem Description:
This is a concern because it could theoretically delete the WRONG service profile in the following situation:
SR 1 creates Service Profile "A"
SR 2 creates Service Profile "B"
User or Workflow renames SP "A" to SP "B" and SP "B" to SP "C"
User runs "Rollback Request" on SR 2 in attempt to delete what was originally SP "B" but is not SP "C"
Because of bug, what was originally SP "A" and became SP "B" is deleted.

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(1.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux16602
Title:
Configuring the FI in stand alone option
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
While Configuring the FI in stand alone option network policy page is not opening.

Conditions:
None

Workaround:
None

Further Problem Description:
None

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy85068
Title:
Unable to Create Fabric Network, in log shows NPE
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
UCSD connection with DCNM fails when 'Create Fabric Network' action is executed in UCSD.

Conditions:
Create Fabric Network action in UCSD 5.4.0.2

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz33975
Title:
RescanRecoverStorageVolumes task is failing in DR Tenant Onboarding WF
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Rescan RecoveryPoint Storage task fails with below error:
UTC Task: EMC-RP-Journal (Rescan RecoverPoint Storage Volumes) failed with error - One or more instances could not be made persistent, selectedContext=

Conditions:
IF storage group names(list of comma separated storage group this lun is associated to) is bigger than 256 string length

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.1), 5.4(0.0), 5.5(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw78757
Title:
Clone Modify VM n/w task does not have same functionality as the orginal
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Clone Modify VM n/w task does not have same functionality as the orginal

Conditions:
Issue noticed on customer setup and the same can be easily replicated in our local environment.
Modify VM network (In-built task)
'Select Network Adapter' and 'Portgoup Name' are dynamically populated when a VM is selected.
But when we clone the task - In Cloned task "Select Network Adapter' and 'Portgoup Name' are not dynamically populated"

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.1(0.1), 5.3(1.2), 5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy57681
Title:
Cloudsense Algorithm is not getting updated from vDC- Manage Categories
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Changes made to Manage Categories for smart algorithm is not picked up during VM provisioning

Conditions:
Change the Smart Allocation Policy from vDC through Manage Categories

Workaround:
Change smart algorithm only works when done through Application Categories.
Administration -> System -> Application Categories

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2), 5.4(0.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz00587
Title:
Manage Categories is not working as expected for Cost Model
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
New Cost model selected in Manage Category option in vDC is not getting reflected in chargeback when a VM is provisioned using a Category to which the new Cost model is assigned.

Conditions:
Using Manage Categories option for changing policies.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2), 5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux51604
Title:
Same Static IP Pool is assigned for SRs executed in parallel
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Parallel Get IP Subnet from IP Subnet Pool tasks return same IP subnet

Conditions:
If two SR are triggered at the same time.

Workaround:
Introduce wait for specific duration in one of the SRs

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy01018
Title:
Config Rack Server task "OUTPUT_CIMC_SERVER_SLOT_1_MAC_ADDRESS" issue
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Configure Rack Server task "OUTPUT_CIMC_SERVER_SLOT_1_MAC_ADDRESS" output is empty when VIC cards are used.

Conditions:
None

Workaround:
Provide the output manually in the next task

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0), 5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz32501
Title:
Cloudsense report is taking more time to generate
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Cloudsense report is taking more time to generate and gets stuck in progress

Conditions:
Generating Cloudsense report and if the report has large data.

Workaround:
If the report generation is taking longer time, then close the in-progress pop-up and refresh the table after sometime.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.1), 5.4(0.3)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux21863
Title:
VMware inventory collection performance improvements during WF execution
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Workflow containing VMware tasks which collect inventory data from given VMware account take long time depending upon the number of vmware tasks and time taken by other tasks in the workflow.

Conditions:
VMware account inventory data is large comprised of hosts, switches, port groups, etc.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux09067
Title:
Cloned GroupAdmin user can see VMs of other tenants
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
When selecting a catalog item that requires selection of a VM, the user sees the list of all VM's known by UCS Director, instead of just seeing the list of VM's in the user's group.

Conditions:
This only occurs if the user has a user role that is a (customized) clone of the regular GroupAdmin role.

Workaround:
Clone the GroupAdmin role again but keep the string "GroupAdmin" in the new name, e.g. "GroupAdmin1".

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(0.1)
Known Fixed Releases: *
5.3(2.1), 5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy13360
Title:
Custom VIX task is not working after upgrade
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Custom VIX task not working after upgrade to 5.3.2.2 beta fails with below error:
(custom_ExecuteVIXScriptCustom) failed with error - java.lang.Exception: [VIXActionHandler] - Invalid parameter, selectedContext=

Conditions:
Custom VIX script

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2)
Known Fixed Releases: *
5.3(2.2), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz42499
Title:
UCSD does not support current Instance Types on AWS, cannot deploy VMs
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
If you try to deploy a Linux VM to AWS, using UCSD's Amazon Deployment Policy, you will receive this error in the SR log:

"VM provisioning failed with error Non-Windows instances with a virtualization type of hvm are currently not supported for this instance type."

Conditions:
Try to deploy a Linux VM to AWS using UCSD's Amazon Deployment Policy.

Workaround:
None

Further Problem Description:
It turns out that this error is being generated by AWS. If you look in UCSD's Amazon Deployment Policy, you will see that only available Instance Types are M1, C1 and M2. However, on Amazon's "Instance Type Matrix" ( http://aws.amazon.com/amazon-linux-ami/instance-type-matrix/), it does not list any of those three Instance Types. It has types like M3, M4, C3 and C4, among others.

In other words: UCSD's Amazon Deployment Policy has not been updated to support the current Instance Types that are available on AWS. As a result the AWS feature of UCSD is not functional, at least for deployment of Linux VMs.

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2), 5.4(0.3)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux82231
Title:
Admin input gets changed when running workflow as compound task
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The issue is with the compound tasks having same user input name but different Admin input values(in the attached scenario, 1 and 2).
After condition, the value is not over writing with the latest one.

Conditions:
Custom task is clone of another

Workaround:
NA

Further Problem Description:
NA

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux26574
Title:
VMAX: Binding issue in add device to SG for 5.3.2.0 with admin input
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Null Pointer Exception in infra logs, while validating the Add thin device to SG task with admin inputs, when the VMAX account is not available.

Conditions:
while validating the Add thin device to SG task with admin inputs, when the VMAX account is not available.

Workaround:
adding VMAX account to ucsd will solve it

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.1)
Known Fixed Releases: *
5.3(2.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz21923
Title:
Scheduled Jobs Did Not Update for DST
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The NTP client automatically synchronizes the appliance OS/system time with the configured NTP server. However, the infra services time doesn't synchronize with the system time automatically.

Conditions:
DST changes

Workaround:
Restart UCSD infra services or appliance

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz10226
Title:
UCS SAN/LAN conectvity policy return err whn Placement Policy is selcted
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Add a placement policy ,if it choose "let system perform placement",return the err no vhba found,no vnic found

Conditions:
Selecting 'Let System Perform Placement'

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz02031
Title:
Acquiring double resources for DR tenant
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
If a VDC with 32 GB ram would require 80 GB ram to be available. UCSD only reserves 32 GB ram as VDC requires but we need to reserve twice the value at tenant level, which is causing a huge waste of resources.

Conditions:
creating a VDC in DR enabled tenant

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.1)
Known Fixed Releases: *
5.3(2.3), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz35241
Title:
Ability to manage network device config backup
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
UCSD inventory database occupying large disk space.

Conditions:
Any change in the UCSD managed network devices configuration results in UCSD pulling running and startup configuration from the devices and storing the same in the inventory database during network inventory collection. Over time, the inventory database grows huge using up large disk space in the appliance.

Workaround:
Inventory database NET_DEVICE_CONFIG_DATA table can be purged for the given network device ip address and/or timestamp. However, it's recommended to obtain a custom task from BU to purge the table.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy31496
Title:
VIX task fails intermittently with guestOSType as 'null',
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VIX task fails intermittently with guestOSType as 'null',

Conditions:
None

Workaround:
Use cloupia script task to get the OS information.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2)
Known Fixed Releases: *
5.3(2.2), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz55781
Title:
Static IP Pool Usage Policy is not detecting used VM Kernel IP
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VM Kernal IP address shows up in 'Global IP Pool Usage' report as 'Used' but it is not detected the same in Static IP Pool Usage report

Conditions:
Using Static IP Pool Policy for assigning IP address to vMotion Interfaces that are not routable from UCSD.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy05475
Title:
VM provisioned on first resource pool under a cluster when none selected
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VM provisioned on first resource pool under a cluster when none selected

Conditions:
If provisioned cluster has a vApp or Resource pool.
Symptoms:
The VM is provisioned on the first available vApp or Resource Pool though none is selected in the computing policy.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz16375
Title:
HyperV Network Policy report is not displaying data
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
HyperV Network Policy report is blank not displaying data

Conditions:
None

Workaround:
Identified the defective record and removed the entries from DB.
delete from db_private_admin.HYPERV_CLOUD_NETWORKING_POLICY where POLICYID=34;
delete from db_private_admin.HYPERV_CLOUD_NETWORKING_POLICY where POLICYID=36;

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy49364
Title:
Add VM vNICs - does not add IP address
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
SR 680238810 for this. My colleague who worked on this before me had two additional cases open for this - SR 636744381 and SR 636779173, but he wasn't able to confirm if a bug was ever opened for it.

So question, when you think a patch would be available for this, should I just plan on cobbling together some workaround in the mean time?

Also, the configuring of the vNIC is only part of the problem. As I mentioned, it appears there are 3 issues with this task:-
Providing a single IP from a static IP pool as the "IP Pool" input (which is a valid input) fails the task with the error message "Cannot reserve static IP Address. Pool exhausted".
The task reboots the VM as part of the last which I believe is unnecessary and obviously disruptive. Perhaps there is a reason for it I am unaware of, but this is not necessary is manually adding the vNIC in vCenter
vNIC(s) not configured after adding

Conditions:
SR 680238810 for this. My colleague who worked on this before me had two additional cases open for this - SR 636744381 and SR 636779173, but he wasn't able to confirm if a bug was ever opened for it.

So question, when you think a patch would be available for this, should I just plan on cobbling together some workaround in the mean time?

Also, the configuring of the vNIC is only part of the problem. As I mentioned, it appears there are 3 issues with this task:-
Providing a single IP from a static IP pool as the "IP Pool" input (which is a valid input) fails the task with the error message "Cannot reserve static IP Address. Pool exhausted".
The task reboots the VM as part of the last which I believe is unnecessary and obviously disruptive. Perhaps there is a reason for it I am unaware of, but this is not necessary is manually adding the vNIC in vCenter
vNIC(s) not configured after adding

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(0.1), 5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz35512
Title:
UCSD Loop task pickup wrong service profile
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Workflow user Input to select a iterated value with a loop task then values from the previous Workflow execution are reflected in the task output.

Conditions:
Loop task in orchestration workflow to select the service profile as user input for iteration

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw67855
Title:
Each UCSC Test Connection action creates a new web session in the UCSC
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Unable to login to UCS Central GUI using the same user account associated with UCSD to manage the UCS Central.

Conditions:
User performed many "Test Connectivity" actions on the UCS Central through UCSD GUI.

Workaround:
Avoid running too many successive "Test Connectivity" actions on the UCS Central through UCSD GUI.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(0.0), 5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy02631
Title:
Missing Output variable for task Netapp, NetAppcluster and VM
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The output variable is missing for the netapp tasks, Execute NetApp CLI, Execute NetApp Cluster CLI , Execute VM Command. The desired information needs to be pulled out of the log file and wrap the original function.

Conditions:
All the Net app related tasks , Net App cluster and vm tasks mentioned in the summary when executed, the output of the command gets dumped into a log file irrespective of the situation.

Workaround:
There is no particular workaround to achieve. The tasks need to be modified thereby the output is fetched onto a variable. A bug is filed for this issue and netapp team would be fixing it

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy78955
Title:
UCSD: 'Add VM vNICs' task - get rid of VM reboot after add vNIC?
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The UCS Director built-in task 'Add VM vNICs' as currently designed requires a reboot of the VM after adding a vNIC. This should not be true, given that it is not required when adding a vNIC to a VM in vCenter. Can we get rid of that un-needed reboot?

Conditions:
Use built-in task 'Add VM vNICs'

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(0.1)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw89617
Title:
Hyper V Error : Non HA VM Cannot Use Cluster Disk Resource
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VM provsion on Hyper V fails
The task failed with error : NonHAVMCannotUseClusterDiskResource

Conditions:
Provision a VM on Hyper HA cluster

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.1), 5.4(0.0), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux33139
Title:
Multiple if-else tasks are not manageable in Workflow Designer
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Multiple if-else tasks are not manageable in Workflow Designer since the tasks in the left are not visible.

Conditions:
Creating WF with multiple if else tasks

Workaround:
Only way to access those tasks at Workflow Designer window is to set the screen resolution to a upper one like 2560x1440 as they are hidden under the [Available Tasks] pane.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(0.0), 5.3(2.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux58853
Title:
Parameter is not defined for BOOTPROTO,NETMASK in ifcfg-eth2
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Parameters NETMASK and BOOTPROTO is not defined for ifcfg-eth2 interface and default IPV6 is enabled.

Conditions:

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy78132
Title:
VM Inventory issue for VM provisioned using OVF and assigned to new vDC
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Single VM inventory causes the VM to disappear for VM provsioned through OVF and then assigned to new vDC and delete the old vDC.

Conditions:
Provision VM from OVF and assign to new vDC and delete the old vDC on which VM is first provisioned.

Workaround:
Do not assign the VM to a new vDC after provisioning
Do not delete the vDC on which the VM is provisioned

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.2)
Known Fixed Releases: *
5.3(2.3), 5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz19884
Title:
Assign VM to vDC is not working on Provisioned VMs
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
VM is not assigned to selected vDC when 'Assign VM to vDC' action is triggered.

Conditions:
Using 'Assign VM to vDC' action button

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy16917
Title:
Kohls TAC 637967947 VM Prov. Task pauses for 30 min before template copy
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Kohls TAC ticket 637967947 - VM Provision Task pauses for 30 minutes before template copy

Conditions:
Kohls TAC ticket 637967947 - VM Provision Task pauses for 30 minutes before template copy

Workaround:
na

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux37173
Title:
Cannot add task "Add ACL Policy Rules" to workflow
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Add ACL Policy Rules task cannot be added to a workflow.

Conditions:
Seen on UCSD 5.3.2.0. Have not tried other versions.

Workaround:
In "Task Inputs" screen, set the following:
1) Rule 1:
Name: some name
Protocol/Service: Service
Service Port: change 0 to some dummy port number
2) Rule 2 and Rule 3
Check "Add rule 2" and "Add rule 3" and then setup
dummy rules as done for rule 1.
3) Click on next, at this point screen should have moved
to "User Output Mapping" and "Submit" button should be there.
4) Click on "back"
5) Setup rules as normally done.

Basically, "Service port" needs to be set to some number
other than 0 irrespective of whether it shows up in the UI or not
and irrespective of whether it is used or not.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw95441
Title:
Missing tasks when a vCenter AC is deleted and added with same name
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Missing Performance data collector task in System Tasks

Conditions:
If a vCenter account is deleted from UCSD and Add back with same name. Applicable to both Single node and Multi-node UCSD.

Workaround:
Restart the appliance services

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux57577
Title:
Remove Capacity Reservation error during workflow rollback
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Remove Capacity Reservation error is seen during workflow rollback.

Conditions:
This happens when the reserved ip address is assigned to a VM, VMware Inventory Collector runs at least once, and "IP Pool Policy Usage Report" shows the IP as used with usage reported by "VMware-connector"

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.3(2.2)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy48019
Title:
Disallow scheduling a WF with 'Start Time' in the past
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Past time scheduled workflows are executing at the current time

Conditions:
workflows which are scheduled to execute at the past time are executing at the current time

Workaround:
Disallowing the WF's scheduling with Start Time in the past

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz13861
Title:
UCS Director 5.4 - Brocade SAN Zoning Task fails
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Brocade SAN Zoning task fails when FCAdapter WWPN value is submitted without colons. At Telus UCSD 5.4 discovered VMAX3 and FC storage ports WWPN values are stored without colons resulting in Brocade SAN task failing.

Conditions:
UCSD 5.4, EMC Solutions enabler 8.0 provides WWPN value of VMAX3 FC ports without colon. UCSD does not correct to format and store WWPN as is without adding colons. Bricade SAN zoning task fails as per attached pictures.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux48041
Title:
APIC container password reset is not working as expected
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
APIC container password reset does not work and in some cases the reset password is not shown

Conditions:
Provisioning an APIC container

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy48966
Title:
Resize VM Memory & CPU task throws string:'null', selectedContext=<None>
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
When 'Resize VM Memory and CPU task' is executed on a Powered-off VM (directly through VM console), the task is throwing below error:
Add Additional CPU without Inventory (Resize VMware VM Memory and CPU) failed with error - For input string: 'null', selectedContext=

Conditions:
VM powered off directly from VM console or vCenter and UCSD does not know the VM current status.

Workaround:
To know the current status of the VM, Add VM Resync task before the Resize VM Memory and CPU task in the workflow.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux74690
Title:
Create VM Disk action is populating all datastores not assigned to vDC
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Create VM Disk action is populating all the datastore available in the vCenter.

Conditions:
Create VM Disk action on a VM

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux44855
Title:
Nexus Device: Update Trunk Task overwrites the existing VLAN config
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Observed on a Nexus device in UCS-D 5.3.2.0 release.

Conditions:

Workaround:
use Network Device CLI task

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy44778
Title:
Create UCS Service Profile from Template append 1 to Service Profile
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Appending prefix 1 to the Service Profile name

Conditions:
Using 'Create UCS Service Profile from Template task for creating Service Profile

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.1)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy67392
Title:
Unable to edit a vCenter account which has same name as VMAX account
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Editing a vCenter account with same name as VMAX account, shows VMAX account details

Conditions:
Both vCenter and VMAX account having the same name

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz15933
Title:
Create F5 Load balancer Virtual Server need to make Mask field optional
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Create F5 Load balancer Virtual Server task says that the netmask is the mandatory field

Conditions:
Using Create F5 Load balancer Virtual Server task

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy53857
Title:
API: vNIC Template attribute for ADD/DELETE VLAN not showing in XML
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The API UCS_ADD_VLAN_TO_VNIC_TEMPLATE doesn't render the relevant XML tag for the selected vnic template.

Conditions:
The issue is constant and occurs at all circumstances whenever the API is hit .

Workaround:
There is no workaround. This needs to be fixed and it is fixed as part of 5403 and 5500.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux81732
Title:
Diagnostic Log required Part of DFA Fabric Inventory Collection
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
DCNM Partition and Network information is deleted from UCSD after an Inventory Collection.

Conditions:
None

Workaround:
1.Login into the UCSD.
2.Navigate to Administration -> Physical Accounts -> Multi Domain Manager -> Select the DCNM Account and Delete it.
3.Navigate to Administration ->System -> System Task -> Under Cisco Fabric Tasks -> DCNM Deleted Account Cleanup Task.
Navigate to Physical -> Network -> Multi Domain Manager -> DCNM Accounts -> DCNM Account Created -> Fabric Discovered Organization tab -> Click on Sync DCNM.
Step5 will fetch all the Organizations present with the Orchestration of the current UCSD into the Fabric Discovered Organization.
6.Select the Organization and click on Assign Group will fetch the organization, partitions and networks into the corresponding tabs.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz69428
Title:
Current Online Users is showing users from other MSP groups
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
MSP Admin report for Current Online users report is showing users logged in from other MSP Organizations

Conditions:
Access 'Current Online Users' report as MSP Admin

Workaround:
None.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy65487
Title:
Storage Policy does not do thick provisioning when provisioning a VM
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
In the VMware Storage Policy, leave the Thin Provision checkbox unchecked. The VM gets provisioned and the logs even show Thick provisioning specified however after the VM has been provisioned the type next to the disk shows as Thin provisioned.

Conditions:
Checkbox left unchecked does not seem to turn on thick provisioning

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux57722
Title:
LDAP User Role Filter does not work with "equals" operator
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
When using LDAP User Role Filter, you are expected to enter the "Group Name" or more technically what is called the "sAMAccountName". When you set a LDAP User Role Filter operator to "equals", the filter does not work against the actual "sAMAccountName" (Group Name). If we set the operator to "starts with", the filter does work. Sounds like the LDAP User Role Filter is actually expecting a different (longer) value than the "sAMAccountName", perhaps something like "groupname@domain.com" for example.

Conditions:
When using LDAP User Role Filter, you are expected to enter the "Group Name" or more technically what is called the "sAMAccountName". When you set a LDAP User Role Filter operator to "equals", the filter does not work against the actual "sAMAccountName" (Group Name). If we set the operator to "starts with", the filter does work. Sounds like the LDAP User Role Filter is actually expecting a different (longer) value than the "sAMAccountName", perhaps something like "groupname@domain.com" for example.

Workaround:
Use "starts with" operator instead of "equals" operator in LDAP User Role Filter

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCus49804
Title:
VMAX:: Getting unmarshalling VMaxThinPoolDevice
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Inframgr log file contains NPE (Null pointer Exception) while collecting inventory for EMC VMax thin pool

Conditions:
If a VMAX thin pool is configured with the devices other than thin device and data devices, NPE is thrown

Workaround:
There is no impact with the inventory collection process. Only the unknown devices wont be listed in Thin pool drill down report.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(0.0)
Known Fixed Releases: *
5.2(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy33318
Title:
Existing Workflow inputs ar not working when vDC is selected as an input
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Existing Workflow inputs are not working when vDC is selected as an workflow user input

Conditions:
vDC selector as a workflow user input

Workaround:
Select the vDC to have the other input to be populated.

Further Problem Description:
NOTE: this bug may be a variant on or special case of CSCuy40389

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy33089
Title:
Time lease editable by end user though admin provide input in catalog
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Time lease option during End user service request creation is editable though admin provide input in catalog

Conditions:
Time lease option is already configured in Catalog by Admin user

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux29687
Title:
Post UCSD5.3 upgrade, VM created in SCVMM becomes non-HA
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Post UCSD5.3 upgrade, VM created in SCVMM becomes non-HA

Conditions:
Using HA for VM provisioning

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux76571
Title:
Windows Ovf deployment is not working with vCenter 6.0
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Windows OVF deployment fails with below error
VM Customization failed. Reason: A specified parameter was not correct: spec.identity

Conditions:
Windows OVF deployment on vCenter 6.0

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.3(2.2), 5.4(0.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux12485
Title:
UCSC SPs inventory collection takes ~10 minutes
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
UCS Central is added to UCSD. When the user executes the "Create Global Service Profile from Template" task, it is taking more time to complete the functionality even though the SP creation is completed in the UCS Central immediately. UCS Central Global SP inventory taking more time and it in turn affect the time taken to complete the task.

Conditions:
This time taken will be increase based on the number of global service profiles in the UCS Central account. If we have more number of Global SP in UCS Central and it will take more time to complete the task.

Workaround:
Its a performance issue only. Functionality will work fine. To reduce the time taken by this take, we can remove the unnecessary Global Service Profiles from the UCS Central account. With this we should be able to reduce the time taken to complete the task.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.1), 5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy85073
Title:
Delete DCNM account is not clearing System tasks
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Deleting DCNM account in UCSD is not clearing the system task of the deleted account.

Conditions:
Delete DCNM account

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux29890
Title:
Cloudera Cluster provision fails if host name contains "-"
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Cloudera Cluster provision fails if host name contains "-"

Conditions:
when trying to create KS Indexer HBASE_INDEXER role in Cloudera, it is not accepting if role name contains "-"

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux42752
Title:
UCSC vNICs/MAC address and vHBA values captured are 'derived'
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
A brand new UCS Central 1.3(1b) and Director 5.3.2.0 environment has been setup with two UCS Domains. When I run a workflow (specifically the "Provision Baremetal ESXi" workflow) with a task to 'Create Service Profile from Template', the task completes but the output variables are not all populated/set. Specifically, the MAC and WWPN details are not assigned to the MAC and WWPN variables. They are set as 'derived'. The Service Profile however does have MAC and WWPNs set for the virtual interfaces.

Conditions:
1. No free MAC/WWPN available from the associated pools.
OR
2. SP inventory collection finished too fast and before UCSC 1.3(1b) changes value of MAC/WWPN from 'derived' to actual values.

Workaround:
None.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.2(0.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy20563
Title:
Hadoop provisioning fails with duplicate IP address assignment issue
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Configuring with small subnets like eth0 IP address(172.16.10.2) matched with eth1 IP address(172.16.10.20) of another node resulting in wrong IP address association.

Conditions:
NA

Workaround:
Configure with different network range for all the three vnics like(eth0:10.29.161.60,eth1:192.168.1.2,eth2:192.168.2.2).

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy40433
Title:
Duplicate VM entries found for Discovered VMs
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Duplicate entries of VM that are discovered from vCenter

Conditions:
Discovered VMs in UCSD from the vCenter account.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(1.0)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux20266
Title:
Multi VM provisioning with loop creating VMs with same VM ID
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Multi VM provisioning with loop task creating VMs with same VM ID and subsequent VMs after the first VM are not discovered in UCSD.

Conditions:
VM provisioning using Loop task for multi VM provisioning

Workaround:
Customer created a task custom task as a workaround

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(1.2), 5.3(2.0)
Known Fixed Releases: *
5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux10102
Title:
Form fields are not populating when the WF is executed as Adv Catalog
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
Custom workflow fields are working as expected when executed in Orchestration. But the same workflow when executed as Advance catalogs for both admin or end user is not working as expected.

Conditions:
Custom workflow executed as Advance Catalog

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.1), 5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy29776
Title:
API: Fetching cloned fenced container data using API throws exception
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
The API userAPIgetServiceContainerData ( Application container) on execution throws Remote service exception on passing an application container id that is cloned from another application container.

Conditions:
The issue occurs in all circumstances. The cloned container id when passed as input to the API userAPIgetServiceContainerData throws RSE in response.

Workaround:
No possible workaround for the issue. The issue was reported as part of 5402. A bug was filed and the dev team have fixed the issue.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux90796
Title:
NetApp Inventory task is missing when Collect Inventory task is executed
Status:
Fixed
Severity:
3 Moderate
Description:

Symptom:
- Collect Inventory task is not triggering inventory on NetApp account
- NetApp Inventory task is missing when Collect Inventory task is executed

Conditions:
Using 'Collect Inventory' task for triggering NetApp Inventory

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0), 5.4(0.2), 5.5(0.0)
Known Fixed Releases: *
5.3(2.2), 5.4(0.2), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuw99305
Title:
Host install inprogress after Add livenode action in cloudera distribtn
Status:
Fixed
Severity:
4 Minor
Description: *

Symptom:
Host Install is still running in Recent Commands of Cloudera Manager UI

Conditions:
Perform Add Live Node action from UCS Director

Workaround:
Remove scm*.lock file under /tmp directory of the new node if any

Further Problem Description:

Last Modified:
20-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuw46623
Title:
Rollback the 'Activate San Zone Set' explanation in the guide
Status:
Fixed
Severity:
4 Minor
Description:

Symptom:
This bug is for users who requested updating the documentation to explain the application behavior of Activate San Zoneset button

Conditions:

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
7.3(0)ZN(0.66)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuq64621
Title:
Incorrect window/button labels on VDC manage categories
Status:
Fixed
Severity:
4 Minor
Description:

Symptom:
When you go to Policies > VDC's and click "manage categories" you come to a new screen for that VDC.
Opening any of those, you will see a screen with an incorrect label on the window and on the buttons.

Title: CatalogFeature.form.vdcAppCtgry.label.FORM_LABEL_EDIT_CATEGORY

Button: CatalogFeature.catalog.COMMON_BUTTON_LABEL_SAVE

Conditions:
Seen in 4.x and 5.0

Workaround:
No workaround - cosmetic

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
4.1(0.3)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz79472
Title:
NullPointerExceptionin log if Policy in storage tier is missing/modified
Status:
Fixed
Severity:
4 Minor
Description:

Symptom:
NullPointer Exception in logs during Resource Allocation step.

Conditions:
If the storage policy used for VM provisioning is deleted/name modified in the storage tier selected during provisioning.

Workaround:
None

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy04550
Title:
RHEL kick-start is failing when the user used "#" in the SSH password
Status:
Fixed
Severity:
4 Minor
Description:

Symptom:
RHEL kick-start is failing when the user used ?#? in the SSH password

Conditions:
RHEL kick-start is failing when the user used ?#? in the SSH password

Workaround:
Enter Alpha numeric password

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCup96957
Title:
Interface coloured icons not showing when connection status shown
Status:
Fixed
Severity:
5 Cosmetic
Description:

Symptom:
Physical > Network > Switch > Interfaces shows for interfaces that are "up" a green icon and for interfaces that are down, a "red" icon.

If the interface connection status is there too, there's no icon shown. For example "up (connected" or "down (disconnected)".

Conditions:
N/A

Workaround:
N/A

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
4.1(0.4)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCut48355
Title:
Guided Setup reappears with login name with different capitalization
Status:
Fixed
Severity:
5 Cosmetic
Description:

Symptom:
The "Guided Setup" window will reappear even after checking the "Do not show this page again" when logging in using a different capitalization for the login name.

Conditions:
To Recreate:
Create new login user with System Admin Access Level (for example, Login Name="test_admin")
Login as the new user using the login name in all lowercase (ex: "test_admin")
At the Guided Setup screen, check the "Do not show this page again" checkbox and click Submit.
Log out.
Login as the user using all caps for the login name, or any different capitalization than all lowercase (ex: "Test_Admin")
The Guided Setup screen will reappear.

Workaround:

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.2(0.1)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuy58749
Title:
userAPIGetWorkflowInputs - add option to fetch inputs 5.3-style
Status:
Fixed
Severity:
6 Enhancement
Description:

Symptom:
As of 5.4, userAPIGetWorkflowInputs call returns *all* inputs (no matter whether they are defined as Admin Inputs in the workflow or not). However, the customer uses scripts to launch workflows via REST API calls. Those scripts depend on the old behavior of this API call: i.e., their script first calls userAPIGetWorkflowInputs to decide which inputs need to be parameterized when they call the actual workflow from REST API.

Conditions:
Call the "userAPIGetWorkflowInputs" API call against a UCSD 5.4 appliance.

Workaround:
None

Further Problem Description:
? The customer uses scripts to launch workflows via REST API calls. Those scripts depend on the old behavior of this API call: i.e., their script first calls userAPIGetWorkflowInputs to decide which inputs need to be parameterized when they call the actual workflow from REST API.

? Customer would like to put in a bug to request that another API call can be created, or an option added to userAPIGetWorkflowInputs API call, such that you are able to request a list of only the *required* input parameters of a workflow (i.e., those inputs that do not already have a value set by admin inputs)?

? In other words: we would like a way to choose between the old and new behaviors of userAPIGetWorkflowInputs

? This issue is not simply academic: if you call a workflow via REST API, and you send values for parameters that already have Admin Input values, it causes unpredictable behavior, which tends to cause the workflow to fail. E.g., it may cause neither value to be passed to the workflow.

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.0), 5.4(0.3)
Known Fixed Releases: *
5.4(0.3), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCux06605
Title:
UCSD 5.3.2.0 / Bind Thin Device to VMAX Thin Pool Failed
Status:
Fixed
Severity:
6 Enhancement
Description:

Symptom:
UCSD 5.3.2.0 / Bind Thin Device to VMAX Thin Pool Failed

Conditions:
None

Workaround:
None

Further Problem Description:
None

Last Modified:
31-MAY-2016
Known Affected Releases:
5.3(2.0)
Known Fixed Releases: *
5.3(2.1), 5.4(0.1), 5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz37880
Title:
No option to specify same or different remote oracle DB while restore
Status:
Open
Severity:
6 Enhancement
Description: *

Symptom:
FTP backup is not supported for the Oracle DB configured UCSD server.

Conditions:
1. Login to shelladmin and take back up using the option 7.
2. Restore the DB by enter the option 8.
3. After services stopped, Enter the backup file to restore.
4. While restoring it is not asking for the remote DB option like same or different DB. Because if user want to restore the backup files of other DB, they need to copy that file from the path of other Oracle DB /u01/app/oracle/admin//dpdump to the current oracle DB and need to perform restore.

Workaround:
Copying backup file under the path /u01/app/oracle/admin/ebdb/dpdump/ from one Oracle remote machine to another remote Oracle machine may help in restoring DB in any Oracle configured server.

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.5(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuz11959
Title:
UCSD for expansion module 3 and 4
Status:
Open
Severity:
6 Enhancement
Description:

Symptom:
After you click the button ?configure expansion module ports?,you will open a window which can change fi port mode from ether to fc.
But this window only has the port belong to module 2. You can't find port of module 3 and 4.

Conditions:
NA

Workaround:
NA

Further Problem Description:
NA

Last Modified:
25-MAY-2016
Known Affected Releases: *
5.4(0.2), 5.5(0.0)
Known Fixed Releases:
Alert Type:
Updated *
Bug Id:
CSCuy65042
Title:
Enable configuration or remove Remote Desktop option from VM in VACS
Status:
Fixed
Severity:
6 Enhancement
Description:

Symptom:
Drop down option of remote desktop upon using the Launch VM Client button on a Windows VM in a VACS container.

Conditions:
In the context of a VM that is running Windows OS and is inside a VACS container

Workaround:
None

Further Problem Description:
NA

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)
Alert Type:
Updated *
Bug Id:
CSCuz65776
Title:
Session management for Nexus Devices for timeout issue
Status:
Fixed
Severity:
6 Enhancement
Description:

Symptom:
Rollback of SR for 'Create SAN ZONE' is failing with session limit exceeded error

Conditions:
If more sessions are opened from UCSD than the configured session on the devices or if session opening and closing is taking longer time.

Workaround:
Increase session count on the device

Further Problem Description:

Last Modified:
31-MAY-2016
Known Affected Releases:
5.4(0.2)
Known Fixed Releases: *
5.5(0.0)

Find additional information in Bug Search index.

 

2015 Cisco and/or its affiliates. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks

 

没有评论:

发表评论