https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |ms@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c3 --- Comment #3 from Frederic Crozat 2013-05-22 13:33:25 UTC --- it looks like (open)SUSE had a behaviour regarding /etc/HOSTNAME (or /etc/hostname these days) which is different from other distributions (like Fedora, I can't say for Debian..) which are setting /etc/hostname as hostname and not stripping it. I can probably modify systemd to strip anything after the first . (like boot.localnet was doing) but it would be nice if somebody could explain why we have this "different" behaviour.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c5 --- Comment #5 from Boris Wesslowski 2013-05-23 10:11:52 UTC --- I also found this to be inconsistent among distributions (e.g. RHEL does fqdn, CentOS does host name, all Debians and Ubuntus i looked at only had a host name in /etc/hostname to begin with, SLES does host name). hostname(5) allows a free-form string up to 64 characters in length (but recommends something compatible with DNS). The pacemaker documentation contains examples on Fedora where among the first things they do is modifying /etc/sysconfig/network to have uname -n return a host name instead of fqdn. This currently does not seem to be an option on openSUSE 12.3. Thanks for the quick fix, uname -n and DRBD/OpenAIS/Pacemaker now work just as expected. Since at least drbd and pacemaker configurations had to be customized for this behavior on openSUSE 12.3, deploying this change will require reconfiguration of existing setups, there should be a warning in the change log... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c7 --- Comment #7 from Boris Wesslowski 2013-05-24 09:35:12 UTC --- Since I don't know if OBS can simply make me a diff, may I ask what you changed? Is the fix in binary code or "just some text file"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c9 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|maintenance@opensuse.org | --- Comment #9 from Frederic Crozat 2013-05-24 12:10:07 UTC --- So, after discussing with various people internally, including maintenance team and based on comment 5, we should not push a fix for this bug on 12.3, since it might break existing setup. I'll push the fix for Factory but unless we get confirmation the fix for this bug on 12.3 won't have any impact on default installed system, we won't push it for 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c11 --- Comment #11 from Boris Wesslowski 2013-05-27 12:33:46 UTC --- To put the two angles in comment 9 into perspective, this fix will not affect a default installed system; the affected software is not preconfigured by default and the change is only as bad as changing the host name with yast or dhcp. drbd and pacemaker are the only programs that come to mind that once configured will be unable to recognize their configuration or may react with failures in clustering if the output of uname -n changes. Usage of drbd and especially pacemaker is probably rare among openSUSE 12.3 installations. Even so a warning up to an interactive dialog would be adequate for the update in such cases. So while pushing this fix is probably not as bad as it may seem I can understand if you don't want to on 12.3; I'm ok with Factory being fixed, thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=820213 https://bugzilla.novell.com/show_bug.cgi?id=820213#c13 Thomas Espenhain changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas@espenhain.eu --- Comment #13 from Thomas Espenhain 2013-05-30 15:53:49 UTC --- Will the fix be in release 13.1? We have also problems with the new behavior. We have a lot of custom scripts depending on $HOSTNAME env var or hostname command expecting the hostname without domain. So I will skip the 12.3 release and hope in 13.1 the old behavior is restored again like in the releases before. By the way if you change a network setting via yast2 (i.e. toggle "Assign Hostname to Loopback IP" in Hostname/DNS tab) yast2 restores the old behavior until the next reboot. So if current 12.3 installtions depending on the output of hostname, they will get in trouble after they changed the network setting. It doesn't matter wheater the setting "Assign Hostname to Loopback IP" is enabled or not. Greetz Thomas -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.