nova compute may fail on startup with ironic virt driver

Bug #1660581 reported by Vladyslav Drok
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
devstack
Invalid
Undecided
Unassigned
grenade
Fix Released
Undecided
Unassigned

Bug Description

Nowadays, we do not ensure that keystone is running prior to doing start_nova_compute. In case of ironic, it causes trouble, as ironic client cannot initialize without keystone and compute fails if the apache was being restarted at that moment. This was fixed previously on ironic side, but recently, another place was introduced in grenade: https://review.openstack.org/#/c/424730/.

The problem described here can be seen in http://logs.openstack.org/30/424730/18/check/gate-grenade-dsvm-ironic-ubuntu-xenial-nv/3bb8d4d/logs/new/screen-n-cpu.txt.gz?level=ERROR and http://logs.openstack.org/30/424730/18/check/gate-grenade-dsvm-ironic-ubuntu-xenial-nv/3bb8d4d/logs/apache/error.txt.gz - apache was restarting while ironic client tried to initialize.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to devstack (master)

Fix proposed to branch: master
Review: https://review.openstack.org/427098

Changed in devstack:
assignee: nobody → Vasyl Saienko (vsaienko)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on devstack (master)

Change abandoned by Vasyl Saienko (<email address hidden>) on branch: master
Review: https://review.openstack.org/427098

Revision history for this message
Vasyl Saienko (vsaienko) wrote :

In addition, nova-compute will not start as nova is upgraded prior to Ironic.
Until grenade allows to setup dependency between services during upgrade https://bugs.launchpad.net/grenade/+bug/1660646 we should ignore nova-compute service status on nova upgrade phase.

Revision history for this message
John L. Villalovos (happycamp) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to grenade (master)

Reviewed: https://review.openstack.org/427248
Committed: https://git.openstack.org/cgit/openstack-dev/grenade/commit/?id=99c8c9e998ea9a95845958fd6b1f8dbae9fadef1
Submitter: Jenkins
Branch: master

commit 99c8c9e998ea9a95845958fd6b1f8dbae9fadef1
Author: Vasyl Saienko <email address hidden>
Date: Tue Jan 31 17:16:36 2017 +0200

    Do not wait for nova-compute when ironic is enabled

    Ironic should be upgraded before nova according to requirements [0]
    using reverse order will lead to nova-compute start failure.
    This patch ensures that we do not check nova-compute status in the
    nova upgarde phase, when ironic is enabled, as it is expected behaviour.
    Ironic will restart nova-compute later.

    [0] http://docs.openstack.org/developer/ironic/deploy/upgrade-guide.html#general-upgrades-all-versions

    Change-Id: I48dc7649eedb6c6d6753da8ba66fcfccb09acd58
    Closes-Bug: #1660581
    Related-Bug: #1660646

Changed in grenade:
status: New → Fix Released
Revision history for this message
Sean Dague (sdague) wrote :

No open reviews found in this bug, unassigning. Please add a comment with active reviews before assigning an individual, or tag the bug in the gerrit review, which will do that automatically. We try not to assign bugs without patches as that discourages other folks from looking into bugs.

Changed in devstack:
assignee: Vasyl Saienko (vsaienko) → nobody
status: In Progress → New
Revision history for this message
Dr. Jens Harbott (j-harbott) wrote :

Seems that this was fixed in grenade.

Changed in devstack:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.