Bug 684030

Summary: Update Cisco UCS XML-Based fencing agent to support UCS sub-orgs
Product: Red Hat Enterprise Linux 5 Reporter: Eric Williams <ericwill>
Component: cmanAssignee: Lon Hohberger <lhh>
Status: CLOSED DUPLICATE QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.5CC: cluster-maint, djansa, edamato
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-14 14:01:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Eric Williams 2011-03-10 22:36:38 UTC
Description of problem:
Customers using the Cisco UCS XML-Based fencing agent have notified Cisco that the XML-based agent only works to fence service profiles for blades that are in the top level (org-root) tree.  

Version-Release number of selected component (if applicable):


How reproducible:
Very

Steps to Reproduce:
1.  Create a sub-org in UCS (ex. org-root/org-testing123)
2.  Create a new service profile in the sub-org created in step 1 (ex. service profile ls-test in org-root/org-testing123.)
3.  Specify org-root/org-testing123/ls-test service profile as Service profile to be fenced
  
Actual results:
Fencing agent fails.

Expected results:
Fencing agent should support multi-heirarchy that UCS supports.  Max number of UCS org levels is set at 5 deep.

Additional info:

Comment 2 Perry Myers 2011-03-14 14:01:33 UTC

*** This bug has been marked as a duplicate of bug 678902 ***