|Summary:||[openstack] Backport bulk inspection error output|
|Product:||Red Hat OpenStack||Reporter:||Joe Talerico <jtaleric>|
|Component:||python-rdomanager-oscplugin||Assignee:||Brad P. Crochet <brad>|
|Status:||CLOSED ERRATA||QA Contact:||Omri Hochman <ohochman>|
|Version:||7.0 (Kilo)||CC:||apevec, athomas, brad, dcadzow, dmacpher, dyasny, hbrock, jslagle, lhh, mburns, nlevinki, rhel-osp-director-maint, tsedovic, yeylon|
|Target Release:||7.0 (Kilo)|
|Fixed In Version:||python-rdomanager-oscplugin-0.0.10-28.el7ost||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|:||1309824 (view as bug list)||Environment:|
|Last Closed:||2016-02-18 16:53:14 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Joe Talerico 2016-02-10 17:26:11 UTC
Description of problem: OSP7 openstack baremetal bulk introspection returns that there was a error, but does not return which nodes had errors. Liberty has a patch to have a bit more output with failures.
Comment 2 Angus Thomas 2016-02-11 11:01:07 UTC
We can't backport this into the 7.3 release, because we're out of time and this is essentially an RFE, rather than a fix for a regression. In addition to aaddressing this in the next release, we can look into creating a validation check to assist with this. Those are consumable by field engineers deploying OSP director as soon as they're written and don't need to wait for a product release. Tomas, can you please look into addressing this issue with a validation?
Comment 3 Dan Yasny 2016-02-11 17:17:58 UTC
duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1302386 maybe?
Comment 4 Mike Burns 2016-02-11 17:27:37 UTC
(In reply to Dan Yasny from comment #3) > duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1302386 maybe? No, this bug handles the return code for bulk introspection. The other one just makes a host failure more visible. They're similar, but not duplicates.
Comment 6 Dan Macpherson 2016-02-16 06:49:04 UTC
Mike, do you know if this bug will make it to 7.3? Angus seemed to indicate that it wouldn't in comment #2.
Comment 8 errata-xmlrpc 2016-02-18 16:53:14 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0264.html