Bug 1917821 - Adding new host with reboot causes the host to end up non operational
Summary: Adding new host with reboot causes the host to end up non operational
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Infra
Version: 4.4.5
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ovirt-4.4.5
: ---
Assignee: Dana
QA Contact: Petr Matyáš
URL:
Whiteboard:
Depends On: 1853906
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-19 13:09 UTC by Petr Matyáš
Modified: 2021-03-18 15:14 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.4.5.5
Clone Of:
Environment:
Last Closed: 2021-03-18 15:14:16 UTC
oVirt Team: Infra
Embargoed:
pm-rhel: ovirt-4.4+
gdeolive: testing_ack+


Attachments (Terms of Use)
engine log (1.36 MB, text/plain)
2021-01-19 13:09 UTC, Petr Matyáš
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 113388 0 master MERGED core: Host deploy flow need to wait until host reboot finishes 2021-02-15 14:08:24 UTC

Description Petr Matyáš 2021-01-19 13:09:11 UTC
Created attachment 1748712 [details]
engine log

Description of problem:
When adding a new host with reboot action the host ends up in Non Operational state because it is rebooted and immediately (ok 30s after) checks for SDs availability which obviously fails as the host is rebooting.
Other issue might be that the host is never moved to state Rebooting which might be also the case for reinstall.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.5-0.11.el8ev.noarch

How reproducible:
always

Steps to Reproduce:
1. add a host with reboot action
2.
3.

Actual results:
host checks for SDs availability immediately after reboot

Expected results:
host moves to rebooting and only then it checks availability of SDs

Additional info:
After some time the host might be reported as up.

Comment 1 Petr Matyáš 2021-02-15 16:26:37 UTC
Verified on ovirt-engine-4.4.5.5-0.13.el8ev.noarch

Comment 2 Sandro Bonazzola 2021-03-18 15:14:16 UTC
This bugzilla is included in oVirt 4.4.5 release, published on March 18th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.5 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.