http://bugzilla.opensuse.org/show_bug.cgi?id=974661 Bug ID: 974661 Summary: wicked resets host name after wickedd restart Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: johannes.grassler@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Build Identifier: We recently had an issue with one of our Jenkins jobs failing due to the machine's host name reverting to 'linux' after wickedd is restarted (see [0] for details). The machine in question had its hostname set to 'cleanvm.openstacklocal' by cloud-init. At a later point our QA script restarted wickedd and wickedd reverted the hostname to 'linux'. The problem appears to be caused by /etc/wicked/extensions/hostname. When we disabled that script by an `exit 0` at the top wicked no longer reset the host name. Adding some debugging output narrowed the problem down to the `install` operation in /etc/wicked/extensions/hostname. Specifically, wickedd set the hostname to `linux` (found in the hostname section of /var/lib/wicked/lease-eth0-dhcp-ipv4.xml but just putting an arbitrary value in there did not reset the host name to that arbitrary value, so probably the source of truth is somewhere else). [0] https://github.com/SUSE-Cloud/automation/pull/945 Reproducible: Always Steps to Reproduce: 1. Boot a VM with this image: http://download.opensuse.org/repositories/openSUSE:/Leap:/42.1:/Images/image... 2. Set the machine's host name to an arbitrary value (either manually using hostnamectl or through cloud-init) 3. Issue a `systemctl restart wickedd`. After this the machine's run-time host name will change to `linux`. Actual Results: The machine's host name changed to `linux`. Expected Results: The host name should have remained the one originally set by cloud-init and found in /etc/hostname and /proc/sys/kernel/hostname (cleanvm.openstacklocal in the case at hand). -- You are receiving this mail because: You are on the CC list for the bug.