yahoo-eng-team team mailing list archive

[Alan Pevec <1180178@xxxxxxxxxxxxxxxxxx>]

** Changed in: nova/grizzly
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1180178

Title:
  Instance IP addresses are re-used even when previous instance could
  not be powered off

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Released
Status in tripleo - openstack on openstack:
  Triaged

Bug description:
  Expected:

    When a baremetal instance is deleted, but cannot be powered off, its
  ip addresses should not be assigned to any new instances.

  Actual:
    The still-on baremetal instance's IP may be reassigned to a new instance.

  Environment:
    - nova trunk as it existed a few days ago
    - IPMI power driver
    - quantum-ovs trunk

  Repro:
    - boot a baremetal instance
    - nova delete the instance, but ensure it cannot be powered off by nova
    - boot new instances until a new one gets the same ip - now there are two nodes who think they have the same ip.

  nova-list excerpt:

  | eb25c949-e1d4-48a5-a041-8aa8a53becb5 | notcompute-clint2.notcompute              | ACTIVE | deleting   | Running     | ctlplane=10.10.16.139 |
  | 4959c430-7a4a-408a-9a8c-43bb54cea06c | notcompute-clint3.notcompute              | ACTIVE | None       | Running     | ctlplane=10.10.16.139 |

  nova-compute.log of instance boot followed by instance delete with
  power-off failure:

  /var/log/upstart/nova-compute.log:2013-05-15 01:18:58,432.432 23016 INFO nova.virt.baremetal.pxe [-] PXE deploy started for instance eb25c949-e1d4-48a5-a041-8aa8a53becb5
  /var/log/upstart/nova-compute.log:2013-05-15 01:19:50,442.442 23016 INFO nova.virt.baremetal.pxe [-] PXE deploy completed for instance eb25c949-e1d4-48a5-a041-8aa8a53becb5
  /var/log/upstart/nova-compute.log:2013-05-15 03:02:45,763.763 23016 AUDIT nova.compute.manager [req-4bb96dfc-7a3e-44b5-86cd-a5e9e28b7064 87b44714e906420a9e6a07f6835b5b61 c30643483cd849a6b61e98c6ccc03a66] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] Terminating instance
  /var/log/upstart/nova-compute.log:2013-05-15 03:02:51,784.784 23016 ERROR nova.virt.baremetal.driver [req-4bb96dfc-7a3e-44b5-86cd-a5e9e28b7064 87b44714e906420a9e6a07f6835b5b61 c30643483cd849a6b61e98c6ccc03a66] Error from baremetal driver during destroy: Baremetal power manager failed to stop node for instance u'eb25c949-e1d4-48a5-a041-8aa8a53becb5'
  /var/log/upstart/nova-compute.log:2013-05-15 03:02:52,062.062 23016 TRACE nova.openstack.common.rpc.amqp InstancePowerOffFailure: Baremetal power manager failed to stop node for instance u'eb25c949-e1d4-48a5-a041-8aa8a53becb5'
  /var/log/upstart/nova-compute.log:2013-05-15 03:12:20,978.978 23016 INFO nova.compute.manager [-] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] During sync_power_state the instance has a pending task. Skip.
  /var/log/upstart/nova-compute.log:2013-05-15 03:22:31,519.519 23016 INFO nova.compute.manager [-] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] During sync_power_state the instance has a pending task. Skip.
  /var/log/upstart/nova-compute.log:2013-05-15 03:32:42,251.251 23016 INFO nova.compute.manager [-] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] During sync_power_state the instance has a pending task. Skip.
  /var/log/upstart/nova-compute.log:2013-05-15 03:42:52,216.216 23016 INFO nova.compute.manager [-] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] During sync_power_state the instance has a pending task. Skip.
  /var/log/upstart/nova-compute.log:2013-05-15 03:53:03,285.285 23016 INFO nova.compute.manager [-] [instance: eb25c949-e1d4-48a5-a041-8aa8a53becb5] During sync_power_state the instance has a pending task. Skip

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1180178/+subscriptions