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.
I will try to explain the patch in c#20, also ccing jiri to see if it can be accepted in libteam upstream.
-----
Prior these fixes, teamd was managed by systemd, but it didn't have any dependence in teamd.service. It could lead to that teamd was stopped before nfs was stopped, then nfs block.
After we added 'Before=network-pre.target', it would delay teamd's stop until network was stopped completely. It seemed the shutdown order was nfs -> network -> teamd then. The nfs block issue was gone.
Unfortunately, teamd was also stopped in network's ifdown-Team script through "systemctl stop teamd.service". It means our change will make network try to
stop one service (teamd) that was dependent on network itself, then the network block issue showed up.
Now we change to start teamd with '/usr/bin/teamd -d' in network's ifup-Team script and stop with '/usr/bin/teamd -k'. It means teamd will not be managed by systemd, but be managed by network completely, which can fix all the issues we mentioned in this BZ.
IMO, it's better let the teamd NOT work as a systeamd service, but be ONLY managed by network and be a part of network service.
1) The shudown block issue here can be fixed, :D
2) teamd is one daemon each team device, earlier to handle in network. Besides, even if we make it work as a systemd service, network still has to start/stop it. It can never be independent from network.
(In reply to Xin Long from comment #30)
> IMO, it's better let the teamd NOT work as a systeamd service, but be ONLY
> managed by network and be a part of network service.
> 1) The shudown block issue here can be fixed, :D
Agree, that would be more easy to handle team.
I think you guys need to discuss this with systemd people.
Comment 33Marcelo Ricardo Leitner
2016-08-08 16:27:45 UTC
(In reply to Jiri Pirko from comment #32)
> I think you guys need to discuss this with systemd people.
We are also doing that, in upstream and internally. We are actually shooting everywhere as systemd folks couldn't help us much so far.
The latest idea (still in the works) we have is to still use systemd but ignore dependencies when stopping teamd. So we can still use systemd and most of its features, but also make it work as we need on stop.