Loading...

XML

Word

Printable

Acceptance Criteria:

Hide

Given a OCP cluster 4.12 or later version with nmstate operator with br-ex holding DNS configurations

When customer using nmstate operator to change DNS settings using desire state which only contain DNS configuration with `br-ex` marked as ignored.

Then NetworkManger will invoke dispatcher script of OCP `30-resolv-prepender` to setup the expected `/etc/resolv.conf`.

Given a OCP cluster 4.12 or later version with nmstate operator installed.

When customer using nmstate operator to create 50+ VLANs without DNS changes.

Then the `30-resolv-prepender` will not change content of `/etc/resolv.conf`.

Show
Given a OCP cluster 4.12 or later version with nmstate operator with br-ex holding DNS configurations When customer using nmstate operator to change DNS settings using desire state which only contain DNS configuration with `br-ex` marked as ignored. Then NetworkManger will invoke dispatcher script of OCP `30-resolv-prepender` to setup the expected `/etc/resolv.conf`. Given a OCP cluster 4.12 or later version with nmstate operator installed. When customer using nmstate operator to create 50+ VLANs without DNS changes. Then the `30-resolv-prepender` will not change content of `/etc/resolv.conf`.
Preliminary Testing:
None
Test Link:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/1548
Errata Link:
https://errata.devel.redhat.com/advisory/120156
Test Coverage:
None

The `30-resolv-prepender` NetworkManager dispatcher script of openshift
has been invoked even there is no DNS changes at all.

Introducing new NetworkManager dispatch event/action could eliminate the unneeded invoke of `30-resolv-prepender`

causes

OPNET-355 Resolv-prepender should support new "dns-changed" NM event

is cloned by

RHEL-10195 Better dispatch way for DNS changes [RHEL 8]

links to

RHBA-2023:120156 NetworkManager bug fix and enhancement update

mentioned on

Merge request - Update to 1.45.4 release (development)