Bug 1828458
| Summary: | [RFE] nm-online systemd unit file has hardcoded timeout | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Dan Williams <dcbw> |
| Component: | NetworkManager | Assignee: | Thomas Haller <thaller> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.2 | CC: | acardace, atragler, bgalvani, lrintel, rkhan, rob.fisher, sukulkar, thaller, till, vbenes |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 8.2 | Flags: | pm-rhel:
mirror+
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | Telco | ||
| Fixed In Version: | NetworkManager-1.25.1-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 01:49:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dan Williams
2020-04-27 18:15:50 UTC
the rhbz links to case https://access.redhat.com/support/cases/#/case/02639509, but I fail to understand how that is related. It would be interesting to know why it takes 32 seconds. The timeout is something that should not be reached in regular operation. Maybe we should just increase the timeout to 45 seconds instead? Working systems would should suffer from this increased timeout. How about https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/484 ? Would "EnvironmentFile=-/etc/sysconfig/nm-online" be preferable? Why? (In reply to Thomas Haller from comment #2) > the rhbz links to case > https://access.redhat.com/support/cases/#/case/02639509, but I fail to > understand how that is related. It's something we found while debugging the cluster for that specific support case, and will fix one of the issues we found there WRT node hostname. > It would be interesting to know why it takes 32 seconds. The timeout is > something that should not be reached in regular operation. Maybe we should > just increase the timeout to 45 seconds instead? Working systems would > should suffer from this increased timeout. I think it's just "enterprise stuff takes longer". We'll grab some NM logs to diagnose further. > How about > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/ > merge_requests/484 ? > Would "EnvironmentFile=-/etc/sysconfig/nm-online" be preferable? Why? Filename was just a suggestion based off what other services do in RHEL/Fedora. Doesn't matter what the file is as long as it's %config and can be edited locally. Will comment on the MR. fixed on master: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/e468b48ab7b8e2ddc8802db4b93e3f13787835e4 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4499 |