Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1463224

Summary: iDRAC get/set power state fails (OSP-9)
Product: Red Hat OpenStack Reporter: Jaison Raju <jraju>
Component: python-dracclientAssignee: RHOS Maint <rhos-maint>
Status: CLOSED WONTFIX QA Contact: nlevinki <nlevinki>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0 (Mitaka)CC: apevec, arkady_kanevsky, bfournie, cdevine, christopher_dearborn, dcain, dsneddon, dtantsur, jjoyce, John_walsh, jraju, jschluet, kurt_hey, lhh, mburns, morazi, nlevinki, pmannidi, racedoro, rajini.karthik, randy_perryman, smerrow, sreichar
Target Milestone: ---Keywords: OtherQA, Triaged, ZStream
Target Release: 9.0 (Mitaka)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1428005 Environment:
Last Closed: 2017-11-04 20:46:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1428005    
Bug Blocks: 1356451, 1428008    

Comment 3 Bob Fournier 2017-09-03 18:59:04 UTC 
So, this is merged to OSP-10.  As there is a workaround for OSP-9, can we change the 
Target Release to osp-10 from osp-9, i.e. not merge to osp-9?
Comment 4 Jaison Raju 2017-11-02 00:04:40 UTC 
(In reply to Bob Fournier from comment #3)
> So, this is merged to OSP-10.  As there is a workaround for OSP-9, can we
> change the 
> Target Release to osp-10 from osp-9, i.e. not merge to osp-9?
Its already fixed in RHOS10 .
https://bugzilla.redhat.com/show_bug.cgi?id=1428005
Comment 5 Bob Fournier 2017-11-02 00:09:21 UTC 
>> So, this is merged to OSP-10.  As there is a workaround for OSP-9, can we
>> change the 
>> Target Release to osp-10 from osp-9, i.e. not merge to osp-9?
>Its already fixed in RHOS10 .
>https://bugzilla.redhat.com/show_bug.cgi?id=1428005

Yes as I indicated this is fixed in OSP-10, but this bug is targeted to OSP-9.
Can we just use the workaround for OSP-9 and not merge this fix?
Comment 7 Bob Fournier 2017-11-04 20:46:13 UTC 
Thanks a lot Jaison.  I'm going to close this then as we have a separate BZ for OSP-10 that tracks the fix.