<div dir="ltr"><span><div class="gmail_signature"><div dir="ltr"><div><div>The inconsistency in device naming is documented in <a href="https://docs.openstack.org/nova/pike/user/block-device-mapping.html#intermezzo-problem-with-device-names">https://docs.openstack.org/nova/pike/user/block-device-mapping.html#intermezzo-problem-with-device-names</a>.</div><div><br></div><div>Similar to Tim's suggested approach, you can also mount the device by its UUID. A while back I wrote a small, relatively untested, Python script to which modifies fstab & replaces the device names with UUID=<device UUID> (see attached). It depends on Augeas (python-augeas) to modify fstab.</div><div><br></div><div>This script can be downloaded into the Instance using cloud-init, and then executed on initial boot with runcmd.<br></div><div><br></div><div dir="ltr"><div style="font-size:12.8px">—</div><div class="gmail_extra">Blake Covarrubias</div><div class="gmail_extra">Product Manager</div><div class="gmail_extra">Platform9 Systems, Inc<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 25, 2018 at 11:13 PM, Tim Bell <span dir="ltr"><<a href="mailto:Tim.Bell@cern.ch" target="_blank">Tim.Bell@cern.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_3696905136884347270WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Labels can be one approach where you mount by disk label rather than device</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Creating the volume with the label</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<pre style="background:rgb(247,247,247) none repeat scroll 0% 0%"><code><span style="font-family:Consolas;color:rgb(51,51,51);letter-spacing:0.15pt;border:1pt none windowtext;padding:0cm"># mkfs -t ext4 -L testvol /dev/vdb</span></code></pre>
<pre style="background:rgb(247,247,247) none repeat scroll 0% 0%"><span style="font-size:12pt;font-family:Consolas;color:rgb(51,51,51);letter-spacing:0.15pt"> </span></pre>
<p class="MsoNormal"><span lang="EN-GB">/etc/fstab then contains</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal" style="background:rgb(247,247,247) none repeat scroll 0% 0%"><span style="font-size:10pt;font-family:Consolas;color:rgb(51,51,51);letter-spacing:0.15pt;border:1pt none windowtext;padding:0cm">LABEL=testvol /mnt ext4 noatime,nodiratime,user_xattr <wbr> 0 0</span><span style="font-size:12pt;font-family:Consolas;color:rgb(51,51,51);letter-spacing:0.15pt"></span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">You still need to be careful to not attach data disks at install time though but it addresses booting order problems.</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<p class="MsoNormal"><span lang="EN-GB">Tim</span></p>
<p class="MsoNormal"><span lang="EN-GB"> </span></p>
<div style="border-color:rgb(181,196,223) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm">
<p class="MsoNormal" style="margin-left:36pt"><b><span style="font-size:12pt;color:black">From:
</span></b><span style="font-size:12pt;color:black">Jean-Philippe Méthot <<a href="mailto:jp.methot@planethoster.info" target="_blank">jp.methot@planethoster.info</a>><br>
<b>Date: </b>Friday, 26 January 2018 at 07:28<br>
<b>To: </b>"Logan V." <<a href="mailto:logan@protiumit.com" target="_blank">logan@protiumit.com</a>><br>
<b>Cc: </b>openstack-operators <<a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.<wbr>openstack.org</a>><br>
<b>Subject: </b>Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi</span></p>
</div><div><div class="gmail-h5">
<div>
<p class="MsoNormal" style="margin-left:36pt"> </p>
</div>
<p class="MsoNormal" style="margin-left:36pt"><a name="m_3696905136884347270__MailOriginalBody">Yea, the configdrive is a non-issue for us since we don’t use those. The multi-drive issue is the only one really affecting us. While removing the second drive and reattaching it after
boot is probably a good solution, I think it’s likely the issue will come back after a hard reboot or migration. Probably better to wait before I start converting my multi-disk instances to virtio-scsi. If I am not mistaken, this should also be an issue in
Pike and master, right? </a></p>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span> </span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black">Jean-Philippe Méthot</span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black">Openstack system administrator</span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black">Administrateur système Openstack</span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black">PlanetHoster inc.</span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black"> </span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><span style="font-size:9pt;font-family:Helvetica;color:black"> </span></span></p>
</div>
<p class="MsoNormal" style="margin-left:36pt"><span> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span><br>
<br>
</span></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<div>
<p class="MsoNormal" style="margin-left:36pt"><span>Le 26 janv. 2018 à 14:23, Logan V. <</span><a href="mailto:logan@protiumit.com" target="_blank"><span>logan@protiumit.com</span><span></span></a><span>>
a écrit :</span></p>
</div>
<p class="MsoNormal" style="margin-left:36pt"><span> </span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36pt"><span>There is a small patch in the bug which resolves the config drive<br>
ordering. Without that patch I don't know of any workaround. The<br>
config drive will always end up first in the boot order and the<br>
instance will always fail to boot in that situation.<br>
<br>
For the multi-volume instances where the boot volume is out of order,<br>
I don't know of any patch for that. One workaround is to detach any<br>
secondary data volumes from the instance, and then reattach them after<br>
booting from the one and only attached boot volume.<br>
<br>
Logan<br>
<br>
On Thu, Jan 25, 2018 at 10:21 PM, Jean-Philippe Méthot<br>
<</span><a href="mailto:jp.methot@planethoster.info" target="_blank"><span>jp.methot@planethoster.info</span><span></span></a><span>> wrote:<br>
<br>
</span></p>
<blockquote style="margin-top:5pt;margin-bottom:5pt">
<p class="MsoNormal" style="margin-right:0cm;margin-bottom:12pt;margin-left:36pt">
<span>Thank you, it indeed seems to be the same issue. I will be following this<br>
bug report. A shame too, because we were waiting for the patch to allow us<br>
to setup 2 drives on virtio-scsi before starting to make the change. In the<br>
meantime, have you found a way to circumvent the issue? Could it be as easy<br>
as changing the drive order in the database?<br>
<br>
<br>
Jean-Philippe Méthot<br>
Openstack system administrator<br>
Administrateur système Openstack<br>
PlanetHoster inc.<br>
<br>
<br>
<br>
<br>
Le 26 janv. 2018 à 13:06, Logan V. <</span><a href="mailto:logan@protiumit.com" target="_blank"><span>logan@protiumit.com</span><span></span></a><span>> a écrit
:<br>
<br>
</span><a href="https://bugs.launchpad.net/nova/+bug/1729584" target="_blank"><span>https://bugs.launchpad.net/<wbr>nova/+bug/1729584</span><span></span></a><span><br>
<br>
</span></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36pt"><span> </span></p>
</div>
</div></div></div>
</div>
<br>______________________________<wbr>_________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.<wbr>openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-operators</a><br>
<br></blockquote></div><br></div></div></div></div></div></span></div>