<html>
<head>
<base href="https://bugzilla.suse.com/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_IN_PROGRESS "
title="IN_PROGRESS - L3: sles12sp4 -> sles15sp1 upgrade of HLI in Azure results in non-bootable system"
href="https://bugzilla.suse.com/show_bug.cgi?id=1194320#c36">Comment # 36</a>
on <a class="bz_bug_link
bz_status_IN_PROGRESS "
title="IN_PROGRESS - L3: sles12sp4 -> sles15sp1 upgrade of HLI in Azure results in non-bootable system"
href="https://bugzilla.suse.com/show_bug.cgi?id=1194320">bug 1194320</a>
from <span class="vcard"><a class="email" href="mailto:jordan.causey@suse.com" title="Jordan Causey <jordan.causey@suse.com>"> <span class="fn">Jordan Causey</span></a>
</span></b>
<pre>(In reply to Martin Wilck from <a href="show_bug.cgi?id=1194320#c35">comment #35</a>)
<span class="quote">> I have never used --no-kernel. Indeed, the dm-multipath module is necessary
> for multpath support. I don't know what happens with required modules if the
> cusomer specifies --no-kernel.</span >
In this case, those dracut params are being set by some python scripts
implemented as part of the Distribution Migration System (DMS) RPMs. This is a
bit of a unique scenario, as DMS is typically only used for cloud-hosted VMs,
which would usually not implement multipath.
In this case, these are bare-metal servers that are managed by MSFT in Azure
datacenters. These hosts have their own dedicated on-site storage (NetApp),
hence the need for multipath support.
The dracut man describes the "--no-kernel" param as:
--no-kernel
do not install kernel drivers and firmware files
So that could definitely be the culprit here. Should be pretty easy to test
with a PTF, but this is not a change that would likely be beneficial to other
DMS customers moving forward.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>