Bug 1817402
Summary: | Host up timeout during deploying hosted engine via cockpit. | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-ansible-collection | Reporter: | Wei Wang <weiwang> | ||||||
Component: | hosted-engine-setup | Assignee: | Yedidyah Bar David <didi> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wei Wang <weiwang> | ||||||
Severity: | urgent | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | unspecified | CC: | bugs, cshao, didi, eslutsky, lsvaty, mavital, michal.skrivanek, mperina, peyu, qiyuan, sbonazzo, shlei, weiwang, yaniwang, yturgema | ||||||
Target Milestone: | ovirt-4.4.0 | Keywords: | TestBlocker | ||||||
Target Release: | 1.1.2 | Flags: | sbonazzo:
ovirt-4.4?
sbonazzo: planning_ack? sbonazzo: devel_ack+ weiwang: testing_ack+ |
||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | ovirt-ansible-hosted-engine-setup-1.1.2 | Doc Type: | No Doc Update | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-05-20 20:01:02 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
Wei Wang
2020-03-26 09:56:35 UTC
Created attachment 1673739 [details]
var log files
Created attachment 1673740 [details]
picture
(In reply to Martin Perina from comment #3) > Isn't it duplicate of BZ1814940? Yes, since the BZ1814940 record another bug in comment #3, so report the host up timeout bug in a new report file. BZ1814940 is only for comment #3 now. Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1814940#c11 Current bug is only on hosted-engine side, and only for making it wait longer for the host to become up. @Didi increasing timeout does not seem like the right solution. The problem was that rdma service was not enabled, and boot time was expanded by a lot. We already have WA, and waiting for gluster/rhel fixed. IMHO this timeout should not be accepted, WDYT? (In reply to Lukas Svaty from comment #6) > @Didi increasing timeout does not seem like the right solution. > > The problem was that rdma service was not enabled, and boot time was > expanded by a lot. > We already have WA, and waiting for gluster/rhel fixed. Not sure what you mean. We already saw several ansible-host-deploy logs that took, from first to last line (all ansible code, no reboots or anything) more than 10 minutes. > > IMHO this timeout should not be accepted, WDYT? If you mean to say: 10 minutes should be enough, we should make our ansible code not take more than 10 minutes, then I agree with you, and mperina tells me we are working on it. Current bug is a workaround, yes, for the time being (and I have no problem keeping it also later, for slow setups or whatever). (In reply to Yedidyah Bar David from comment #7) > I have no problem keeping it also later, for slow setups or whatever). TBH I would go even higher. While the RHV host should be generally up to date you can easily be installing an outdated version and then have plenty of packages to be updated, slow machines, etc. I would personally use 30 minutes Test with rhvh-4.4.0.16-0.20200401.0 and rhvm-appliance-4.4-20200403.0.el8ev.x86_64, hosted engine deploy successful, the bug is fixed. QE will move the status to "VERIFIED" until dev move the status to "ON_QA" This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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. |