nova-libvirt-compare.py should handle VERIFY_RESIZE better
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Operators |
New
|
Undecided
|
Simon Leinen |
Bug Description
I just migrated a few SHUTOFF instances to other hypervisors. They have been moved to other hypervisors and are in VERIFY_RESIZE state now. nova-libvirt-
$ ./nova-
Possible inconsistency: Instance f783ca49-
On hypervisor zhdk0067.
Possible inconsistency: Instance a7b25635-
On hypervisor zhdk0065.
Possible inconsistency: Instance 32a01399-
On hypervisor zhdk0065.
Possible inconsistency: Instance e0208935-
On hypervisor zhdk0065.
Possible inconsistency: Instance cfa840b7-
On hypervisor zhdk0065.
Possible inconsistency: Instance d0ad605e-
On hypervisor zhdk0065.
Possible inconsistency: Instance 062944e5-
On hypervisor zhdk0065.
Possible inconsistency: Instance ecff603b-
On hypervisor zhdk0067.
Possible inconsistency: Instance e62feb7f-
On hypervisor zhdk0069.
Possible inconsistency: Instance 3633420d-
On hypervisor zhdk0065.
Instance cfa840b7-
Found on hypervisor zhdk0036.
Should be running on zhdk0065.
Instance ecff603b-
Found on hypervisor zhdk0036.
Should be running on zhdk0067.
Instance e62feb7f-
Found on hypervisor zhdk0041.
Should be running on zhdk0069.
Instance 3633420d-
Found on hypervisor zhdk0035.
Should be running on zhdk0065.
Instance e0208935-
Found on hypervisor zhdk0035.
Should be running on zhdk0065.
Instance f783ca49-
Found on hypervisor zhdk0035.
Should be running on zhdk0067.
Instance a7b25635-
Found on hypervisor zhdk0037.
Should be running on zhdk0065.
Instance d0ad605e-
Found on hypervisor zhdk0037.
Should be running on zhdk0065.
Instance 062944e5-
Found on hypervisor zhdk0037.
Should be running on zhdk0065.
Instance 32a01399-
Found on hypervisor zhdk0037.
Should be running on zhdk0065.
Is not bad that the script warns about instances in VERIFY_RESIZE, because if instances remain in that state for extended periods of time, that may point to a problem. But the warnings could be made less verbose. In particular, the fact that the instances are known to two hypervisors is completely normal.
In addition, we might only warn about VERIFY_RESIZE instances when desired (via a to-be-defined command flag) and/or when the state hasn't been modified more than a given amount of time ago.
Changed in osops: | |
assignee: | nobody → Simon Leinen (simon-leinen) |