<html><head></head><body>Hello,<br><br>Thanks, we will check these params.<br>Cheers<br><br><div class="gmail_quote">Le 9 février 2021 17:50:23 GMT+01:00, Lee Yarwood <lyarwood@redhat.com> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 09-02-21 12:23:58, Sean Mooney wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Tue, 2021-02-09 at 11:21 +0000, Arnaud Morin wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">Hey all,<br><br>From time to time we are facing an issue when puting instance in rescue<br>with the same image as the one the instance was booted.<br><br>E.G.<br>I booted an instance using Debian 10, disk are:<br><br>debian@testarnaud:~$ lsblk<br>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT<br>sr0 11:0 1 486K 0 rom <br>vda 254:0 0 10G 0 disk <br>└─vda1 254:1 0 10G 0 part /<br>debian@testarnaud:~$ cat /etc/fstab <br># /etc/fstab: static file system information.<br>UUID=5605171d-d590-46d5-85e2-60096b533a18 / ext4<br>errors=remount-ro 0 1<br><br><br><br>I rescued the instance:<br>$ openstack server rescue --image bc73a901-6366-4a69-8ddc-00479b4d647f testarnaud<br><br><br>Then, back in the instance:<br><br>debian@testarnaud:~$ lsblk<br>NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT<br>sr0 11:0 1 486K 0 rom <br>vda 254:0 0 2G 0 disk <br>└─vda1 254:1 0 2G 0 part <br>vdb 254:16 0 10G 0 disk <br>└─vdb1 254:17 0 10G 0 part /<br><br><br><br>Instance booted on /dev/vdb1 instead of /dev/vda1<br><br>Is there anything we can configure on nova side to avoid this<br>situation?<br></blockquote><br> in ussuri lee yarwood added<br> <a href="https://specs.openstack.org/openstack/nova-specs/specs/ussuri/implemented/virt-rescue-stable-disk-devices.html">https://specs.openstack.org/openstack/nova-specs/specs/ussuri/implemented/virt-rescue-stable-disk-devices.html</a><br> to nova which i belive will resolve the issue<br> <br> from ocata+ i think you can add hw_rescue_bus=usb to get a similar<br> effect but from ussuri we cahgne the layout so thtat the rescue disk<br> is always used. lee is that right?<br></blockquote><br>Yeah that's correct, from Ussuri (21.0.0) with the libvirt driver the<br>instance should continue to show all disks connected as normal with the<br>rescue disk appended last and always used as the boot device.<br><br>In your case, switching the rescue bus should change the default boot<br>device type n-cpu tells libvirt to use working around your problem.<br>Another obvious thing you can try is just using a different image so the<br>two MBRs don't conflict?<br><br>Cheers,<br></pre></blockquote></div></body></html>