Hostname changes not persistent

Bug #1780017 reported by Sanjeev Gopal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Only applicable to Ubuntu 18.04. Changes made via "hostnamectl set-hostname" are not persistent - reverts after a reboot.

See results details below:

# hostnamectl status
   Static hostname: xxxlxd903
         Icon name: computer-vm
           Chassis: vm
        Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
           Boot ID: 463b63d5bc3942a9abacdf34054644b4
    Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
            Kernel: Linux 4.15.0-24-generic
      Architecture: x86-64

# hostnamectl set-hostname xxxlxd903x

# hostnamectl status
   Static hostname: xxxlxd903x
         Icon name: computer-vm
           Chassis: vm
        Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
           Boot ID: 463b63d5bc3942a9abacdf34054644b4
    Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
            Kernel: Linux 4.15.0-24-generic
      Architecture: x86-64

# shutdown -r now

...

$ hostnamectl status
   Static hostname: xxxlxd903
         Icon name: computer-vm
           Chassis: vm
        Machine ID: ee8de2e6dffc42f9985e4e0c5350bda2
           Boot ID: ffb13e8eb23f40029a7685178229c2bb
    Virtualization: vmware
  Operating System: Ubuntu 18.04 LTS
            Kernel: Linux 4.15.0-24-generic
      Architecture: x86-64

Note: System is fully patched now. Was happening earlier too - with a fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Jul 4 12:52:19 2018
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=UUID=72a62618-633d-11e8-9a7c-005056911d79 ro maybe-ubiquity
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/05/2016
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/05/2016:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
modified.conffile..etc.systemd.timesyncd.conf: [modified]
mtime.conffile..etc.systemd.timesyncd.conf: 2018-05-29T20:59:09.725641

Revision history for this message
Sanjeev Gopal (sanjeevgopal) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.