Description of problem:
No way to set hostname in anaconda
Version-Release number of selected component (if applicable):
Fedora 18 Alpha RC2
Install Fedora 18 from DVD image.
Steps to Reproduce:
1. Install Fedora 18 from DVD image
2. No option to set hostname
No option to set hostname
Option as in previous versions to set hostname to something besides localhost.localdomain
It is possible that this option is in the configuration for the network adapter, but when I tried to click on the configure button, nothing happened.
While it did set up my network adapter, I just had to accept how anaconda decided to set it up, and couldn't go into the configuration to change it.
Also, it didn't create the /etc/sysconfig/network file.
Setting hostname is not designed/implemented anywhere in UI yet, it should work using kickstart network --hostname option, though not in Alpha (RC2), patches are only in master.
> While it did set up my network adapter, I just had to accept how anaconda
> decided to set it up, and couldn't go into the configuration to change it.
> Also, it didn't create the /etc/sysconfig/network file.
This is fixed in master with patches mentioned above.
F18 TC2 still has no option to set the hostname
In forums.fedoraforum.org (F18 Development), someone mentioned this:
/etc/sysconfig/network (Hostname only) <<<< RELEVANT TO THIS BUGREPORT
SystemD v +195 for F18 now has:
# hostnamectl status
Static hostname: superservercowball
Pretty hostname: superserver.cowball
Icon name: n/a
Machine ID: 5d91ca5f9debf4df91890550bb335d84
Boot ID: aec5010be8b945149e041ad03324e3b1
Operating System: Fedora 18 (Spherical Cow)
CPE OS Name: cpe:/o:fedoraproject:fedora:18
Kernel: Linux 3.6.3-3.fc18.x86_64
# hostnamectl set-hostname hyperserver.cowball
Installing and updating from F18b TC6 bring such systemd version, so future
test composes will most likely have such systemd version.
The hostname could be set by anaconda or during firstboot.
If it is decided that the hostname will be set by firstboot, then firstboot
can simply add a text dialog or similar to enter the hostname and execute a 'hostnamectl set-hostname'. It looks simple for firstboot to be implemented, exept for package groups that do not have xorg.
I would prefer for the hostname to be set by anaconda, so one can boot with the desired hostname. (the setting could be added below 'set root password' during install.
We need to set hostname before storage configuration as it is used for default LVM and RAID names.
FYI, the /etc/sysconfig/network -> /etc/hostname patch is being reviewed.
*** Bug 870921 has been marked as a duplicate of this bug. ***
(In reply to comment #5)
> To Reartes:
> We need to set hostname before storage configuration as it is used for
> default LVM and RAID names.
Indeed this is true .. see: bug 884701 for details about
the current regression in Anaconda.
Nominating as NTH to bring more eyes to it, although I'd prefer to dedicate proper time to design / discuss the place of the setting in UI post F18.
What about a boot parameter, like 'advanced' that will ask the user for a hostname, BEFORE anaconda?
This would be a Q&D route for F18.
Advanced parameter specified:
The current hostname is 'fedora', type the desired hostname or just press ENTER to accept the current value.
Setting hostname to Cowball
NTH nomination was done wrong by mistake, fixing. I am +1 NTH at least on this, it is a very common complaint about newUI that there is no hostname setting.
Discussed at 2012-12-12 NTH review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-12/f18final-blocker-review-4.2012-12-12-17.01.log.txt . Accepted as NTH, this is a regression from F17 behaviour and a popular request/complaint about newUI, plus it causes https://bugzilla.redhat.com/show_bug.cgi?id=884701 for LV naming.
what is the anticipated way to change hostname in fedora 18 at all? I can't figure out.
Here is updates image with a patch adding hostname to network spoke:
Hostname sanity check is done when leaving spoke.
(In reply to comment #14)
> Here is updates image with a patch adding hostname to network spoke:
> Hostname sanity check is done when leaving spoke.
It is for F18 TC2
Tested (against TC3 - the updates.img seems to work ok). The dialog works. The hostname is properly set on the installed system. The LV name uses the hostname I set (used autopart). Hostname sanity check seems to work - except that the error message is too long and goes off the side of the screen; I think the error message display code lacks line wrapping, I need to file a separate bug for that (seen it with root password errors also). This patch looks good, please apply it for next anaconda build.
Filed https://bugzilla.redhat.com/show_bug.cgi?id=888112 for the error message overflow.
Tested using final TC3 (anaconda version 18.37.3) and performed a minimal install on virtualbox VM.
hostname textbox appears under network spoke and the given hostname is retained for installation and shows up correctly in the installed system.
Radek, can you please commit this so we get it in the next build? It missed 37.4 unfortunately.
I see some nitpicking about the layout on the ML, but seriously, it's getting pretty late, just pick something and go with it guys :)
(In reply to comment #13)
> man hostnamectl
This sucks. Why isn't just changing the /etc/hostname file
sufficient? I tried just changing the file and it did nothing.
Note that calling out to arbitrary binaries is unacceptable
when modifying guests (eg. from virt-sysprep).
(In reply to comment #21)
> (In reply to comment #13)
> > man hostnamectl
> This sucks. Why isn't just changing the /etc/hostname file
> sufficient? I tried just changing the file and it did nothing.
> Note that calling out to arbitrary binaries is unacceptable
> when modifying guests (eg. from virt-sysprep).
I'm confused. It says "Fixed In Version: anaconda-18.37.5-1"
up above yet I don't see the usual automated messages in the
Comment areas reporting the progress of the fix, asking for
karma and so on. Am I missing something? Thanks.
*** Bug 889740 has been marked as a duplicate of this bug. ***
Option to set hostname is present under the new TC4 image (anaconda 18.37.8) and it does set the hostname for the installed system as specified during installation.
Works well. This bug report can be closed (I think).
Yes, it can.