[Bug 964654] New: /etc/hostname settings ignored
http://bugzilla.suse.com/show_bug.cgi?id=964654 Bug ID: 964654 Summary: /etc/hostname settings ignored Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: hkuehnemund@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- YaST set an arbitrary hostname (linux-6o0n) during installation on my laptop (using DHCP on eth0 and wlan0). As YaST -> Hostnames does not offer an option to change the hostname either. So I changed /etc/hostname, saved the file, restarted network as well as rebooted a couple of times. Hwoever, content of /etc/hostname is not considered ... #linux-6o0n:~ # cat /etc/hostname #linux-6o0n.suse e1m1 #linux-6o0n:~ # -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c1 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |hkuehnemund@suse.com, | |mfilka@suse.com Flags| |needinfo?(hkuehnemund@suse. | |com) --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> --- maybe you have the "use hostname from DHCP" checkbox enabled in "yast2 lan" ? Otherwise the important question would be NetworkManager or wicked? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c2 Hannes Kühnemund <hkuehnemund@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(hkuehnemund@suse. | |com) | --- Comment #2 from Hannes Kühnemund <hkuehnemund@suse.com> --- I cannot change those settings with "yast2 lan", see screenshot. Seems that NetworkManager is handling it ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c3 --- Comment #3 from Hannes Kühnemund <hkuehnemund@suse.com> --- Created attachment 664162 --> http://bugzilla.suse.com/attachment.cgi?id=664162&action=edit screenshot "yast2 lan" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c4 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |GNOME Assignee|bnc-team-screening@forge.pr |bnc-team-gnome@forge.provo. |ovo.novell.com |novell.com --- Comment #4 from Bernhard Wiedemann <bwiedemann@suse.com> --- NetworkManager is handled by gnome team -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c5 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org Flags| |needinfo?(hkuehnemund@suse. | |com) --- Comment #5 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Hannes Kühnemund from comment #2)
I cannot change those settings with "yast2 lan", see screenshot. Seems that NetworkManager is handling it ...
Yast says it "can't configure *SOME* settings" - The hostname is not amongst the settings it can't manage for you. Klick OK, change to the tab Hostname/DNS and you will see that the part for settings the hostname is NOT grayed out.. and can be configured. alternatively, you can use
hostnamectl set-hostname <NAME>
Please verify and report back -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c6 --- Comment #6 from Dominique Leuenberger <dimstar@opensuse.org> --- (In reply to Bernhard Wiedemann from comment #4)
NetworkManager is handled by gnome team
FWIW: at the time NM launches the network (in the user session), the hostname has long been set already on the command line -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c7 Hannes Kühnemund <hkuehnemund@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(hkuehnemund@suse. | |com) | --- Comment #7 from Hannes Kühnemund <hkuehnemund@suse.com> --- (In reply to Dominique Leuenberger from comment #5)
Yast says it "can't configure *SOME* settings" - The hostname is not amongst the settings it can't manage for you.
Klick OK, change to the tab Hostname/DNS and you will see that the part for settings the hostname is NOT grayed out.. and can be configured.
That worked, thank you. So basically this is a YaST usability issue because when you open YaST2 and search for "hostname", you get the "hostname module" presented, which is entirely useless in this scenario (see screenshot). Shall we move this to the YaST team (Jiri S.)? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c8 --- Comment #8 from Hannes Kühnemund <hkuehnemund@suse.com> --- Created attachment 664176 --> http://bugzilla.suse.com/attachment.cgi?id=664176&action=edit yast2 hostname being useless here -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c9 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|GNOME |YaST2 Assignee|bnc-team-gnome@forge.provo. |yast2-maintainers@suse.de |novell.com | QA Contact|qa-bugs@suse.de |jsrain@suse.com --- Comment #9 from Dominique Leuenberger <dimstar@opensuse.org> --- YaST Team - please consider if you want / can make something out of the report. Changing a hostname seems not to be as straight forward -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c10 --- Comment #10 from Hannes Kühnemund <hkuehnemund@suse.com> --- Well, the "hostname" option in YaST2 does not allow to change the hostname, but the user has to run yast2 lan instead. This is confusing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c11 --- Comment #11 from Hannes Kühnemund <hkuehnemund@suse.com> --- Where are we with this? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c12 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wimer@suse.com Flags| |needinfo?(wimer@suse.com) --- Comment #12 from Lukas Ocilka <locilka@suse.com> --- (In reply to Hannes Kühnemund from comment #8)
Created attachment 664176 [details] yast2 hostname being useless here
In fact, this is a module for managing `Hostname Aliases` in /etc/hosts That might, indeed, be a bit confusing for newcomer. I'd ask Ken for help if you think it needs to be changed. Additionally, changing hostname for a system managed by NetworkManager works as defined by Dominique. Changing this to something more understandable also depends on Ken's design. The fact, that this is confusing as it's not enough to just change /etc/hostname is indeed confusing, but beyond Yast responsibility as this is defined by the basesystem. (In reply to Hannes Kühnemund from comment #11)
Where are we with this?
This is just a P5 for openSUSE, we are implementing new features and we are fully booked till the feature freeze and at least two more weeks after that. If it is a top priority for you, please, adjust it in Bugzilla, but what I'm currently seeing are in fact two separate bugreports here, that deserves two separate bugports as they (also) might have different priorities. So, Ken? Could you PLS take a look? In case of any questions, PLS talk to Michal, Me, Jiri and/or Hannes. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 Knut Alejandro Anderssen González <kanderssen@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen@suse.com, | |wimer@suse.de Flags| |needinfo?(wimer@suse.de) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=964654 http://bugzilla.suse.com/show_bug.cgi?id=964654#c14 Tomáš Chvátal <tchvatal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #14 from Tomáš Chvátal <tchvatal@suse.com> --- This is automated batch bugzilla cleanup. The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such it 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 openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com