Bug 1327275 - Rerunning introspection on the same set of nodes might be broken [NEEDINFO]
Summary: Rerunning introspection on the same set of nodes might be broken
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-ironic-inspector
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: async
: 8.0 (Liberty)
Assignee: Dmitry Tantsur
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-14 16:09 UTC by Dmitry Tantsur
Modified: 2016-06-15 12:39 UTC (History)
4 users (show)

Fixed In Version: openstack-ironic-inspector-2.2.6-1.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-15 12:39:22 UTC
Target Upstream Version:
dtantsur: needinfo? (jcoufal)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1570447 0 None None None 2016-04-14 16:09:51 UTC
Red Hat Product Errata RHBA-2016:1229 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 8 director Bug Fix Advisory 2016-06-15 16:38:45 UTC

Description Dmitry Tantsur 2016-04-14 16:09:52 UTC 
The simplest reproducer is running introspection on only one node, waiting for the finish, then running again on the same node.
Comment 2 Dmitry Tantsur 2016-05-09 15:18:32 UTC 
ironic-inspector 2.2.6 was released upstream with the fix for this bug. I think we should update.
Comment 4 Raviv Bar-Tal 2016-05-19 13:21:20 UTC 
Manual installed openstack-ironic-inspector-2.2.6-1.el7ost.noarch and repeatedly Run introspection for 10 time on the same nodes.

All introspections pass with no errors
Comment 6 errata-xmlrpc 2016-06-15 12:39:22 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://access.redhat.com/errata/RHBA-2016:1229
Note You need to log in before you can comment on or make changes to this bug.