Bug 2103744
| Summary: | [ACM 2.5.1] Multi-node 4.11 spoke installation failing as hosts fail to reboot within timeout | ||
|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | epassaro |
| Component: | Infrastructure Operator | Assignee: | Igal Tsoiref <itsoiref> |
| Status: | CLOSED DUPLICATE | QA Contact: | Chad Crum <ccrum> |
| Severity: | unspecified | Docs Contact: | Derek <dcadzow> |
| Priority: | unspecified | ||
| Version: | rhacm-2.5.z | CC: | ccrum, epassaro, itsoiref, mfilanov, trwest, yfirst |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-07-06 15:05:02 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
epassaro
2022-07-04 16:59:49 UTC
Pending user action usually point to a wrong boot order. Is that the case here? if it's not, what happen after the host manage to boot? These are actually KVM virtual machines, and in the XML there is only one boot option, not sure if it can still be skipping the booting from the infraenv iso. BTW at the beginning I thought it was an issue similar to BZ2074483 and its duplicate BZ2093486. I've asked there (https://bugzilla.redhat.com/show_bug.cgi?id=2074483#c21) but I don't find any error in libvirt logs or in the boot logs of the VM. After booting the VM I can ssh to it and I can see that the agent service is running without errors. Something else I could check? When rebooting during installation the host should boot into the disk and not he discovery ISO. @itsoiref are you aware of any libvirt configuration that should be checked in this case? @epassaro can you please get events from the cluster? you should have a link in the agent cluster install. Logs from the service will help as well Boot order we use is "disk,cdrom" it allows to start with cdrom when disk is clean and to start from disk after we write rchos. Can you please show your dumpxml? actually it is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2100456#c3 *** This bug has been marked as a duplicate of bug 2100456 *** The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |