Bug 2036840 - Dell iDRAC PXE boot set on IPv6 address on IPv4 provisioning cluster
Summary: Dell iDRAC PXE boot set on IPv6 address on IPv4 provisioning cluster
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.9
Hardware: Unspecified
OS: Other
medium
urgent
Target Milestone: ---
: ---
Assignee: Latha S
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-04 07:34 UTC by Rei
Modified: 2023-03-09 01:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-09 01:10:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
iDRAC capture (84.97 KB, image/png)
2022-01-04 07:37 UTC, Rei
no flags Details

Description Rei 2022-01-04 07:34:44 UTC
Description of problem:
The PXE boot set on IPv6 address while the bootstrap use IPv4 for provisioning

Version-Release number of selected component (if applicable):
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.9.0-0.nightly-2021-12-23-045233   True        False         22m     Cluster version is 4.9.0-0.nightly-2021-12-23-045233


How reproducible:
Deploy on Dell hardware, this is the install-config (edited)
[root@ ~]# cat install-config.yaml
apiVersion: v1
baseDomain: <domain>
networking:
  networkType: OVNKubernetes
  machineCIDR: <ipv4>
metadata:
  name: <name>
compute:
- name: worker
  replicas: 2
controlPlane:
  name: master
  replicas: 3
  platform:
    baremetal: {}
platform:
  baremetal:
    provisioningNetwork: Managed
    provisioningNetworkInterface: eno1np0
    provisioningNetworkCIDR: <ipv4>
    bootstrapOSImage: http://registry.domain:8080/images/rhcos-49.84.202110081407-0-qemu.x86_64.qcow2.gz?sha256=88af7c3968a936edb96d759caef2e43473bb9f0bc3f37e89176f4f9d2ba91df5
    clusterOSImage: http://registry.domain.com:8080/images/rhcos-49.84.202110081407-0-openstack.x86_64.qcow2.gz?sha256=bbbb9243f084fc330a2c95e0bf33708d68e17628f48086eac574dcb96d35df9e
    apiVIP: <ipv4>
    ingressVIP: <ipv4>
    hosts:
      - name: openshift-master-0
        role: master
        bmc:
          address: redfish://<idrac>:443/redfish/v1/Systems/System.Embedded.1
          disableCertificateVerification: True
          username: <user>
          password: <pass>
        bootMACAddress: <mac>
        rootDeviceHints:
          deviceName: /dev/sda
      - name: openshift-master-1
        role: master
        bmc:
          address: redfish://<idrac>:443/redfish/v1/Systems/System.Embedded.1
          disableCertificateVerification: True
          username: <user>
          password: <pass>
        bootMACAddress: <mac>
        rootDeviceHints:
          deviceName: /dev/sda
      - name: openshift-master-2
        role: master
        bmc:
          address: redfish://<idrac>:443/redfish/v1/Systems/System.Embedded.1
          disableCertificateVerification: True
          username: <user>
          password: <pass>
        bootMACAddress: <mac>bootMACAddress: BC:97:E1:29:A8:00
        rootDeviceHints:
          deviceName: /dev/sda
      - name: openshift-worker-0
        role: worker
        bmc:
          address: redfish://<idrac>:443/redfish/v1/Systems/System.Embedded.1
          disableCertificateVerification: True
          username: <user>
          password: <pass>
        bootMACAddress: <mac>
        rootDeviceHints:
          deviceName: /dev/sda
      - name: openshift-worker-1
        role: worker
        bmc:
          address: redfish://<idrac>:443/redfish/v1/Systems/System.Embedded.1
          disableCertificateVerification: True
          username: <user>
          password: <pass>
        bootMACAddress: <mac>
        rootDeviceHints:
          deviceName: /dev/sda
additionalTrustBundle: |
  <certs>

pullSecret: |
  { "auths": { "registry.domain:5000": { "auth": <private>" } }}
fips: false
sshKey: |
  ssh-rsa <private>
- mirrors:
  - registry.domain:5000/localimages/local-release-image
  source: quay.io/openshift-release-dev/ocp-v4.0-art-dev
- mirrors:
  - registry.domain:5000/localimages/local-release-image
  source: registry.ci.openshift.org/ocp/release


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
Should set PXE on IPv4

Additional info:

Comment 1 Rei 2022-01-04 07:37:32 UTC
Created attachment 1848783 [details]
iDRAC capture

Comment 2 Riccardo Pittau 2022-01-04 17:21:36 UTC
hi, can you please provide more information? Would be greatly helpful to have some how to reproduce steps for example.
Also be aware that that particular setting is manually configured by the user, not by the installer.

Comment 3 Rei 2022-01-06 05:52:15 UTC
@rpittau Can you please advise what setting done automatically and what should be manually.
I'm focus on PXE devices. In my case the IPv4 device set disable in the boot order. Are the boot order set automatically? PXE IP version  automatically?
The reproduce steps is to deploy the BM on Dell platform (Should you need the iDRAC firmware version?) with IPv4 in Provision network and Baremetal network
The PXE device should be
2 devices and both on IPv6 
1 device on  IPv6 and the other on IPv4 and the IPv4 device set disable in the boot order

Comment 4 Riccardo Pittau 2022-01-06 08:45:16 UTC
@rhalle I'm not sure I understand the expectations of this particular deployment.
My understanding is that everything should be on IPv4, at least this is what it says in the Expected Results in the description.
The screenshot you posted is of a setting that is not managed by the installer but manually configured by the user prior to begin the installation (on PXE device settings -> Protocol)

Comment 5 Rei 2022-01-06 10:18:46 UTC
@rpittau Yes, this is the problem. What should be done manually and what should be done automatically?
PXE IP version can be done manually but boot order must be done automatically

Comment 6 Dmitry Tantsur 2022-01-17 10:31:36 UTC
When PXE booting, the device should (and most do) try all IP families (assuming you're in UEFI mode). Limiting it to one address family seems to be a Dell-specific feature that we don't have any real exposure to. I'll ask Dell people about it, but so far the best I can offer is to open a documentation bug for the users to double-check that they don't have this setting set or set incorrectly.

Comment 10 Shiftzilla 2023-03-09 01:10:33 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9062


Note You need to log in before you can comment on or make changes to this bug.