On Wed, May 05, 2021 at 10:03:29AM +0100, Richard W.M. Jones wrote:
> On Wed, May 05, 2021 at 09:41:48AM +0100, Richard W.M. Jones wrote:
> > 
> > No idea what particular component / update caused that though,
> > or even how to find out.
> 
> So it started with:
> 
> localhost.localdomain systemd-hostnamed[1796302]: Hostname set to 
> <localhost.localdomain> (static)
> 
> but this seems uncorrelated with any package installation or removal.
> After this systemd and NetworkManager appear to be battling with each
> other to set the hostname.  I have hundreds of messages like this:
> 
> May 04 13:52:08 localhost.localdomain NetworkManager[1503]: <info>  
> [1620132728.1664] policy: set-hostname: set hostname to 'pick' (from DHCPv4)
> May 04 13:52:08 localhost.localdomain systemd[1]: Starting Hostname Service...
> May 04 13:52:08 localhost.localdomain systemd[1]: Started Hostname Service.
> May 04 13:52:08 localhost.localdomain systemd-hostnamed[4074869]: Hostname 
> set to <localhost.localdomain> (static)
> ...
> May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info>  
> [1620132767.0935] policy: set-hostname: current hostname was changed outside 
> NetworkManager: 'localhost.localdomain'
> May 04 13:52:47 localhost.localdomain NetworkManager[1503]: <info>  
> [1620132767.0938] policy: set-hostname: set hostname to 'pick' (from DHCPv4)
> 
> Setting the hostname now through hostnamectl hasn't calmed things
> down, now they're battling to set the hostname to 'pick' (NM) or
> 'pick.home.annexia.org' (systemd).
> 
> Is this a bug?  What component would it be filed against?

I assume you had 'localhost.localdomain' in /etc/hostname, and now you have 
'pick.home.annexia.org'
after the call to 'hostnamectl set-hostname'. This sounds like a bug in NM 
then, because
the static configuration in /etc/ should take precedence, so NM shouldn't set 
the hostname
at all.

If it's not too much trouble, could you attach the output from
'busctl introspect org.freedesktop.hostname1 /org/freedesktop/hostname1 
org.freedesktop.hostname1',
ideally without NM running, so we know what hostnamed thinks on its own?

Zbyszek
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to