Bug 1246053 - Inconsistency between node state in nova and ironic.
Summary: Inconsistency between node state in nova and ironic.
Keywords:
Status: CLOSED DUPLICATE of bug 1245298
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director
Version: Director
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: y2
: 7.0 (Kilo)
Assignee: Lucas Alvares Gomes
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-23 11:49 UTC by Leonid Natapov
Modified: 2016-04-18 06:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-30 17:02:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Leonid Natapov 2015-07-23 11:49:23 UTC
Inconsistency between node state in nova and ironic.
I have same node showed differently when running nova list and ironic node-list:
Nova shows that node is SHUTOFF Shutdown while ironic shows it as Power on/Active (which is the actual node's state)



+--------------------------------------+------------------------+---------+------------+-------------+---------------------+
| ID                                   | Name                   | Status  | Task State | Power State | Networks            |
+--------------------------------------+------------------------+---------+------------+-------------+---------------------+
| 3056860b-94ef-4db0-89b0-2f86299486a7 | overcloud-compute-0    | ACTIVE  | -          | Running     | ctlplane=192.0.2.22 |
| efd6c966-6300-4920-8ffd-b63519d19ced | overcloud-controller-0 | SHUTOFF | -          | Shutdown    | ctlplane=192.0.2.21 |
| 2ad0de1f-c195-4305-98ff-56210a23ed43 | overcloud-controller-1 | ACTIVE  | -          | Running     | ctlplane=192.0.2.23 |
| 3ff1c27c-2f02-4874-9c15-b7130763c613 | overcloud-controller-2 | ACTIVE  | -          | Running     | ctlplane=192.0.2.24 |
+--------------------------------------+------------------------+---------+------------+-------------+---------------------+
[stack@puma42 ~]$ ironic node-list
+--------------------------------------+------+--------------------------------------+-------------+-----------------+-------------+
| UUID                                 | Name | Instance UUID                        | Power State | Provision State | Maintenance |
+--------------------------------------+------+--------------------------------------+-------------+-----------------+-------------+
| ad32ddf2-61d5-4520-9432-e91cd9814a25 | None | efd6c966-6300-4920-8ffd-b63519d19ced | power on    | active          | False       |
| bd628d7a-6aad-4f2f-a7a9-ba2239ba35f9 | None | 3056860b-94ef-4db0-89b0-2f86299486a7 | power on    | active          | False       |
| af3a40ec-169d-4aab-b08b-038e3991c656 | None | 3ff1c27c-2f02-4874-9c15-b7130763c613 | power on    | active          | False       |
| 1a50437e-29ad-4c8b-8bc6-e27f28263478 | None | 2ad0de1f-c195-4305-98ff-56210a23ed43 | power on    | active          | False       |
+--------------------------------------+------+--------------------------------------+-------------+-----------------+-------------+

Comment 3 James Slagle 2015-07-23 16:42:00 UTC
did the 2 states ever go back in sync? There is an interval defined in /etc/nova/nova.conf, sync_power_state_interval, which defaults to 600 seconds. So it's possible the 2 would get in sync eventually.

If not, please attach /var/log/nova/* and /var/log/ironic/*

Comment 5 Leonid Natapov 2015-07-23 17:05:05 UTC
(In reply to James Slagle from comment #3)
> did the 2 states ever go back in sync? There is an interval defined in
> /etc/nova/nova.conf, sync_power_state_interval, which defaults to 600
> seconds. So it's possible the 2 would get in sync eventually.
> 
> If not, please attach /var/log/nova/* and /var/log/ironic/*

no,never.

Comment 6 James Slagle 2015-07-23 17:14:27 UTC
please attach /var/log/nova/* and /var/log/ironic/*

Comment 8 Lucas Alvares Gomes 2015-11-30 17:02:49 UTC

*** This bug has been marked as a duplicate of bug 1245298 ***


Note You need to log in before you can comment on or make changes to this bug.