Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-4220

Allow custom network interface names on IPI cluster installation

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • openshift-4.10, openshift-4.12
    • Node
    • False
    • None
    • False
    • Not Selected
    • x86_64
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request
      Allow custom network interface names on IPI cluster installation

      2. What is the nature and description of the request?
      Customer is trying hard to find a way that can help them rename interface name on a IPI installation. They were following this [Kbase|https://access.redhat.com/solutions/5222981] but since this sin't working for them the ign weren't getting used. Below is the reply from them.

      This was proposed earlier in this ticket but didn't work for IPI-based installations.
      While ignition files can be generated and modified, only the modifications of the bootstrapper VM are kept, and changes to master.ign and worker.ign are apparently ignored.
      But if you or someone from RH can get this to work with IPI: that would be great and solve the issue!" 

      3. Why does the customer need this? (List the business requirements here)
      Customer is expected to deliver the cluster by September end. They need to have two clusters & hence this will simplify their deployments.

      4. List any affected packages or components.
      RHCOS, NetworkManager, NMState

      Attachments

        Activity

          People

            ddharwar@redhat.com Deepthi Dharwar
            rhn-support-adubey Akash Dubey
            Mat Kowalski
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: