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

Cannot deploy OCP 4.18 with NIC cable disconnected

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

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • rhel-9.6.z
    • nmstate
    • None
    • No
    • None
    • rhel-net-mgmt
    • None
    • False
    • 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.

      Given an OpenShift 4.18+ installer using nmstate.service on a baremetal node and a NIC is physically disconnected (no carrier) during installation,

      When the system administrator provides a NodeNetworkConfigurationPolicy with state: up and the YAML disables nmstate verification,

      Then the installer completes without rollback due to missing carrier and the NIC remains configured as declared in YAML

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. Given an OpenShift 4.18+ installer using nmstate.service on a baremetal node and a NIC is physically disconnected (no carrier) during installation, When the system administrator provides a NodeNetworkConfigurationPolicy with state: up and the YAML disables nmstate verification, Then the installer completes without rollback due to missing carrier and the NIC remains configured as declared in YAML ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      When installing OpenShift node with nmstate YAML containing `state: up` for network installer which cable is disconnected, the installer will fail with error:

      
VerificationError: Verification failure: ens1f2.interface.state desire '"up"', current '"down"'

      What is the impact of this issue to you?

      As Telco user, I want to install a OpenShift node before connecting cables as pre-deploy action. OCP 4.18 switched to `nmstate.service` from `nmstatectl gc` mode, this cause this use case not working anymore.

      Please provide the package NVR for which the bug is seen:

      nmstate 2.2.39

      How reproducible is this bug?:

      100%

      Steps to reproduce

      # Deploy a OpenShift single node on a baremetal server with nmstate state 
# marking `state:up` for cable disconnected NIC.

      Expected results

      Installer should ignore the carrier and move on the installation.

      Actual results

      The whole network configure been rollback causing the installation been terminated.

              nm-team Network Management Team
              fge@redhat.com Gris Ge
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: