Bug 1330590 - Need to run ironic-inspector-dbsync after dropping DB
Summary: Need to run ironic-inspector-dbsync after dropping DB
Keywords:
Status: CLOSED DUPLICATE of bug 1328237
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 14:13 UTC by David Juran
Modified: 2016-04-27 15:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-27 15:02:04 UTC
Target Upstream Version:

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

Description David Juran 2016-04-26 14:13:20 UTC 
Description of problem:
In procedure 11.3, step 2 on https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/director-installation-and-usage/112-troubleshooting-hardware-introspection it is described how one can remove the file /var/lib/ironic-inspector/inspector.sqlite if introspection is interrupted. If this procedure is carried out, however, one must also run


ironic-inspector-dbsync --config-file /etc/ironic-inspector/inspector.conf upgrade

to re-populate the DB, otherwise subsequent introspection attempts will fail.
Comment 2 David Juran 2016-04-27 15:02:04 UTC 

*** This bug has been marked as a duplicate of bug 1328237 ***
Note You need to log in before you can comment on or make changes to this bug.