Description of problem: During installation of Fedora 24 on s390x I can see two network connections: [anaconda root@test ~]# nmcli c NAME UUID TYPE DEVICE enca00 07f02cc1-670c-4dd1-9ece-07a6ec94ac1b 802-3-ethernet enca00 enca00 9a9d8330-64a4-4ed1-aef6-7ebb2eefce7d 802-3-ethernet -- [anaconda root@test ~]# Version-Release number of selected component (if applicable): NetworkManager-1.2.0-0.8.rc1.fc24 How reproducible: always Steps to Reproduce: 1. run installation on s390x Actual results: two network connections during the installation Expected results: just one network connection reported by nmcli Additional info: * the installation images were created locally by lorax-24.17-1.fc24, since there are no official F24 composes for s390x yet.
Created attachment 1147234 [details] journalctl
Created attachment 1147235 [details] nmcli c show uuid 07f02cc1-670c-4dd1-9ece-07a6ec94ac1b
Created attachment 1147237 [details] nmcli c show uuid 9a9d8330-64a4-4ed1-aef6-7ebb2eefce7d
Created attachment 1147497 [details] [PATCH] device/ethernet: ignore s390 'portname' attribute when not set This patch should fix the issue, but I was not able to test it (yet).
(In reply to Beniamino Galvani from comment #4) > Created attachment 1147497 [details] > [PATCH] device/ethernet: ignore s390 'portname' attribute when not set > > This patch should fix the issue, but I was not able to test it (yet). lgtm
patch lgtm too
Merged to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0589e659ca1aab76be9ca11e705bef56c3b03f45 nm-1-0: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-0&id=fc6b8ba1bf487321090de40b19766a04725b419f and nm-1-2: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=5fa3c1230fe1dcb5d2b1f838ed99bba8703d4e57
I've built NM rpms with the patch applied and created new installation images - this issue is not reproducible with the patch applied. It also resolves the issue reported in bug 1327169, so I will close that bug as a duplicate of this one.
*** Bug 1327169 has been marked as a duplicate of this bug. ***
Where can we expect an update for NetworkManager package? It's blocking proper testing of F-24 on s390x.
ping, any update here, please?
We already have NetworkManager-1.2.2-1.fc24 built, is the fix there?
(In reply to Dan Horák from comment #12) > We already have NetworkManager-1.2.2-1.fc24 built, is the fix there? Yes, it is.
NetworkManager-1.2.4-1.fc24 network-manager-applet-1.2.4-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f739ece3cf
NetworkManager-1.2.4-1.fc24, network-manager-applet-1.2.4-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f739ece3cf
NetworkManager-1.2.4-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-fade485364
NetworkManager-1.2.4-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-fade485364
network-manager-applet-1.2.4-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f739ece3cf
NetworkManager-1.2.4-2.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.