Bug 1532709 - Host is set to non responsive after update when reboot takes a long time
Summary: Host is set to non responsive after update when reboot takes a long time
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.3
: ---
Assignee: Ondra Machacek
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-09 16:01 UTC by Petr Matyáš
Modified: 2018-05-10 06:32 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-10 06:32:44 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)
engine log (290.90 KB, text/plain)
2018-01-09 16:01 UTC, Petr Matyáš
no flags Details
engine log (502.38 KB, text/plain)
2018-01-17 11:58 UTC, Petr Matyáš
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86645 0 master MERGED core: honor ServerRebootTimeout during host reboot 2021-02-09 05:26:07 UTC
oVirt gerrit 89381 0 ovirt-engine-4.2 MERGED core: honor ServerRebootTimeout during host reboot 2021-02-09 05:26:07 UTC

Description Petr Matyáš 2018-01-09 16:01:45 UTC
Created attachment 1379182 [details]
engine log

Description of problem:
When updating a host through UI with reboot after update field selected, the host is set to non responsive because it's rebooting and thus really not responsive, the status should be set to either still updating (or similar) or rebooting.

Version-Release number of selected component (if applicable):
ovirt-engine-4.2.1-0.2.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. update a host and select reboot after update
2.
3.

Actual results:
host in non responsive status (when the reboot takes a bit longer, probably wont reproduce on virtual machines)

Expected results:
host in status rebooting/updating and then up

Additional info:

Comment 1 Martin Perina 2018-01-10 08:45:47 UTC
We need to honor ServerRebootTimeout also during host reboot after successful upgrade

Comment 2 Ondra Machacek 2018-01-17 09:37:07 UTC
We do:

2018-01-09 17:43:42,243+02 INFO  [org.ovirt.engine.core.bll.SshHostRebootCommand] (EE-ManagedThreadFactory-engine-Thread-5785) [32a39b62] Waiting 300 seconds, for server to finish reboot process.

Petr, please try to update 'ServerRebootTimeout' config value.

Comment 3 Petr Matyáš 2018-01-17 11:58:27 UTC
Created attachment 1382371 [details]
engine log

In this reproduction the host didn't go to non responsive, however the host was set to "Up" right after the upgrade was finished (before reboot).
Like the check for status was executed before the host could be shut down.

Comment 4 Yaniv Kaul 2018-03-15 14:02:58 UTC
Is this on track to 4.2.2? If not, please defer to 4.2.3.

Comment 5 Pavol Brilla 2018-04-19 14:16:10 UTC
Installed Packages
ovirt-engine.noarch                             4.2.3.2-0.1.el7

Host behave correctly during upgrade

Comment 6 Sandro Bonazzola 2018-05-10 06:32:44 UTC
This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.