That's all very useful advise -- thank you. :)
On Sun, Mar 29, 2015 at 8:39 PM, gustavo panizzo (gfa)
wrote:
>
>
> On 03/29/2015 11:19 AM, Joe Topjian wrote:
>
>> Hello,
>>
>> Without specifying a rescue image, Nova will use the image that the
>> instance is based on when performing a rescue.
>>
On 03/29/2015 11:19 AM, Joe Topjian wrote:
Hello,
Without specifying a rescue image, Nova will use the image that the
instance is based on when performing a rescue.
I've noticed that this is problematic for "cloud-friendly" images such
as the official Ubuntu images and the newer CentOS 7 imag
Hello,
Without specifying a rescue image, Nova will use the image that the
instance is based on when performing a rescue.
I've noticed that this is problematic for "cloud-friendly" images such as
the official Ubuntu images and the newer CentOS 7 images. I'm finding that
/dev/vdb still ends up mou
Hi,
I am running OpenStack nova 2.17.0 on Ubuntu 14.04.1 with libvirt 1.2.2
and QEMU 2.0.0 (Debian 2.0.0+dfsg-2ubuntu1.5).
When attempting to nova rescue an instance, the instance boots with
updated libvirt XML but ends up booting to the old, non-rescue disk
(second disk in XML) 80% of the time.
