Bug 1320145 - NM does not set hostname
Summary: NM does not set hostname
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-22 12:10 UTC by Vít Ondruch
Modified: 2016-10-29 11:44 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-29 11:44:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vít Ondruch 2016-03-22 12:10:54 UTC
Description of problem:
$ hostname
localhost

$ LANG=C.UTF-8 journalctl -b -u NetworkManager
... snip ...
Mar 22 13:02:12 localhost NetworkManager[1203]: <info>  [1458648132.396400] Setting system hostname to 'unused-4-232.brq.redhat.com' (from address lookup)
Mar 22 13:02:12 localhost NetworkManager[1203]: <warn>  [1458648132.396488] couldn't set the system hostname to 'unused-4-232.brq.redhat.com': (1) Operace není povolena
Mar 22 13:02:12 localhost NetworkManager[1203]: <warn>  [1458648132.396500] You should use hostnamed when systemd hardening is in effect!


Version-Release number of selected component (if applicable):
$ rpm -q NetworkManager
NetworkManager-1.2.0-0.6.beta2.fc25.x86_64


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Beniamino Galvani 2016-03-25 15:05:58 UTC
Please upgrade to NetworkManager-1.2.0-0.7.beta2.fc25.x86_64, this should be fixed now.

Comment 2 Vít Ondruch 2016-03-30 13:57:26 UTC
Thx, it works now with:

$ rpm -q NetworkManager
NetworkManager-1.2.0-0.8.beta3.fc25.x86_64

Comment 3 Jan Kurik 2016-07-26 04:35:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.


Note You need to log in before you can comment on or make changes to this bug.