https://github.com/coreos/bugs/issues/2193
On Friday, October 13, 2017 at 2:28:43 PM UTC+8, [email protected] wrote: > > I was trying set the hostname using hostnamectl but it threw following > error. > > *"ip-10-1-1-154 jeeva # hostnamectl set-hostname > k8s-worker-1507708889.ops1.srcclr.com > <http://k8s-worker-1507708889.ops1.srcclr.com>* > *Could not set property: Failed to activate service > 'org.freedesktop.hostname1': timed out"* > > systemd-hostname.service also failed. > > logs -- > *"ct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: > systemd-hostnamed.service: Main process exited, code=exited, > status=226/NAMESPACE* > *Oct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: > Failed to start Hostname Service.* > *Oct 13 04:24:14 ip-10-1-1-154.us-west-2.compute.internal systemd[1]: > systemd-hostnamed.service: Unit entered failed state."* > > > All the systemd files are updated on Oct12th. Our application depends on > the hostname and at the moment I could revert the AWS issued hostname with > ours > > OS - coreos-1520.6.0 > systemd - 234 >
