tempest

  1. Bug #1807723
  2. Comment #9

Comment 9 for bug 1807723

Revision history for this message
Matt Riedemann (mriedem) wrote : Re: swap multiattach volume intermittently fails when servers are on different hosts

We start deleting server2 here:

http://logs.openstack.org/81/606981/4/check/tempest-slow/fafde23/controller/logs/screen-n-cpu.txt.gz#_Dec_08_01_45_42_924650

Dec 08 01:45:42.924650 ubuntu-xenial-ovh-gra1-0001066161 nova-compute[32186]: INFO nova.compute.manager [None req-a0211268-269b-4227-ba65-a680ec13b6e3 tempest-TestMultiAttachVolumeSwap-1803326020 tempest-TestMultiAttachVolumeSwap-1803326020] [instance: e0b74695-f9a0-4f4c-8a08-a0de3420cc6c] Terminating instance

Interestingly I don't see anything in there about disconnecting from volume1 which likely means the code to get the BDM that represents volume1 and server2 is not found. And that's likely the reason trying to delete volume1 fails - because when deleting server2, which is the only thing that's supposed to be attached to volume1 after the swap volume (server1 swaps from vol1 to vol2), we should be disconnecting from volume1 but are not and the target connection is left intact.