Hide Forgot
Description of problem: After upgrading F17 to F19 via the FIDO process, no hostname offered to the DHCP server. Version-Release number of selected component (if applicable): How reproducible: Didn't try to reproduce. Steps to Reproduce: 1. Upgrade F17 to F19 using FIDO. 2. Use DHCP for IP allocation 3. Check DHCP server for hostname Actual results: DHCP (DSL Router box) inserts a generic hostname. Expected results: The same hostname as in F17. Additional info: hostnamectl updates all versions of the hostname, and the DHCP server shows the correct hostname.
Thanks, but I must admit i don't get it. (In reply to Oliver Sampson from comment #0) > Description of problem: > After upgrading F17 to F19 via the FIDO process, no hostname offered to the > DHCP server. *to* the server or *from* the server ? > Steps to Reproduce: > 1. Upgrade F17 to F19 using FIDO. What is FIDO ? > 2. Use DHCP for IP allocation > 3. Check DHCP server for hostname I don't understand this step. What exactly did you do ? > Actual results: > DHCP (DSL Router box) inserts a generic hostname. So I guess the router is dhcp server in this case and your Fedora machine is dhcp client, right ? If the problem is in what hostname does the router send (insert ?) then I can't do anything with it, can I ? > Additional info: > hostnamectl updates all versions of the hostname, and the DHCP server shows > the correct hostname. I don't get this, sorry. Can you perhaps re-formulate it ?
Hello, I'm not sure if it is the same problem, but yesterday I have found that hostname is somehow "baked" into initrd. Something copies /etc/hostname from filesystem to initrd, so the hostname from DHCP is not honored later (i.e. after deletion of /etc/hostname).
(In reply to Jiri Popelka from comment #1) > Thanks, but I must admit i don't get it. I'm not surprised. I think I had a senior moment while typing this up. > > (In reply to Oliver Sampson from comment #0) > > Description of problem: > > After upgrading F17 to F19 via the FIDO process, no hostname offered to the > > DHCP server. > > *to* the server or *from* the server ? I assume *to* the server. The way I understand DHCP is that the client sends a request message with a hostname, and the server sends/sets an IP address among other things. > > > Steps to Reproduce: > > 1. Upgrade F17 to F19 using FIDO. > > What is FIDO ? That's the senior moment. The FedUp upgrade process. > > > 2. Use DHCP for IP allocation > > 3. Check DHCP server for hostname > > I don't understand this step. What exactly did you do ? I looked in the DSL Router box for which computers it thinks are attached. For devices that don't have a name, it assigns a generic name like "PC_192_168_0_54". For my other machines, and this machine running F17 the name was the hostname. After F19 it was a generic one. > > > Actual results: > > DHCP (DSL Router box) inserts a generic hostname. > > So I guess the router is dhcp server in this case and your Fedora machine is > dhcp client, right ? Yes. If the problem is in what hostname does the router send > (insert ?) then I can't do anything with it, can I ? > > > Additional info: > > hostnamectl updates all versions of the hostname, and the DHCP server shows > > the correct hostname. > > I don't get this, sorry. Can you perhaps re-formulate it ? After seeing that my hostname was flubbed in the DSL Router, I used hostnamectl on the F19 machine to reset (completely set?) the hostname. After the next DHCP request, the hostname in the DSL Router was set correctly.
The description is perfect now, thanks :-) (In reply to Oliver Sampson from comment #3) > After seeing that my hostname was flubbed in the DSL Router, I used > hostnamectl on the F19 machine to reset (completely set?) the hostname. > After the next DHCP request, the hostname in the DSL Router was set > correctly. So it looks like that the F17->F19 upgrade either somehow eviscerated the hostname from configuration file(s) (/etc/sysconfig/network, /etc/hostname) or NetworkManager (NM) was unable to get it from them and pass it to dhclient or something like that. I remember that something similar was bug #875085 about, so let's try to pass this to NM, hopefully NM guys have seen something like that previously. Oliver, please confirm that you use NetworkManager.
I use NetworkManager.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.