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

Fix testing Failures due to connection.autoconnect-ports Unknown Property

    • rhel-system-roles-1.78.1-0.1.el9
    • None
    • None
    • 4
    • rhel-sst-system-roles
    • 2
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • System Roles Sprint 1, System Roles Sprint 2, System Roles Sprint 3, System Roles Sprint 4
    • Hide

      Given that the network role's CI environment is operational and accessible,
      When running the tests_team_plugin_installation_nm.yml and tests_wireless_plugin_installation_nm.yml tests,
      Then the tests should not encounter failures related to the unknown property connection.autoconnect-ports and should pass without errors or exceptions.

      Definition of Done:

      • The implementation meets the acceptance criteria
      Show
      Given that the network role's CI environment is operational and accessible, When running the tests_team_plugin_installation_nm.yml and tests_wireless_plugin_installation_nm.yml tests, Then the tests should not encounter failures related to the unknown property connection.autoconnect-ports and should pass without errors or exceptions. Definition of Done: The implementation meets the acceptance criteria
    • Pass
    • None
    • Bug Fix
    • Hide
      .No property conflicts between the `NetworkManager` service and the `NetworkManager` plugin

      Previously, the `network` RHEL system role did not request user consent to restart the `NetworkManager` service when updates were available to networking packages, particularly, due to wireless interface changes. Consequently, this led to potential conflicts between the `NetworkManager` service and the `NetworkManager` plugin. Alternatively, the `NetworkManager` plugin was failing to run correctly. The problem has been fixed by making the `network` RHEL system role ask user for their consent to restart the `NetworkManager` service. As a result, there are no property conflicts between the `NetworkManager` service and the `NetworkManager` plugin in the described scenario.
      Show
      .No property conflicts between the `NetworkManager` service and the `NetworkManager` plugin Previously, the `network` RHEL system role did not request user consent to restart the `NetworkManager` service when updates were available to networking packages, particularly, due to wireless interface changes. Consequently, this led to potential conflicts between the `NetworkManager` service and the `NetworkManager` plugin. Alternatively, the `NetworkManager` plugin was failing to run correctly. The problem has been fixed by making the `network` RHEL system role ask user for their consent to restart the `NetworkManager` service. As a result, there are no property conflicts between the `NetworkManager` service and the `NetworkManager` plugin in the described scenario.
    • Done
    • None

      The network role's CI testing is encountering failures with the error message {{error: }}
      ``
      adding connection failed: failure to add connection: nm-connection-error-quark: connection.autoconnect-ports: unknown property (7).
      ``

      These failures occur specifically in the `tests_team_plugin_installation_nm.yml` and `tests_wireless_plugin_installation_nm.yml` tests.

      The issue has been identified and is currently being addressed in pull request #675.

              rmeggins@redhat.com Richard Megginson
              rh-ee-sfaye Stanislas Faye
              Wen Liang Wen Liang
              David Jez David Jez
              Jaroslav Klech Jaroslav Klech
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: