|
Bugzilla – Full Text Bug Listing |
| Summary: | netcfg: do not use .site as default TLD | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Ludwig Nussel <lnussel> |
| Component: | YaST2 | Assignee: | Tomáš Chvátal <tchvatal> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | tiwai |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 923990 | ||
|
Description
Ludwig Nussel
2015-06-09 08:44:30 UTC
maybe we could even merge netcfg into aaa_base or rather net-tools where the manpages of most files are The hostname stuff is fun. Especially all the migrations around. Also yast writes there, we would need to tweak it out to talk with systemd and tell it to set hostname by its mechanisms instead of writting it to the file. I don't mind where the files are put in the end, there is like 1 bug per 5 years on this package, so it is almost no-effort to keep it working :) Sent it to the Factory. Anyway if you want to put it all into separate package file a bug against the other one. I am willing to give this pkg up ;-) This is an autogenerated message for OBS integration: This bug (934056) was mentioned in https://build.opensuse.org/request/show/311665 Factory / netcfg This is an autogenerated message for OBS integration: This bug (934056) was mentioned in https://build.opensuse.org/request/show/320307 Factory / netcfg The recent update broke my machine after updating Tumbleweed. Now it got an empty /etc/HOSTNAME and the old one was stored in /etc/HOSTNAME.rpmorig. And hostname command returns "localhost". Meanwhile /etc/hostname (and /etc/hostname.rpmorig) contain the right string. (In reply to Takashi Iwai from comment #7) > The recent update broke my machine after updating Tumbleweed. > Now it got an empty /etc/HOSTNAME and the old one was stored in > /etc/HOSTNAME.rpmorig. And hostname command returns "localhost". > > Meanwhile /etc/hostname (and /etc/hostname.rpmorig) contain the right string. Can't reproduce on any of the testing Factory deploiments I have. Any insight on how the layout was done before you updated? Eg. HOSTNAME being proper symlink to hostname or something special, etc etc. (In reply to Tomáš Chvátal from comment #8) > (In reply to Takashi Iwai from comment #7) > > The recent update broke my machine after updating Tumbleweed. > > Now it got an empty /etc/HOSTNAME and the old one was stored in > > /etc/HOSTNAME.rpmorig. And hostname command returns "localhost". > > > > Meanwhile /etc/hostname (and /etc/hostname.rpmorig) contain the right string. > > Can't reproduce on any of the testing Factory deploiments I have. > > Any insight on how the layout was done before you updated? > Eg. HOSTNAME being proper symlink to hostname or something special, etc etc. No, /etc/HOSTNAME is a normal file. I can reproduce this by reinstalling netcfg. % cat /etc/HOSTNAME alsa1.suse.de % zypper in -f netcfg .... (1/1) Installing: netcfg-11.5-30.1 .......................................[done] Additional rpm output: warning: /etc/aliases created as /etc/aliases.rpmnew warning: /etc/defaultdomain created as /etc/defaultdomain.rpmnew warning: /etc/exports created as /etc/exports.rpmnew warning: /etc/hostname saved as /etc/hostname.rpmorig warning: /etc/hosts created as /etc/hosts.rpmnew warning: /etc/hosts.equiv created as /etc/hosts.equiv.rpmnew % cat /etc/HOSTNAME (In reply to Takashi Iwai from comment #9) > (In reply to Tomáš Chvátal from comment #8) > > (In reply to Takashi Iwai from comment #7) > > > The recent update broke my machine after updating Tumbleweed. > > > Now it got an empty /etc/HOSTNAME and the old one was stored in > > > /etc/HOSTNAME.rpmorig. And hostname command returns "localhost". > > > > > > Meanwhile /etc/hostname (and /etc/hostname.rpmorig) contain the right string. > > > > Can't reproduce on any of the testing Factory deploiments I have. > > > > Any insight on how the layout was done before you updated? > > Eg. HOSTNAME being proper symlink to hostname or something special, etc etc. > > No, /etc/HOSTNAME is a normal file. > I can reproduce this by reinstalling netcfg. > > % cat /etc/HOSTNAME > alsa1.suse.de > > % zypper in -f netcfg > .... > (1/1) Installing: netcfg-11.5-30.1 > .......................................[done] > Additional rpm output: > warning: /etc/aliases created as /etc/aliases.rpmnew > warning: /etc/defaultdomain created as /etc/defaultdomain.rpmnew > warning: /etc/exports created as /etc/exports.rpmnew > warning: /etc/hostname saved as /etc/hostname.rpmorig > warning: /etc/hosts created as /etc/hosts.rpmnew > warning: /etc/hosts.equiv created as /etc/hosts.equiv.rpmnew > > % cat /etc/HOSTNAME Okay, where came from the HOSTNAME as file, it is not supposed to be such since SLE12. Anyway will test it out here as it still should kinda converted it correctly and not bork like this. And seems I am still unable to reproduce it even if I hand create HOSTNAME file Before: scarabeus@bugaboo: /etc $ ll |grep hostname -rw-r--r-- 1 root root 16 25. srp 09.25 hostname scarabeus@bugaboo: /etc $ ll |grep HOSTNAME -rw-r--r-- 1 root root 19 25. srp 09.50 HOSTNAME After: scarabeus@bugaboo: /etc $ ll |grep hostname -rw-r--r-- 1 root root 19 25. srp 09.52 hostname lrwxrwxrwx 1 root root 8 25. srp 09.51 HOSTNAME -> hostname It even carries over different value from HOSTNAME to hostname as you can see... Hmm, it's working for me, too. Wait... Maybe there was no /etc/hostname beforehand or empty, only /etc/HOSTNAME existed and contained the string. Then after update, it's linked to the empty new /etc/hostname. This sounds feasible? (In reply to Takashi Iwai from comment #12) > Hmm, it's working for me, too. > > Wait... Maybe there was no /etc/hostname beforehand or empty, only > /etc/HOSTNAME existed and contained the string. Then after update, it's > linked to the empty new /etc/hostname. This sounds feasible? Now it's broken again, but in a different way from what I wrote. I have an empty /etc/hostname and HOSTNAME is symlinked: % ls -l /etc/hostname -rw-r--r-- 1 root root 0 Aug 21 09:02 /etc/hostname % ls -l /etc/HOSTNAME lrwxrwxrwx 1 root root 8 Aug 21 09:02 /etc/HOSTNAME -> hostname Then set a name string: % echo alsa1.suse.de > /etc/hostname % ls -l /etc/hostname -rw-r--r-- 1 root root 14 Aug 25 10:27 /etc/hostname And update: % zypper in -f netcfg .... (1/1) Installing: netcfg-11.5-30.1 .......................................[done] Additional rpm output: warning: /etc/aliases created as /etc/aliases.rpmnew warning: /etc/defaultdomain created as /etc/defaultdomain.rpmnew warning: /etc/exports created as /etc/exports.rpmnew warning: /etc/hostname saved as /etc/hostname.rpmorig warning: /etc/hosts created as /etc/hosts.rpmnew warning: /etc/hosts.equiv created as /etc/hosts.equiv.rpmnew It's gone again: % ls -l /etc/hostname -rw-r--r-- 1 root root 0 Aug 21 09:02 /etc/hostname % cat /etc/hostname Cra* that indeed is a bug. Fixed by sr#326599. |