[ovirt-users] Re: [ANN] oVirt 4.3.6 is now generally available

Il giorno ven 27 set 2019 alle ore 16:44 Gianluca Cecchi < gianluca.cecchi(a)gmail.com&gt; ha scritto: > On Fri, Sep 27, 2019 at 12:42 PM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; > wrote: > > [snip > > >> >>> engine >>> 1) yum update to update OS >>> I think versionlock plugin of oVirt will prevent update of its core >>> parts, correct? >>> >> >> correct, version lock will prevent core oVirt packages to be updated. >> >> >> > [snip] > >> >>> 2) reboot >>> >>> 3) update oVirt >>> NOTE: probably non need d update setup packages, because put in in >>> previous update phase, correct? >>> >> >> correct, setup packages will be updated in previous loop, just run >> engine-setup here >> >> >>> >>> 4) eventually yum update again to see if any packages due to new repo >>> conf >>> >> >> shouldn't be needed but no harm in doing it. >> > In fact I didn't get anything > > >> >> >>> >>> 5) reboot of engine >>> >> >> engine will be already restarted by engine-setup. If there are no new >> updates at kernel level no need to reboot again. >> > just to replicate a future scenario of rebooting and see that previous > time all went up ok > > >> >> >>> >>> hosts >>> 6) put into maintenance >>> 7) simply yum update that will update CentOS packages + oVirt ones >>> (vdsm and such..) >>> >> >> Please use the engine to upgrade hosts, there's a command in webadmin >> interface for that. >> >> It's *a bit* outdated, but still valid: >> https://ovirt.org/documentation/upgrade-guide/upgrade-guide.html >> >> > > I tried and went well (at least for the first host) as a final result, > but the events inside web admin gui don't seem to be well coordinated... > > See below the sequence of events I got after selecting > Installation --> Upgrade (and checking the box to migrate running VMs) > > one vm running on it was correctly migrated and then the host put into > maintenance, but then it seems to me that the following update of vdsmd or > other subsysystems tried to got it up again. > In fact I saw in the gui the host coming up, then down, then non > operational (the X in the red square) > Then the host rebooted and came in up state again and I was able to > manually migrate a VM into it. > One other thing to improve in my opinion is that the upgrade of the host > from engine should inject the job that normally once a day checks if a host > has available updates: it seems somehow quirky that you pilot host upgrade > form engine and engine itself doesn't know that the host has been upgraded > (till tomorrow of course...) > +Laura Wright <lwright(a)redhat.com&gt; , +Martin Perina <mperina(a)redhat.com&gt; can you please look into this feedback? > > Thanks, > Gianluca > > > Host ov200 upgrade was started (User: user1@my_domain@my_domain). > 9/27/19 3:55:10 PM > Migration initiated by system (VM: hostcopy1, Source: ov200, Destination: > ov301, Reason: ). 9/27/19 3:55:11 PM > Host ov200 was switched to Maintenance Mode. 9/27/19 3:55:11 PM > Migration completed (VM: hostcopy1, Source: ov200, Destination: ov301, > Duration: 13 seconds, Total: 20 seconds, Actual downtime: 88ms) 9/27/19 > 3:55:31 PM > VDSM ov200 command ConnectStorageServerVDS failed: Connection timeout for > host 'ov200.my_domain', last response arrived 22501 ms ago. 9/27/19 3:57:03 > PM > Host ov200 is not responding. It will stay in Connecting state for a > grace period of 60 seconds and after that an attempt to fence the host will > be issued. 9/27/19 3:57:03 PM > .. > Host ov200 is non responsive. 9/27/19 3:57:09 PM > Executing power management status on Host ov200 using Proxy Host ov301 > and Fence Agent ipmilan:10.4.192.66. 9/27/19 3:57:09 PM > Soft fencing on host ov200 was successful. 9/27/19 3:57:19 PM > VDSM ov200 command ConnectStorageServerVDS failed: Connection timeout for > host 'ov200.my_domain', last response arrived 16876 ms ago. 9/27/19 3:59:03 > PM > Host ov200 is non responsive. 9/27/19 3:59:03 PM > Executing power management status on Host ov200 using Proxy Host ov301 > and Fence Agent ipmilan:10.4.192.66. 9/27/19 3:59:04 PM > No faulty multipath paths on host ov200 9/27/19 3:59:04 PM > Executing power management status on Host ov200 using Proxy Host ov301 > and Fence Agent ipmilan:10.4.192.66. 9/27/19 3:59:04 PM > Status of host ov200 was set to NonResponsive. 9/27/19 3:59:17 PM > .. > Host ov200 is not responding. It will stay in Connecting state for a > grace period of 60 seconds and after that an attempt to fence the host will > be issued. 9/27/19 4:00:24 PM > Soft fencing on host ov200 was successful. 9/27/19 4:00:38 PM > VDSM ov200 command ConnectStorageServerVDS failed: Connection timeout for > host 'ov200.my_domain', last response arrived 7121 ms ago. 9/27/19 4:00:56 > PM > .. > Host ov200 was restarted using SSH by the engine. 9/27/19 4:02:31 PM > Upgrade was successful and host ov200 will be rebooted. 9/27/194:02:31 PM > VDSM ov200 command ConnectStorageServerVDS failed: Connection timeout for > host 'ov200.my_domain', last response arrived 5341 ms ago. 9/27/19 4:02:46 > PM > Host ov200 cannot access the Storage Domain(s) <UNKNOWN> attached to the > Data Center MYDC. Setting Host state to Non-Operational. 9/27/19 4:02:46 PM > Failed to connect Host ov200 to Storage Pool MYDC 9/27/19 4:02:46 PM > ... > Executing power management status on Host ov200 using Proxy Host ov301 > and Fence Agent ipmilan:10.4.192.66. 9/27/19 4:12:27 PM > Status of host ov200 was set to Up. 9/27/19 4:12:27 PM > Host ov200 power management was verified successfully. 9/27/19 4:12:27 PM > > > > -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*