Created attachment 1737936 [details] journal Description of problem: NetworkManager fails to bring up a VLAN interface because the traffic shaping options have been configured by another service (sqm-scripts). Version-Release number of selected component (if applicable): NetworkManager-1.26.4-1.fc33.x86_64 sqm-scripts-1.4.0-2.fc33.noarch How reproducible: Always Steps to Reproduce: 1. Create a VLAN connection, for example enp4s0.20 2. Configure sqm-scripts to apply the layer_cake.qos settings on enp4s0.20 3. Reboot Actual results: At startup, the interface activation fails with this error: dic 09 12:25:26 NetworkManager[820]: <warn> [1607513126.9708] platform-linux: do-delete-tfilter[9: -65536]: failure 22 (Invalid argument - Parent Qdisc doesn't exists) dic 09 12:25:26 NetworkManager[820]: <warn> [1607513126.9710] device (enp4s0.20): failed applying traffic control rules dic 09 12:25:26 NetworkManager[820]: <info> [1607513126.9710] device (enp4s0.20): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed') dic 09 12:25:26 NetworkManager[820]: <info> [1607513126.9710] device (enp4s0.20): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed') dic 09 12:25:26 NetworkManager[820]: <info> [1607513126.9724] manager: NetworkManager state is now CONNECTED_LOCAL dic 09 12:25:26 NetworkManager[820]: <warn> [1607513126.9757] device (enp4s0.20): Activation: failed for connection 'wan' dic 09 12:25:26 NetworkManager[820]: <info> [1607513126.9809] device (enp4s0.20): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') This failure causes sqm-scripts to stop. One second later, NetworkManager attempts to connect again and this time it succeeds. Expected results: No conflict if the qdisc is configured while the interface is being brought up. Additional info: I've been discussing this issue with a sqm-scripts developer in this pull request: https://github.com/tohojo/sqm-scripts/pull/129
I'm not sure the networkmanager fault is actually due to sqm-scripts; rather my guess would be that it fails because it expects to find a qdisc on the interface at inception but VLAN interfaces use 'noqueue' so they don't have one... :)
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.