Back to bug 1920398
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla | 2021-01-26 09:02:51 UTC | Pool ID | sst_networking_rhel_7 | |
| Xin Long | 2021-01-28 09:46:39 UTC | CC | lxin | |
| Xin Long | 2021-01-29 08:08:12 UTC | Assignee | rkhan | lxin |
| Petr Barta | 2021-02-04 10:47:44 UTC | CC | pbarta | |
| Flags | needinfo?(lxin) | |||
| Xin Long | 2021-02-09 09:00:02 UTC | Flags | needinfo?(lxin) | |
| Xin Long | 2021-02-10 04:27:51 UTC | CC | bgalvani | |
| Xin Long | 2021-02-10 05:05:40 UTC | Flags | needinfo?(bgalvani) | |
| Beniamino Galvani | 2021-02-10 08:10:16 UTC | Flags | needinfo?(bgalvani) | |
| Beniamino Galvani | 2021-02-22 08:22:53 UTC | CC | thaller | |
| Xin Long | 2021-02-23 10:52:15 UTC | Status | NEW | ASSIGNED |
| Red Hat One Jira (issues.redhat.com) | 2021-03-24 00:56:02 UTC | Link ID | Red Hat Issue Tracker RHELPLAN-72391 | |
| Marcelo Ricardo Leitner | 2021-03-29 15:00:36 UTC | CC | mleitner | |
| Xin Long | 2021-04-11 22:23:28 UTC | Assignee | lxin | bgalvani |
| Jamie Bainbridge | 2021-04-21 00:06:28 UTC | Group | redhat, private | |
| CC | jbainbri | |||
| Jamie Bainbridge | 2021-04-21 00:48:12 UTC | Link ID | Red Hat Knowledge Base (Solution) 5980411 | |
| Till Maas | 2021-05-12 05:50:28 UTC | Status | ASSIGNED | NEW |
| CC | acardace, atragler, lrintel, rkhan, sukulkar, till | |||
| Component | libteam | NetworkManager | ||
| Assignee | bgalvani | nm-team | ||
| Summary | Equivalent "primary-reselect" bonding option for teamd | RFE: Support activating team and bond ports in a specific order | ||
| QA Contact | liali | desktop-qa-list | ||
| RHEL Program Management | 2021-05-12 05:50:28 UTC | Keywords | FutureFeature | |
| Till Maas | 2021-06-08 09:50:43 UTC | CC | fge | |
| Flags | needinfo?(fge) | |||
| Gris Ge | 2021-06-24 04:21:17 UTC | Flags | needinfo?(fge) | needinfo?(forestia) |
| Gris Ge | 2021-07-08 13:17:54 UTC | Keywords | Triaged | |
| Fani Orestiadou | 2021-07-10 07:50:02 UTC | Flags | needinfo?(forestia) | |
| Gris Ge | 2021-07-29 04:27:44 UTC | Pool ID | sst_networking_rhel_7 | sst_networking_rhel_8 |
| Component | NetworkManager | NetworkManager | ||
| Version | 7.8 | 8.6 | ||
| Product | Red Hat Enterprise Linux 7 | Red Hat Enterprise Linux 8 | ||
| Target Milestone | rc | beta | ||
| Gris Ge | 2021-07-29 04:36:47 UTC | Doc Text | Cause: NetworkManager does not support activating bond/team ports in order of port priority. Consequence: Unexpected team/bond port been chose as active port. Workaround (if any): Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34 Result: Before issue been fixed, please use refer to workaround. | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Lucie Vařáková | 2021-08-16 13:01:30 UTC | Docs Contact | mmuehlfe | |
| Marc Muehlfeld | 2021-09-29 09:07:28 UTC | Doc Text | Cause: NetworkManager does not support activating bond/team ports in order of port priority. Consequence: Unexpected team/bond port been chose as active port. Workaround (if any): Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34 Result: Before issue been fixed, please use refer to workaround. | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. |
| Flags | needinfo?(bgalvani) | |||
| Beniamino Galvani | 2021-09-30 09:19:05 UTC | Flags | needinfo?(bgalvani) | |
| Jonathan Maxwell | 2021-10-11 23:48:29 UTC | Blocks | 2006093 | |
| Gris Ge | 2021-11-03 12:48:13 UTC | Blocks | 2006093 | |
| Lenka Špačková | 2021-11-10 08:32:35 UTC | Doc Text | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. //For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. |
| Flags | needinfo?(mmuehlfe) | |||
| Marc Muehlfeld | 2021-11-10 16:28:06 UTC | Flags | needinfo?(mmuehlfe) | needinfo?(jbainbri) |
| Jamie Bainbridge | 2021-11-10 23:31:59 UTC | Flags | needinfo?(jbainbri) | |
| Marc Muehlfeld | 2021-11-11 09:26:15 UTC | Doc Text | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. //For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. |
| Group | private, redhat | |||
| Fernando F. Mancera | 2022-02-10 10:27:33 UTC | CC | ferferna | |
| Red Hat Bugzilla | 2022-02-22 05:43:23 UTC | CC | atragler | |
| Jamie Bainbridge | 2022-09-27 01:45:38 UTC | CC | sfaye | |
| Keywords | Triaged | |||
| Target Release | --- | 8.8 | ||
| Pasi Karkkainen | 2022-11-09 15:29:40 UTC | CC | pasik | |
| Jamie Bainbridge | 2022-11-21 23:06:20 UTC | Keywords | Triaged | |
| Flags | needinfo?(jbainbri) | |||
| Flags | needinfo?(jbainbri) | needinfo?(sfaye) | ||
| Till Maas | 2022-12-06 15:37:10 UTC | Flags | needinfo?(sfaye) | |
| Priority | unspecified | high | ||
| Red Hat One Jira (issues.redhat.com) | 2023-01-20 11:51:29 UTC | Blocks | 2152304 | |
| Priority | high | medium | ||
| Link ID | Red Hat Issue Tracker NMT-17 | |||
| Jonathan Maxwell | 2023-04-12 02:07:39 UTC | Type | Bug | Feature Request |
| Assignee | nm-team | ferferna | ||
| CC | takirby | |||
| Blocks | 2183216 | |||
| Fernando F. Mancera | 2023-05-03 09:19:39 UTC | Status | NEW | ASSIGNED |
| Filip Pokryvka | 2023-05-03 19:33:18 UTC | CC | fpokryvk | |
| Fernando F. Mancera | 2023-05-15 14:23:57 UTC | Flags | needinfo?(takirby) | |
| Flags | needinfo?(takirby) | |||
| Status | ASSIGNED | POST | ||
| Fernando F. Mancera | 2023-05-22 07:51:46 UTC | Fixed In Version | NetworkManager-1.40.16-5.el8 | |
| Status | POST | MODIFIED | ||
| Fernando F. Mancera | 2023-05-22 08:32:12 UTC | Doc Type | Known Issue | Enhancement |
| Doc Text | .NetworkManager does not support activating bond and team ports in a specific order NetworkManager activates interfaces alphabetically by interface names. However, if an interface appears later during the boot, for example, because the kernel needs more time to discover it, NetworkManager activates this interface later. NetworkManager does not support setting a priority on bond and team ports. Consequently, the order in which NetworkManager activates ports of these devices is not always predictable. To work around this problem, write a dispatcher script. For an example of such a script, see the corresponding link:https://bugzilla.redhat.com/show_bug.cgi?id=1920398#c34[comment] in the ticket. | Feature: When bonding is configured in active-backup, balance-tlb or balance-alb the priority of the ports can be specified. The value range is signed 32-bit integer. A higher number means a higher priority. Reason: We want to close the gaps between team support and bonding support. The customers must be able to move from team to bonding easily. Result: A new property was added to bond-port in NetworkManager. In order to configure it with nmcli the user must specify `bond-port.prio <value>` when creating or modifying the port connection. |
||
| errata-xmlrpc | 2023-05-23 10:27:06 UTC | Status | MODIFIED | ON_QA |
| Vladimir Benes | 2023-05-29 12:06:18 UTC | CC | vbenes | |
| QA Contact | desktop-qa-list | fpokryvk | ||
| Gris Ge | 2023-07-07 08:37:22 UTC | Flags | needinfo?(forestia) |
Back to bug 1920398