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

Fix nm-cloud-setup to support IP configuration for secondary interfaces on Oracle VM from metadata

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • NetworkManager-1.53.4-1.el10
    • No
    • Moderate
    • ZStream
    • 1
    • rhel-net-mgmt
    • ssg_networking
    • 5
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • NMT SST - 2025Q1
    • Approved Blocker
    • Hide

      Definition of Done:

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

      The acceptance criteria defined below are met.

      Given a valid response from the OCI metadata service for a secondary VNIC,

      When nm-cloud-setup processes the metadata,

      Then the interface must be configured with the correct IP address, subnet, and routing as provided by OCI.

      Definition of Done:

      • The implementation meets the acceptance criteria
      • Integration tests are running and pass 
      • The code is part of a downstream build attached to an errata

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

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

      ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified.

      ( ) 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. Given a valid response from the OCI metadata service for a secondary VNIC, When nm-cloud-setup processes the metadata, Then the interface must be configured with the correct IP address, subnet, and routing as provided by OCI. Definition of Done: The implementation meets the acceptance criteria Integration tests are running and pass  The code is part of a downstream build attached to an errata ( ) Code changes are included in a downstream build attached to an errata. ( ) All required testing (manual and/or automated) passes successfully. ( ) All necessary backports to the related RHEL streams (linked as 'relates' in this issue) have been completed and verified. ( ) Related documentation updates (if applicable) have been completed.
    • Pass
    • Automated
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      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
              rh-ee-sfaye Stanislas Faye
              Network Management Team Network Management Team
              Vladimir Benes Vladimir Benes
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: