[Yahoo-eng-team] [Bug 1546778] Re: libvirt: resize with deleted backing image fails

2017-06-16 Thread Sean Dague
** Changed in: nova/liberty
   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/1546778

Title:
  libvirt: resize with deleted backing image fails

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Won't Fix
Status in OpenStack Compute (nova) liberty series:
  Fix Released

Bug description:
  Once the glance image from which an instance was spawned is deleted,
  resizes of that image fail if they would take place across more than
  one compute node. Migration and live block migration both succeed.

  Resize fails, I believe, because 'qemu-img resize' is called
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7218-L7221)
  before the backing image has been transferred from the source compute
  node
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7230-L7233).

  Replication requires two compute nodes. To replicate:

  1. Boot an instance from an image or snapshot.
  2. Delete the image from Glance.
  3. Resize the instance. It will fail with an error similar to:

  Stderr: u"qemu-img: Could not open '/var/lib/nova/instances/f77f1c5c-
  71f7-4645-afa1-dd30bacef874/disk': Could not open backing file: Could
  not open
  '/var/lib/nova/instances/_base/ca94b18d94077894f4ccbaafb1881a90225f1224':
  No such file or directory\n"

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1546778] Re: libvirt: resize with deleted backing image fails

2016-03-21 Thread Matt Riedemann
There is a backport proposed to stable/kilo but I don't think we should
take it since the original fix for this introduced a regression which we
are having to fix on master, stable/mitaka and stable/liberty now. I'd
rather not deal with that in stable/kilo too.

** Also affects: nova/kilo
   Importance: Undecided
   Status: New

** Changed in: nova/kilo
   Status: New => Won't Fix

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

Title:
  libvirt: resize with deleted backing image fails

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) kilo series:
  Won't Fix
Status in OpenStack Compute (nova) liberty series:
  Fix Committed

Bug description:
  Once the glance image from which an instance was spawned is deleted,
  resizes of that image fail if they would take place across more than
  one compute node. Migration and live block migration both succeed.

  Resize fails, I believe, because 'qemu-img resize' is called
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7218-L7221)
  before the backing image has been transferred from the source compute
  node
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7230-L7233).

  Replication requires two compute nodes. To replicate:

  1. Boot an instance from an image or snapshot.
  2. Delete the image from Glance.
  3. Resize the instance. It will fail with an error similar to:

  Stderr: u"qemu-img: Could not open '/var/lib/nova/instances/f77f1c5c-
  71f7-4645-afa1-dd30bacef874/disk': Could not open backing file: Could
  not open
  '/var/lib/nova/instances/_base/ca94b18d94077894f4ccbaafb1881a90225f1224':
  No such file or directory\n"

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1546778] Re: libvirt: resize with deleted backing image fails

2016-03-08 Thread OpenStack Infra
Reviewed:  https://review.openstack.org/288640
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=db7fd539f261ea53f6c005478049424b9dae1543
Submitter: Jenkins
Branch:master

commit db7fd539f261ea53f6c005478049424b9dae1543
Author: Matthew Booth 
Date:   Fri Mar 4 18:34:21 2016 +

libvirt: Fix resize of instance with deleted glance image

finish_migration() in the libvirt driver was attempting to resize an
image before checking that its backing file was present. This patch
re-orders these 2 operations. In doing so, we also have to resolve an
overloading of the 'disk_info' variable.

Closes-Bug: #1546778

Change-Id: I03e08fae97416ebe5cdedcf238a06d1b90203c5d


** Changed in: nova
   Status: In Progress => 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/1546778

Title:
  libvirt: resize with deleted backing image fails

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) liberty series:
  New

Bug description:
  Once the glance image from which an instance was spawned is deleted,
  resizes of that image fail if they would take place across more than
  one compute node. Migration and live block migration both succeed.

  Resize fails, I believe, because 'qemu-img resize' is called
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7218-L7221)
  before the backing image has been transferred from the source compute
  node
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7230-L7233).

  Replication requires two compute nodes. To replicate:

  1. Boot an instance from an image or snapshot.
  2. Delete the image from Glance.
  3. Resize the instance. It will fail with an error similar to:

  Stderr: u"qemu-img: Could not open '/var/lib/nova/instances/f77f1c5c-
  71f7-4645-afa1-dd30bacef874/disk': Could not open backing file: Could
  not open
  '/var/lib/nova/instances/_base/ca94b18d94077894f4ccbaafb1881a90225f1224':
  No such file or directory\n"

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1546778] Re: libvirt: resize with deleted backing image fails

2016-03-07 Thread Matt Riedemann
** Changed in: nova
   Importance: Undecided => Medium

** Tags added: libvirt resize

** Also affects: nova/liberty
   Importance: Undecided
   Status: New

** Tags added: liberty-backport-potential

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

Title:
  libvirt: resize with deleted backing image fails

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) liberty series:
  New

Bug description:
  Once the glance image from which an instance was spawned is deleted,
  resizes of that image fail if they would take place across more than
  one compute node. Migration and live block migration both succeed.

  Resize fails, I believe, because 'qemu-img resize' is called
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7218-L7221)
  before the backing image has been transferred from the source compute
  node
  
(https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L7230-L7233).

  Replication requires two compute nodes. To replicate:

  1. Boot an instance from an image or snapshot.
  2. Delete the image from Glance.
  3. Resize the instance. It will fail with an error similar to:

  Stderr: u"qemu-img: Could not open '/var/lib/nova/instances/f77f1c5c-
  71f7-4645-afa1-dd30bacef874/disk': Could not open backing file: Could
  not open
  '/var/lib/nova/instances/_base/ca94b18d94077894f4ccbaafb1881a90225f1224':
  No such file or directory\n"

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp