Bug 22413 - NM can't set hostname from DHCP because of systemd hardening status
Summary: NM can't set hostname from DHCP because of systemd hardening status
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-17 20:15 CET by Frank Griffin
Modified: 2019-02-19 16:59 CET (History)
3 users (show)

See Also:
Source RPM: systemd
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frank Griffin 2018-01-17 20:15:56 CET 
When activating a DHCP connection, NM receives a hostname from the DHCP server and tries to set it but fails:

Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4659] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4864] dhcp4 (enp2s0):   address 192.168.3.102
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   plen 24
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   expires in 21600 seconds
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   nameserver '192.168.3.101'
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   domain search 'griffin.treehouse.com'
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   domain search 'treehouse.local'
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   domain name 'griffin.treehouse.com'
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   hostname 'ftgme2'
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4865] dhcp4 (enp2s0):   gateway 192.168.3.100
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4867] dhcp4 (enp2s0): state changed unknown -> bound
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4964] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4987] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4993] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.4995] manager: NetworkManager state is now CONNECTED_LOCAL
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.5254] manager: NetworkManager state is now CONNECTED_SITE
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.5255] policy: set 'Wired connection 1' (enp2s0) as default for IPv4 routing and DNS
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.5257] policy: set-hostname: set hostname to 'ftgme2' (from DHCPv4)
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <warn>  [1516215628.5258] policy: set-hostname: couldn't set the system hostname to 'ftgme2': (1) Operation not permitted
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <warn>  [1516215628.5258] policy: set-hostname: you should use hostnamed when systemd hardening is in effect!
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.5259] dns-mgr: Writing DNS information to /sbin/resolvconf
Jan 17 14:00:28 localhost.localdomain NetworkManager[15003]: <info>  [1516215628.6328] device (enp2s0): Activation: successful, device activated.
J
Marja Van Waes 2018-01-18 07:57:31 CET

CC: (none) => mageia, marja11, ngompa13
Assignee: bugsquad => basesystem

Comment 1 Frank Griffin 2019-02-19 16:59:11 CET 
No longer happening in current cauldron.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.