Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-84695

Fix nm-cloud-setup to support IP configuration for secondary interfaces on Oracle VM from metadata [rhel-9.6.z]

XMLWordPrintable

    • NetworkManager-1.52.0-3.el9_6
    • No
    • Moderate
    • 0day
    • rhel-sst-network-management
    • ssg_networking
    • 1
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      None

      ( ) Code changes are included in a downstream build attached to an errata.

      ( ) All required testing (manual and/or automated) passes successfully.

      ( ) Related documentation updates (if applicable) have been completed.

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. None ( ) Code changes are included in a downstream build attached to an errata. ( ) All required testing (manual and/or automated) passes successfully. ( ) Related documentation updates (if applicable) have been completed.
    • Pass
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      This is a clone of issue RHEL-83198 to use for version rhel-9.6.z
      –
      Original description:
      Following a discussion with Oracle regarding our VLAN support implementation for secondary VNICs in nm-cloud-setup, we discovered an issue in how IP addresses are obtained for secondary interfaces in OCI virtual machines.
      Oracle Cloud Infrastructure (OCI) does not support DHCP for secondary VNICs - only the primary VNIC receives an IP via DHCP.
      IP information for secondary interfaces must be retrieved from the OCI metadata service via:

      curl -H "Authorization: Bearer Oracle" -L http://169.254.169.254/opc/v2/vnics/

      Currently, nm-cloud-setup expects an existing connection on the interface before configuring it. This is problematic, as in OCI the secondary VNICs may not have pre-existing connections and the tool refuses to proceed even after retrieving data from the metadata server.

              rhn-engineering-vbenes Vladimir Benes
              watson-automation Watson Automation
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: