Bug 1330590

Summary: Need to run ironic-inspector-dbsync after dropping DB
Product: Red Hat OpenStack Reporter: David Juran <djuran>
Component: documentationAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED DUPLICATE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: srevivo
Target Milestone: ---Keywords: Documentation, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-27 15:02:04 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:

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 ***