Uploaded image for project: 'OpenStack Strategy'
  1. OpenStack Strategy
  2. RHOSSTRAT-660

os-net-config should resolve conflicts between ifcfg and NM connections

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Done
    • Icon: Critical Critical
    • rhos-18.0.14 FR 4
    • None
    • NFV
    • None
    • Not Selected
    • False
    • False
    • Hide

      None

      Show
      None
    • 0
    • 0
    • 0% To Do, 0% In Progress, 100% Done
    • rhos-connectivity-nfv
    • Feature
    • Hide
      .Cleanup of obsolete network configurations

      A NIC on a data plane node can be used for bare-metal provisioning and other initial configuration tasks. You can then use os-net-config to reconfigure the NIC for operational use in your deployment. In these cases, obsolete remnants of the initial configuration might cause IP address conflicts. To avoid such conflicts, you can use remove_config to clean up the obsolete configuration files from the initial configuration. For more information, see link:https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/planning_your_deployment/plan-networks_planning#plan-remove-config_plan-network[Cleaning up obsolete host network configurations].
      Show
      .Cleanup of obsolete network configurations A NIC on a data plane node can be used for bare-metal provisioning and other initial configuration tasks. You can then use os-net-config to reconfigure the NIC for operational use in your deployment. In these cases, obsolete remnants of the initial configuration might cause IP address conflicts. To avoid such conflicts, you can use remove_config to clean up the obsolete configuration files from the initial configuration. For more information, see link: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html/planning_your_deployment/plan-networks_planning#plan-remove-config_plan-network [Cleaning up obsolete host network configurations].
    • Done

      When a host is deployed using cloud-init there is a file created in /etc/sysconfig/network-scripts/ for network-scripts to handle. That can cause issues upon reboot if an interface has been configured with NetworkManager using nmcli or nmstate. If both network-scripts and NetworkManager are installed, and both have a configuration file in their respective places, then they will confict. os-net-config should remove any ifcfg files left by previous configuration tools once it uses the nmstate back-end to configure the network interface. This will prevent a collision.

      A similar situation can occur if an interface is configured in a NetworkManager connection and then os-net-config adds an ifcfg configuration with NM_CONTROLLED=no. This might be done by calling nmstate with "state: absent" in the YAML, or by calling nmcli to make the interface disabled/unmanaged (state: ignore), or by causing NetworkManager to immediately detect that there is a configuration in /etc/sysconfig/network-scripts that takes precedence and it should mark the interface disabled. This can be done by restarting the NetworkManager service or sending the "nmcli con reload" command.

      When os-net-config is adding a new ifcfg file with NM_CONTROLLED=no it should resolve these conflicts.

       

      Acceptance criteria:

      1) Handle any exception raised by ifcfg vs nmstate config without end user's intervention 

      2) Log the conflict but dont abort/stop deployment/config operations

      Doc imapct:

      No  Yes  (Haresh updated this answer 10/27/25 based on input from Karthik)

              vcandapp@redhat.com Vijayalakshmi Candappa
              rhel-process-autobot RHEL Jira bot
              Gurpreet Singh Gurpreet Singh
              Edu Alcaniz Edu Alcaniz
              rhos-dfg-nfv
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: