<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-GB">Labels can be one approach where you mount by disk label rather than device<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Creating the volume with the label<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<pre style="background:#F7F7F7"><code><span style="font-family:Consolas;color:#333333;letter-spacing:.15pt;border:none windowtext 1.0pt;padding:0cm"># mkfs -t ext4 -L testvol /dev/vdb<o:p></o:p></span></code></pre>
<pre style="background:#F7F7F7"><span style="font-size:12.0pt;font-family:Consolas;color:#333333;letter-spacing:.15pt"><o:p> </o:p></span></pre>
<p class="MsoNormal"><span lang="EN-GB">/etc/fstab then contains<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:#F7F7F7"><span style="font-size:10.0pt;font-family:Consolas;color:#333333;letter-spacing:.15pt;border:none windowtext 1.0pt;padding:0cm">LABEL=testvol /mnt ext4 noatime,nodiratime,user_xattr 0 0</span><span style="font-size:12.0pt;font-family:Consolas;color:#333333;letter-spacing:.15pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></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.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:36.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Jean-Philippe Méthot <jp.methot@planethoster.info><br>
<b>Date: </b>Friday, 26 January 2018 at 07:28<br>
<b>To: </b>"Logan V." <logan@protiumit.com><br>
<b>Cc: </b>openstack-operators <openstack-operators@lists.openstack.org><br>
<b>Subject: </b>Re: [Openstack-operators] Inverted drive letters on block devices that use virtio-scsi<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><a name="_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? <o:p></o:p></a></p>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black">Jean-Philippe Méthot<o:p></o:p></span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black">Openstack system administrator<o:p></o:p></span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black">Administrateur système Openstack<o:p></o:p></span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black">PlanetHoster inc.<o:p></o:p></span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p> </o:p></span></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><span style="font-size:9.0pt;font-family:Helvetica;color:black"><o:p> </o:p></span></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">Le 26 janv. 2018 à 14:23, Logan V. <</span><a href="mailto:logan@protiumit.com"><span style="mso-bookmark:_MailOriginalBody">logan@protiumit.com</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">>
a écrit :<o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody">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"><span style="mso-bookmark:_MailOriginalBody">jp.methot@planethoster.info</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">> wrote:<br>
<br>
<o:p></o:p></span></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:0cm;margin-right:0cm;margin-bottom:12.0pt;margin-left:36.0pt">
<span style="mso-bookmark:_MailOriginalBody">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"><span style="mso-bookmark:_MailOriginalBody">logan@protiumit.com</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody">> a écrit
:<br>
<br>
</span><a href="https://bugs.launchpad.net/nova/+bug/1729584"><span style="mso-bookmark:_MailOriginalBody">https://bugs.launchpad.net/nova/+bug/1729584</span><span style="mso-bookmark:_MailOriginalBody"></span></a><span style="mso-bookmark:_MailOriginalBody"><br>
<br>
<o:p></o:p></span></p>
</blockquote>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="margin-left:36.0pt"><span style="mso-bookmark:_MailOriginalBody"><o:p> </o:p></span></p>
</div>
</div>
</body>
</html>