Bug 1474055
Summary: | Upgrading from f25 to f26 enables network manager | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thomas Köller <thomas> |
Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | bgalvani, dcbw, fgiudici, lkundrak, wwoods, zbyszek |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-29 12:03:37 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
Thomas Köller
2017-07-23 13:04:30 UTC
If anything, that'd be a bug in the NetworkManager packages. Nevertheless, that sounds unlikely — NetworkManager.rpm has normal scriptlets, which do nothing when the package is just upgraded. Did you have NetworkManager.rpm installed before the upgrade? You said NetworkManager.service was disabled, but just to clarify: was it disabled or masked? (In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > Did you have NetworkManager.rpm installed before the upgrade? Yes. I am running a gnome desktop that would certainly break if NetworkManager were removed. > You said NetworkManager.service was disabled, but just to clarify: was it > disabled or masked? IIRC, I had it disabled, although I cannot tell for sure because I cannot restore my system to the state before the upgrade. I checked the transaction history record for the upgrade and found this: [root@sarkovy ~]# dnf history info 547 | fgrep -e NetworkManager Install NetworkManager-1:1.8.2-1.fc26.x86_64 @@commandline Upgraded NetworkManager-config-connectivity-fedora-1:1.4.4-5.fc25.x86_64 @updates/25 Upgraded NetworkManager-glib-1:1.4.4-5.fc25.x86_64 @updates/25 Upgraded NetworkManager-libnm-1:1.4.4-5.fc25.x86_64 @updates/25 Install NetworkManager-wifi-1:1.8.2-1.fc26.x86_64 @@commandline To me this looks as if NetworkManager has been re-installed instead of upgraded, which would explain why it has been enabled, as this is the default. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. |