<div dir="ltr">Chris,<div><br></div><div>Sorry to chime in late, but this might help you (or someone with a similar upgrade situation) in the future. The "<span style="color:rgb(0,0,0);font-family:monospace">rescan-scsi-bus.sh</span><span style="color:rgb(0,0,0);font-family:monospace">" script from the sg3-utils package can handle the update for the size increase without the reboot. Just need to run with the "-s" param to look for resized LUNs like the below (run from a CentOS7.3 server): </span></div><div><span style="color:rgb(0,0,0);font-family:monospace"><br></span></div><div><span style="color:rgb(0,0,0);font-family:monospace">```</span></div><div><span style="color:rgb(0,0,0);font-family:monospace"># rescan-scsi-bus.sh -s </span></div><span style="font-family:monospace">Scanning SCSI subsystem for new devices
<br><b>Searching for resized LUNs
</b><br>0 new or changed device(s) found. <br>0 remapped or resized device(s) found.
<br>0 device(s) removed. <br></span><div><span style="font-family:monospace">```</span></div><div><span style="font-family:monospace"><br></span></div><div><span style="font-family:monospace">Cheers</span></div><div><span style="font-family:monospace">Jeff</span></div><div><span style="font-family:monospace"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 24, 2017 at 9:20 AM, Chris Adams <span dir="ltr"><<a href="mailto:cma@cmadams.net" target="_blank">cma@cmadams.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did see that page, but... I can't get there from here. I can't get<br>
upgraded from 3.5 until I get past this problem, and on 3.5, the hosted<br>
engine storage domain isn't included in the normal UI at all.<br>
<br>
I think I did get this working though; both servers had kernel messages<br>
that they saw the LUN resize, but they didn't actually change the block<br>
device size to reflect that. After rebooting each server (separately),<br>
lsblk showed the new size on both, and a manual pvresize on both shows<br>
the increased VG size.<br>
<br>
On to testing 3.6 upgrade again!<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
Once upon a time, Adam Litke <<a href="mailto:alitke@redhat.com">alitke@redhat.com</a>> said:<br>
> Hi Chris. We added this feature to newer versions of oVirt (see the<br>
> feature page[1]). The easiest way to work around this problem might be to<br>
> add an additional LUN to this domain if you are able to do it. If not, it<br>
> looks like you would need to manually reconnect the host to the domain, to<br>
> a pvresize to the new size. I am not sure if any engine DB updates will<br>
> also be required. Nir and Fred worked on this feature and might be able to<br>
> assist you further.<br>
><br>
><br>
> [1]<br>
> <a href="https://www.ovirt.org/develop/release-management/features/storage/lun-resize/" rel="noreferrer" target="_blank">https://www.ovirt.org/develop/<wbr>release-management/features/<wbr>storage/lun-resize/</a><br>
><br>
> On Fri, Feb 24, 2017 at 9:00 AM, Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>> wrote:<br>
><br>
> > I'm testing upgrading an oVirt 3.5 setup, and I have run into a problem<br>
> > when going from 3.5 to 3.6 on a physical machine configured for the<br>
> > hosted engine. I upgraded the engine itself okay, but when I upgraded<br>
> > the first physical machine, it cannot be re-activated; it gets an error<br>
> > connecting to the storage domain.<br>
> ><br>
> > Checking the logs, it looks like it is looping trying to create a new LV<br>
> > in the HE VG. I assume this is for moving the HE config to the shared<br>
> > storage? It is failing because it is trying to create a 1G LV, but the<br>
> > VG only has 512M free space.<br>
> ><br>
> > I extended the iSCSI volume, but there doesn't appear to be anyway to<br>
> > get the HE nodes to recognize this; they both still see the original<br>
> > size, no matter what I try. Is there a way to get them to see the<br>
> > larger PV, so the new LV(s) can be created?<br>
> ><br>
> > --<br>
> > Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
> > ______________________________<wbr>_________________<br>
> > Users mailing list<br>
> > <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Adam Litke<br>
<br>
> ______________________________<wbr>_________________<br>
> Users mailing list<br>
> <a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
> <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br>
<br>
--<br>
Chris Adams <<a href="mailto:cma@cmadams.net">cma@cmadams.net</a>><br>
______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
</div></div></blockquote></div><br></div>