Version: 4.8.0-0.nightly-2021-05-13-002125 used hardware Dell PowerEdge R640 Bios version 1.6.13 idrac version: 4.40.10.00 iDRAC 9 Scenario: scaling a worker in remote subnet. Observation: loading the boot image takes a long time (7 minutes) and it appears as the boot is stuck. The image is attached. Bad user experience.
Created attachment 1783261 [details] This is what the user gets for that long period of time during boot.
same is expected with SNO
when we say "remote" it's when we have some latency, let's check the latency to the "remote setup" ? also, I would like to know how does that impact SNO deployment. ( I think most customer real-life scenario could be considered remote )
Does the boot succeed eventually (despite taking a long time), or is it completely stuck?
I assume you're using virtual media? Do you have other hardware vendors/models to try?
The boot succeeds after 7 minutes. Want to assure users don't reboot, assuming it's stuck. Using virtual media.
1. Boot msgs are something that is controlled by the HW vendor not something we have control over. 2. Try downgrading firmware to that is listed as supported in OpenShift documentation.[https://docs.openshift.com/container-platform/4.7/installing/installing_bare_metal_ipi/ipi-install-prerequisites.html#ipi-install-firmware-requirements-for-installing-with-virtual-media_ipi-install-prerequisites] 3. Needs documentation update to say that boot times can be expected to be long without indication of progress.
Made the changes in the following PR: https://github.com/openshift/openshift-docs/pull/35750
Made the changes in the following PR: https://bugzilla.redhat.com/show_bug.cgi?id=1960696
Verified - The warning was added with a needed message. https://github.com/openshift/openshift-docs/pull/35794#issuecomment-905664647
I had some discussion with a UK colleague and he suggested more explicit feedback. I have staged, but not committed the following text: Boot times can take up to 10 minutes without any indication of progress. Do not assume the boot is stuck, or abort or reboot during this installation, as this could require troubleshooting on the next installation. The current wording is at https://deploy-preview-37233--osdocs.netlify.app/openshift-enterprise/latest/installing/installing_bare_metal_ipi/ipi-install-prerequisites?utm_source=github&utm_campaign=bot_dp#ipi-install-firmware-requirements-for-installing-with-virtual-media_ipi-install-prerequisites @ale
@(In reply to Tony Mulqueen from comment #19) > I had some discussion with a UK colleague and he suggested more explicit > feedback. > I have staged, but not committed the following text: > > Boot times can take up to 10 minutes without any indication of progress. Do > not assume the boot is stuck, or abort or reboot during this installation, > as this could require troubleshooting on the next installation. > > The current wording is at > https://deploy-preview-37233--osdocs.netlify.app/openshift-enterprise/latest/ > installing/installing_bare_metal_ipi/ipi-install- > prerequisites?utm_source=github&utm_campaign=bot_dp#ipi-install-firmware- > requirements-for-installing-with-virtual-media_ipi-install-prerequisites > @ale The new wording is better IMHO. This way the deploying person(s) won't way for hours/days to start debugging. Thanks!
Can you provide link to the new PR?
@Polina: here is the link to the PR: https://github.com/openshift/openshift-docs/pull/37233 Sheldon moved this back to ON_QA because we made some further changes after VERIFIED was approved by QE. The changes were done to approve the text, as agreed by Alexander, but we need them once more VERIFIED. If the changes meet with your approval please move back to VERIFIED and I will issue a merge request.
I'm moving back to VERIFIED. I checked the changes.
Received notice of merge: Michael Burke <notifications> 2:45 PM (42 minutes ago) to State, openshift/openshift-docs, me Merged #35583 into enterprise-4.6.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days