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

nmstate fails in systems with NetworkManager-wait-online timeout

Linking RHIVOS CVEs to...Migration: Automation ...Sync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhel-10.2
    • rhel-9.6
    • nmstate
    • nmstate-2.2.52-1.el10
    • Yes
    • Critical
    • ZStream
    • rhel-net-mgmt
    • Bug Fix
    • Hide
      `NetworkManager-wait-online.service` is no longer a hard requirement in `nmstate.service`::

      Before this update, the `nmstate.service` systemd unit had a strict `Requires` dependency on the `NetworkManager-wait-online.service` unit. Consequently, in environments where `NetworkManager-wait-online` failed or timed out, the `nmstate` state service failed to start and Nmstate could not apply the necessary network configurations. This update replaces `Requires` in the unit with `Wants`. As a result, the `nmstate` service starts regardless of the status of `NetworkManager-wait-online`, and Nmstate can apply network configurations.
      Show
      `NetworkManager-wait-online.service` is no longer a hard requirement in `nmstate.service`:: Before this update, the `nmstate.service` systemd unit had a strict `Requires` dependency on the `NetworkManager-wait-online.service` unit. Consequently, in environments where `NetworkManager-wait-online` failed or timed out, the `nmstate` state service failed to start and Nmstate could not apply the necessary network configurations. This update replaces `Requires` in the unit with `Wants`. As a result, the `nmstate` service starts regardless of the status of `NetworkManager-wait-online`, and Nmstate can apply network configurations.
    • Done
    • Done
    • Done
    • Not Required
    • None

      nmstate.service has been recently shipped with `Requires=` dependency on NetworkManager-wait-online. This fails in various OpenShift deployments as the latter very often fails in baremetal deployments.

      As a result, we get systems with nmstate.service failing and as a result, static network configuration may not be applied on those.

      This is also kinda circular dependency in case we need nmstate.service to apply a configuration that is needed for the network to be fully functional.

      Ultimately, we'd recommend that nmstate.service only wants but not requires NetworkManager-wait-online.

      This is a regression introduced in v2.2.48 and fixed in 2.2.52
      https://github.com/nmstate/nmstate/releases/tag/v2.2.48
      https://github.com/nmstate/nmstate/releases/tag/v2.2.52

              nm-team Network Management Team
              mkowalsk@redhat.com Mat Kowalski
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Marc Muehlfeld Marc Muehlfeld
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: