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 1920093[details]
NM_trace.log
Description of problem:
When vlan over bond and bond itself both attahced to a vrf, cannot remove vrf and bond directly.
Version-Release number of selected component (if applicable):
nmstate-2.2.0-0.alpha.20221014.el9.x86_64
NetworkManager-1.40.0-1.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
echo "interfaces:
- name: bond0
state: up
type: bond
link-aggregation:
mode: 802.3ad
- name: bond0.4000
type: vlan
state: up
vlan:
base-iface: bond0
id: 4000
- name: vrf0
state: up
type: vrf
vrf:
route-table-id: 100
port:
- bond0
- bond0.4000
" | nmstatectl apply
echo "interfaces:
- name: bond0
type: bond
state: absent
- name: vrf0
type: vrf
state: absent" | nmstatectl apply
# Got error while all interfaces were removed, but NM connection of bond0.4000 remained
ip link show
nmcli con
Actual results:
NmstateError: Bug: DbusConnectionError: org.freedesktop.NetworkManager.DependencyFailed: parent device '4339ad3a-0c1e-45da-9b9c-55d12a9ef786' not found
Expected results:
No error, bond0, vrf0 and bond0.4000 with their NM connections are all removed
Additional info:
This wokrs in nmstate python version
Created attachment 1920093 [details] NM_trace.log Description of problem: When vlan over bond and bond itself both attahced to a vrf, cannot remove vrf and bond directly. Version-Release number of selected component (if applicable): nmstate-2.2.0-0.alpha.20221014.el9.x86_64 NetworkManager-1.40.0-1.el9.x86_64 How reproducible: 100% Steps to Reproduce: echo "interfaces: - name: bond0 state: up type: bond link-aggregation: mode: 802.3ad - name: bond0.4000 type: vlan state: up vlan: base-iface: bond0 id: 4000 - name: vrf0 state: up type: vrf vrf: route-table-id: 100 port: - bond0 - bond0.4000 " | nmstatectl apply echo "interfaces: - name: bond0 type: bond state: absent - name: vrf0 type: vrf state: absent" | nmstatectl apply # Got error while all interfaces were removed, but NM connection of bond0.4000 remained ip link show nmcli con Actual results: NmstateError: Bug: DbusConnectionError: org.freedesktop.NetworkManager.DependencyFailed: parent device '4339ad3a-0c1e-45da-9b9c-55d12a9ef786' not found Expected results: No error, bond0, vrf0 and bond0.4000 with their NM connections are all removed Additional info: This wokrs in nmstate python version