yahoo-eng-team team mailing list archive

[Diana Clarke <diana.joan.clarke@xxxxxxxxx>]

Public bug reported:

When you attempt to 'nova volume-update' a stopped instance, the block
device mapping connection_info is corrupted (it points to the new volume
despite the failure).

  1. create an instance (instance-1)
  2. create two volumes (vol-1 & vol-2)
  3. attach volume: nova volume-attach instance-1 <vol-1-uuid>
  4. nova stop instance-1
  5. swap volume: nova volume-update instance-1 <vol-1-uuid> <vol-2-uuid>
  6. swap will fail, but the connection info points to vol-2 now

Example notes using stable/newton devstack:

   http://paste.openstack.org/show/586715/

A similar downstream bug report:

  Can't re-start a stopped instance after trying to volume-update on it 
  https://bugzilla.redhat.com/show_bug.cgi?id=1373318

** Affects: nova
     Importance: Undecided
     Assignee: Diana Clarke (diana-clarke)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Diana Clarke (diana-clarke)

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

Title:
  'nova volume-update' corrupts BDM connection_info when guest is
  stopped

Status in OpenStack Compute (nova):
  New

Bug description:
  When you attempt to 'nova volume-update' a stopped instance, the block
  device mapping connection_info is corrupted (it points to the new
  volume despite the failure).

    1. create an instance (instance-1)
    2. create two volumes (vol-1 & vol-2)
    3. attach volume: nova volume-attach instance-1 <vol-1-uuid>
    4. nova stop instance-1
    5. swap volume: nova volume-update instance-1 <vol-1-uuid> <vol-2-uuid>
    6. swap will fail, but the connection info points to vol-2 now

  Example notes using stable/newton devstack:

     http://paste.openstack.org/show/586715/

  A similar downstream bug report:

    Can't re-start a stopped instance after trying to volume-update on it 
    https://bugzilla.redhat.com/show_bug.cgi?id=1373318

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