Ironic compute node doesn't take over nodes with instance when the owner compute node is down

Bug #1730834 reported by Min Sun
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Low
Unassigned

Bug Description

   Description
   ===========
   Ironic compute node doesn't take over nodes with instance when the owner compute node is down

   Steps to reproduce
   ==================
   1. I have two ironic compute nodes & two BM nodes
   2. BM1 is controlled by node1, BM2 is controlled by node2
   3. I boot an instance on BM1
   4. Stop nova-compute service on node1
   5. node2 doesn't take over BM1 although node1 is not available

   Expected result
   ===============
   What I expect is that when node1 id down node2 can take over BM1.

   Actual result
   =============
   node1 doesn't take over BM1.
   And all nova operate action will fail as BM1 has nova compute service on node1 is down

   Environment
   ===========
   openstack-nova-common-14.0.3-9.el7ost.noarch
   openstack-nova-novncproxy-14.0.3-9.el7ost.noarch
   openstack-nova-scheduler-14.0.3-9.el7ost.noarch
   python-novaclient-6.0.0-1.el7ost.noarch
   openstack-nova-conductor-14.0.3-9.el7ost.noarch
   openstack-nova-api-14.0.3-9.el7ost.noarch
   python-nova-14.0.3-9.el7ost.noarch
   openstack-nova-cert-14.0.3-9.el7ost.noarch
   openstack-nova-console-14.0.3-9.el7ost.noarch
   openstack-nova-compute-14.0.3-9.el7ost.noarch
   openstack-nova-common-14.0.3-9.el7ost.noarch

Tags: ironic
Min Sun (minsu)
description: updated
tags: added: ironic
Revision history for this message
Min Sun (minsu) wrote :

Anyone meets the same issue here?

Revision history for this message
Jim Rollenhagen (jim-rollenhagen) wrote :

This is expected with the current code. See the release note: https://github.com/openstack/nova/blob/master/releasenotes/notes/ironic-driver-hash-ring-7d763d87b9236e5d.yaml#L10-L16

We should make this better, I agree, so we should leave this bug open. But, it's low priority and probably needs a blueprint when we do it.

Changed in nova:
status: New → Confirmed
Changed in nova:
importance: Undecided → Low
Changed in nova:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on nova (master)

Change abandoned by "Julia Kreger <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/nova/+/813897
Reason: The consensus from the PTG was to refactor the driver to utilize a static mapping. Specifically the introduction of Shard Keys https://review.opendev.org/c/openstack/ironic-specs/+/861803 and their use in the nova.virt.ironic driver https://review.opendev.org/c/openstack/nova-specs/+/862833

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.