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 1273947[details]
logfile showing the issue
The attached logfile is from test "bridge_up_slave" https://beaker.engineering.redhat.com/recipes/3766618 , testing upstream build NetworkManager 1.2.7-15058.90d341e300.el7
Scenario: nmcli - bridge - up slave
* Add a new connection of type "bridge" and options "con-name br10 ifname br10"
* Check ifcfg-name file created for connection "br10"
* Open editor for connection "br10"
* Set a property named "ipv4.method" to "manual" in editor
* Set a property named "ipv4.addresses" to "192.168.1.19/24" in editor
* Save in editor
* Check value saved message showed in editor
* Quit editor
* Bring up connection "br10"
* Add a new connection of type "bridge-slave" and options "con-name br10-slave autoconnect no ifname eth1 master br10"
* Check ifcfg-name file created for connection "br10-slave"
* Bring up connection "br10-slave"
^^^^^^^ fails
Note
[1493049242.7187] ... (eth1): Activation: connection 'br10-slave' \
master deactivated
Please review th/device-clear-master-rh1445394 (for nm-1-2).
According to vbenes, the tests only fail on nm-1-2 branch, but I think the same patch should also be applied to master and all newer stable branches.
Comment 3Beniamino Galvani
2017-04-26 13:37:17 UTC
(In reply to Thomas Haller from comment #2)
> Please review th/device-clear-master-rh1445394 (for nm-1-2).
It seems to me that the check you add is already handled by the code below, i.e. you could just do:
- if (plink->master <= 0)
- return;
the attached patch from comment 2 does not fix the CI tests, and it's unclear how to fix it.
It seems to affect only upstream version nm-1-2 (or it's unclear which versions else are affected).
I don't think that recent versions of upstream NetworkManager are affected (nor is recent RHEL affected, as NetworkManager is newer then 1.2).
Let's not invest time in fixing a CI failure on a no longer supported upstream(!) version.
I close this as WONTFIX.
Created attachment 1315303[details]
[patch] device: clear master device association on external changes
(In reply to Thomas Haller from comment #2)
> Please review th/device-clear-master-rh1445394 (for nm-1-2).
>
> According to vbenes, the tests only fail on nm-1-2 branch, but I think the
> same patch should also be applied to master and all newer stable branches.
for histroy, attach the patch here.
It applies on nm-1-2 branch, commit ae158d8a6da10cb7ac6d0a99ec70adc8a72c1ad5