Bug 2023521 - Switching off automatic DNS is not respected
Summary: Switching off automatic DNS is not respected
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 35
Hardware: aarch64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Marius Vollmer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-15 23:27 UTC by Rémi Lauzier
Modified: 2022-03-26 15:02 UTC (History)
7 users (show)

Fixed In Version: cockpit-264-1.fc35 cockpit-264-1.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-27 04:08:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Image of cockpit conf (128.19 KB, image/png)
2021-11-15 23:27 UTC, Rémi Lauzier
no flags Details
image of networkManager conf (134.41 KB, image/png)
2021-11-15 23:28 UTC, Rémi Lauzier
no flags Details

Description Rémi Lauzier 2021-11-15 23:27:53 UTC
Created attachment 1841922 [details]
Image of cockpit conf

Description of problem: When modifying the network configuration, cockpit refuse to follow.


Version-Release number of selected component (if applicable):
cockpit version 257

How reproducible:
Everytime i change the dns to not be automatic, it doesn't respect my choice. And on ipv6 it refuse to accept the address i put. Even when changing manually the network conf in /etc/NetworkManager/ it doesn't respect the automatic dns config. It only respect the address that i have put.


Steps to Reproduce:
1. Try changing the setting to not be automatic
2. When it finish, cockpit return to automatic configuration

Actual results:
It doesn't respect user choice.

Expected results:
It should respect user choice.

Additional info:

Comment 1 Rémi Lauzier 2021-11-15 23:28:38 UTC
Created attachment 1841923 [details]
image of networkManager conf

Comment 2 Martin Pitt 2021-11-16 16:18:05 UTC
I tested this on current Fedora 35, and confirm this bug. Thanks for the report!

Comment 3 Marius Vollmer 2022-02-23 13:24:16 UTC
Autsch, we messed this up when rewriting to Patternfly and React: https://github.com/cockpit-project/cockpit/pull/17038

Comment 4 Fedora Update System 2022-02-25 09:44:52 UTC
FEDORA-2022-a92eec5eea has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a92eec5eea

Comment 5 Fedora Update System 2022-02-25 09:46:33 UTC
FEDORA-2022-f48fec88f0 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f48fec88f0

Comment 6 Fedora Update System 2022-02-25 18:21:24 UTC
FEDORA-2022-f48fec88f0 has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-f48fec88f0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-f48fec88f0

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-02-25 20:49:25 UTC
FEDORA-2022-a92eec5eea has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a92eec5eea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a92eec5eea

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-02-27 04:08:37 UTC
FEDORA-2022-f48fec88f0 has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-03-26 15:02:24 UTC
FEDORA-2022-a92eec5eea has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.