Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1885696[details]
reproducer.sh
Description of problem:
This is a partial regression of https://bugzilla.redhat.com/show_bug.cgi?id=1724465 , now on RHEL 9.1 it failed at the last step "nmstatectl set bond0_absent.yaml"
Version-Release number of selected component (if applicable):
nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64
DISTRO=RHEL-9.1.0-20220531.0
How reproducible:
Nearly 100%, I saw only one success so far
Steps to Reproduce:
. reproducer.sh
Actual results:
[2022-06-01T07:50:18Z ERROR nmstate::nm::nm_dbus::nm_api] org.freedesktop.NetworkManager.ConnectionNotActive: The connection was not active.
NmstateError: Bug: DbusConnectionError: org.freedesktop.NetworkManager.ConnectionNotActive: The connection was not active. dbus: Some(MethodError("org.freedesktop.NetworkManager.ConnectionNotActive", Some("The connection was not active."), Msg { type: Error, sender: ":1.40", reply-serial: 80, body: Signature: [
s (115),
] }))
Expected results:
bond0 is removed(including the NM connection)
veth0 and veth1 are deactivated, but the NM connections preserved
Additional info:
Upstream patch posed to https://github.com/nmstate/nmstate/pull/1956
I failed to reproduce the failure but noticed nmstate does not change the NM profile/connection for `state:down` interface.
Above patch make sure nmstate allows you to change the interface configure with `state:down`. For example:
```
---
interfaces:
- name: eth1
state: down
- name: eth2
state: down
ipv4:
enabled: true
dhcp: true
- name: bond99
type: bond
state: absent
```
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:7991