yahoo-eng-team team mailing list archive

[gustavo panizzo <1384121@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

if i run nova evacuate --on-shared-storage.  nova-compute (on the
destination node) will try to delete the non-existent port in br-int
failing and making the migration to fail.


2014-10-22 04:48:29.853 6723 AUDIT nova.compute.manager [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Rebuilding instance
2014-10-22 04:48:29.854 6723 INFO nova.compute.manager [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] disk on shared storage, recreating using existing disk
2014-10-22 04:48:30.044 6723 ERROR nova.virt.libvirt.driver [-] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During wait destroy, instance disappeared.
2014-10-22 04:48:30.076 6723 ERROR nova.network.linux_net [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] Unable to execute ['ovs-vsctl', '--timeout=120', 'del-port', u'br-int', u'qvoc57306e5-38']. Exception: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 del-port br-int qvoc57306e5-38
Exit code: 1
Stdout: ''
Stderr: 'ovs-vsctl: no port named qvoc57306e5-38\n'
2014-10-22 04:48:30.126 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Deleting instance files /var/lib/nova/instances/14ed2298-a72e-49bd-9151-c1c24f364970
2014-10-22 04:48:30.128 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Deletion of /var/lib/nova/instances/14ed2298-a72e-49bd-9151-c1c24f364970 complete
2014-10-22 04:48:30.354 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Creating image
2014-10-22 04:48:31.323 6723 INFO nova.compute.manager [-] Lifecycle event 0 on VM 14ed2298-a72e-49bd-9151-c1c24f364970
2014-10-22 04:48:31.389 6723 INFO nova.compute.manager [req-9a7d0c21-92d2-4a09-8e32-bbf67684224d None None] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During sync_power_state the instance has a pending task (rebuild_spawning). Skip.
2014-10-22 04:48:31.389 6723 INFO nova.compute.manager [-] Lifecycle event 2 on VM 14ed2298-a72e-49bd-9151-c1c24f364970
2014-10-22 04:48:31.456 6723 INFO nova.compute.manager [-] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During sync_power_state the instance has a pending task (rebuild_spawning). Skip.


eventually vif creation will timeout 

if i don't tell nova to use shared-storage evacuation works just fine


i'm running icehouse update .1 and .2 i see the problem on both versions

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: icehouse-backport-potential

** Summary changed:

- evacuate --on-shared-storage tries to delete the vm port on new vm and fails
+ evacuate --on-shared-storage tries to delete the vm port on new compute node and fails

-- 
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/1384121

Title:
  evacuate --on-shared-storage tries to delete the vm port on new
  compute node and fails

Status in OpenStack Compute (Nova):
  New

Bug description:
  if i run nova evacuate --on-shared-storage.  nova-compute (on the
  destination node) will try to delete the non-existent port in br-int
  failing and making the migration to fail.

  
  2014-10-22 04:48:29.853 6723 AUDIT nova.compute.manager [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Rebuilding instance
  2014-10-22 04:48:29.854 6723 INFO nova.compute.manager [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] disk on shared storage, recreating using existing disk
  2014-10-22 04:48:30.044 6723 ERROR nova.virt.libvirt.driver [-] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During wait destroy, instance disappeared.
  2014-10-22 04:48:30.076 6723 ERROR nova.network.linux_net [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] Unable to execute ['ovs-vsctl', '--timeout=120', 'del-port', u'br-int', u'qvoc57306e5-38']. Exception: Unexpected error while running command.
  Command: sudo nova-rootwrap /etc/nova/rootwrap.conf ovs-vsctl --timeout=120 del-port br-int qvoc57306e5-38
  Exit code: 1
  Stdout: ''
  Stderr: 'ovs-vsctl: no port named qvoc57306e5-38\n'
  2014-10-22 04:48:30.126 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Deleting instance files /var/lib/nova/instances/14ed2298-a72e-49bd-9151-c1c24f364970
  2014-10-22 04:48:30.128 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Deletion of /var/lib/nova/instances/14ed2298-a72e-49bd-9151-c1c24f364970 complete
  2014-10-22 04:48:30.354 6723 INFO nova.virt.libvirt.driver [req-a856a797-f5c7-41c0-a949-de68e8ddbdfd 184136c2674746b5a4b27d3b13ca91f8 d42aacf8661045beb3a9ee7585bb0c8a] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] Creating image
  2014-10-22 04:48:31.323 6723 INFO nova.compute.manager [-] Lifecycle event 0 on VM 14ed2298-a72e-49bd-9151-c1c24f364970
  2014-10-22 04:48:31.389 6723 INFO nova.compute.manager [req-9a7d0c21-92d2-4a09-8e32-bbf67684224d None None] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During sync_power_state the instance has a pending task (rebuild_spawning). Skip.
  2014-10-22 04:48:31.389 6723 INFO nova.compute.manager [-] Lifecycle event 2 on VM 14ed2298-a72e-49bd-9151-c1c24f364970
  2014-10-22 04:48:31.456 6723 INFO nova.compute.manager [-] [instance: 14ed2298-a72e-49bd-9151-c1c24f364970] During sync_power_state the instance has a pending task (rebuild_spawning). Skip.

  
  eventually vif creation will timeout 

  if i don't tell nova to use shared-storage evacuation works just fine

  
  i'm running icehouse update .1 and .2 i see the problem on both versions

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