Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1917821

Summary: Adding new host with reboot causes the host to end up non operational
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.InfraAssignee: Dana <delfassy>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Matyáš <pmatyas>
Severity: low Docs Contact:
Priority: medium    
Version: 4.4.5CC: bugs, gdeolive, mperina
Target Milestone: ovirt-4.4.5Flags: pm-rhel: ovirt-4.4+
gdeolive: testing_ack+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.5.5 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-18 15:14:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1853906    
Bug Blocks:    
Attachments:
Description Flags
engine log none

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.