yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

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

** Changed in: nova
    Milestone: None => liberty-rc1

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

Title:
  Resize to a flavor with swap doesn't create the swap device if a
  volume is attached

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  1.
  ii  nova-common                      1:2014.2-fuel6.0~mira19                    OpenStack Compute - common files
  ii  nova-compute                     1:2014.2-fuel6.0~mira19                    OpenStack Compute - compute node base
  ii  nova-compute-kvm                 1:2014.2-fuel6.0~mira19                    OpenStack Compute - compute node (KVM)
  ii  nova-compute-libvirt             1:2014.2-fuel6.0~mira19                    OpenStack Compute - compute node libvirt

  I'm using RBD storage.

  3.

  * I have a VM instance created with a default flavor i.e. named "m1.medium" and a volume attached in /dev/vdb.
  * Then I create a new flavor "m1.medium.swap" with swap field populated
  * Then I resize the previous VM instance to this new flavor.

  Expected result:

  * When I restart the VM instance I found the swap disk and the volume
  attached (/dev/vdb).

  Actual result:

  * When I restart the VM instance and volume attached (/dev/vdb) but I
  cannot found the swap disk.

  thanks,

  Salvo.

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