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

Bug 1868409

Summary: Failed to deploy HE with Host is not up, please check logs, perhaps also on the engine machine
Product: [oVirt] vdsm Reporter: Nikolai Sednev <nsednev>
Component: GeneralAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Nikolai Sednev <nsednev>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.40.24CC: bugs, mavital, michal.skrivanek, stirabos
Target Milestone: ovirt-4.4.2Keywords: Reopened, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: vdsm-4.40.25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-18 07:11:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
sosreport from alma04 none

Description Nikolai Sednev 2020-08-12 14:48:30 UTC
Created attachment 1711196 [details]
sosreport from alma04

Description of problem:
Failed to deploy HE with Host is not up, please check logs, perhaps also on the engine machine
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Host is not up, please check logs, perhaps also on the engine machine"}


Version-Release number of selected component (if applicable):
rhvm-appliance-4.4-20200722.0.el8ev.x86_64
ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch
ovirt-hosted-engine-setup-2.4.6-1.el8ev.noarch
Linux 4.18.0-193.14.3.el8_2.x86_64 #1 SMP Mon Jul 20 15:02:29 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.2 (Ootpa)


How reproducible:
100%

Steps to Reproduce:
1.Deploy HE.

Actual results:
Deployment fails.

Expected results:
Deployment should succeed.

Additional info:
Sosreport from alma04.

Comment 1 Michal Skrivanek 2020-08-13 03:23:04 UTC
...and did you check the logs?

Comment 2 Nikolai Sednev 2020-08-13 05:59:16 UTC
(In reply to Michal Skrivanek from comment #1)
> ...and did you check the logs?

I attached them to the bug. Please see the sosreport attached.

Comment 3 Nikolai Sednev 2020-08-13 06:06:00 UTC
See also https://bugzilla.redhat.com/show_bug.cgi?id=1816002, which made the latest changes to error being reported in case of host not being added to the engine properly.

Comment 4 Michal Skrivanek 2020-08-13 06:28:15 UTC
Nikolai, the message was added for a reason, it's for you to take a look at the logs to understand what's wrong with the deployment process. Attaching bunch of logs without saying anything about what you were doing doesn't really motivate anyone to take a look at such bug. It is more likely no. one will ever take a look at it

Either way, "DM multipath kernel driver not loaded", a temporary regression in vdsm-4.40.24 fixed by https://gerrit.ovirt.org/110672 in 4.40.25

Comment 5 Nikolai Sednev 2020-08-13 07:04:18 UTC
(In reply to Michal Skrivanek from comment #4)
> Nikolai, the message was added for a reason, it's for you to take a look at
> the logs to understand what's wrong with the deployment process. Attaching
> bunch of logs without saying anything about what you were doing doesn't
> really motivate anyone to take a look at such bug. It is more likely no. one
> will ever take a look at it
> 
> Either way, "DM multipath kernel driver not loaded", a temporary regression
> in vdsm-4.40.24 fixed by https://gerrit.ovirt.org/110672 in 4.40.25

Why did you closed the bug if I ran the deployment over vdsm-4.40.24-1.el8ev.x86_64, while it'll only fixed in vdsm-4.40.24, which is not yet available to QA.
Shouldn't this bug be set to ON-QA with fixed in version 4.40.24?

Comment 6 Nikolai Sednev 2020-08-13 07:11:24 UTC
BTW vdsm-4.40.24-1.el8ev.x86_64 is from Yestarday's clean HE installation from bob.
Today it already got changed to vdsm-4.40.25-1.el8ev.x86_64 and I didn't encountered with the previous issue.
I might be wrong, but I think that the bug should be moved to verified instead of closed current release.

Comment 7 Nikolai Sednev 2020-08-13 07:34:34 UTC
Original issue was not seen with latest vdsm-4.40.25-1.el8ev.x86_64. 
Moving to verified.

Comment 8 Sandro Bonazzola 2020-09-18 07:11:50 UTC
This bugzilla is included in oVirt 4.4.2 release, published on September 17th 2020.

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

Comment 9 Red Hat Bugzilla 2023-09-14 06:05:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days