This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2214511 - Failed to when "controller" option and controller interface are both mentioned
Summary: Failed to when "controller" option and controller interface are both mentioned
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nmstate
Version: 9.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Gris Ge
QA Contact: Mingyu Shi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-13 07:52 UTC by Mingyu Shi
Modified: 2023-08-17 09:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-17 09:59:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-714 0 None None None 2023-08-11 12:31:07 UTC
Red Hat Issue Tracker   RHEL-1414 0 None None None 2023-08-17 09:59:38 UTC
Red Hat Issue Tracker RHELPLAN-165632 0 None None None 2023-08-11 12:31:22 UTC

Description Mingyu Shi 2023-06-13 07:52:32 UTC
Description of problem:
Failed to when "controller" option and controller interface are both mentioned.
Check the reproducer below, if mentioned "controller: br0" in bond0 interface and contains controller(interfaces.br0) in the desired state, it failed.

My scenario is:
(Already configured bond0 and br0)
1. I requested the full state of bond0 and br0
2. Changed some values(didn't care about the other items)
3. Tried applying the edited state.
It failed since the full state I got in step 1 contains "controller"(I didn't need it, but I didn't care about it neither) 

Version-Release number of selected component (if applicable):
nmstate-2.2.12-2.el9.x86_64
nispor-1.2.10-1.el9.x86_64
NetworkManager-1.43.9-1.el9.x86_64
openvswitch2.15-2.15.0-82.el9fdp.x86_64
DISTRO=RHEL-9.3.0-updates-20230611.28

How reproducible:
100%

Steps to Reproduce:
echo "
interfaces:
- name: bond0
  type: bond
  state: up
  controller: br0
  link-aggregation:
    mode: balance-rr
- name: br0
  type: ovs-bridge
  state: up
  bridge:
    port:
    - name: bond0
" | nmstatectl apply

Actual results:
NmstateError: InvalidArgument: Interface bond0 has controller br0 but not listed in port list of controller interface

Expected results:
No failure

Additional info:
Replaced br0 type as "linux-bridge", got the same failure.
Removing "controller: br0" or "br0.bridge.port" works


Note You need to log in before you can comment on or make changes to this bug.