search

openshift / openshift-docs

OpenShift 3 and 4 product and community documentation
https://docs.openshift.com
Apache License 2.0
748 stars 1.74k forks source link

[enterprise-4.2] Edit suggested in file installing/installing_bare_metal/installing-bare-metal.adoc #18429

Closed kjw3 closed 3 years ago

kjw3 commented 4 years ago

Which section(s) is the issue in?

Creating Red Hat Enterprise Linux CoreOS (RHCOS) machines by PXE or iPXE booting https://docs.openshift.com/container-platform/4.2/installing/installing_bare_metal/installing-bare-metal.html#installation-user-infra-machines-pxe_installing-bare-metal

What needs fixing?

At a customer site on older Dell M610 Blades, we saw an issue where the pxe menu items for bootstrap, master and worker while creating the entry like the doc suggests (using HTTP urls for kernel and initramfs files), would cause the pxe menu to just reload itself and take no action.

We believe that instead, the kernel and initramfs files should be put directly on the tftp server. We believe the cause for the failure is that pxelinux.0 does not have drivers for some physical nics that cause the option inability to pull down the kernel and initramfs files over http.

The examples should be changed to have the user place those files directly on the tftp server and then use relative paths from the tftp boot in the pxe menu configs.

johnsimcall commented 4 years ago

The Dell M610 blades have Broadcom-based NICs.

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-docs/issues/18429#issuecomment-731902215): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.