DavidePrincipi
commented
1 month ago Test case
Prepare cloud-init configuration files.
mkdir cloud-init
cd cloud-init
echo "instance-id: $(uuidgen)" > meta-data
cat - >user-data <<'EOF'
#cloud-config
hostname: ns8-1
manage_etc_hosts: true
fqdn: ns8-1.ci.test
#ssh_authorized_keys:
# - "ssh-rsa REPLACE WITH YOUR PUBLIC KEY"
EOF
# generate the ISO file
rm -f cloud-init.iso
genisoimage -output cloud-init.iso -volid cidata -joliet -rock user-data meta-dataFrom VM hypervisor, select the cloud-init.iso image as CD-ROM disk image. Boot the NS8 .qcow2 image with cloud-init CD-ROM image.
When boot completes access NS8 console and run this command:
sed -i.orig -r '/-\s*update_etc_hosts/ d ; /-\s*update_hostname/ d' /etc/cloud/cloud.cfgComplete NS8 setup with a create-cluster.
Power off the VM.
Modify user-data with a different host name, and generate the ISO again.
Start the VM with the new ISO.
Check that /etc/hostname, hostname -f, /etc/hosts didn't change.
Verify cloud-init activity in /var/log/cloud-init.log. For example:
grep -E 'update_hostname|/etc/hosts' /var/log/cloud-init.log
Some cloud providers configure Cloud-init to overwrite
/etc/hostsat every boot. When the leader node is rebooted it is shown offline.Issue origin and workaround
NS8 actions
create-cluster,join-cluster, andpromote-nodemodify/etc/hosts. However those changes can be overwritten during reboot if Cloud-init is configured to expand a template for/etc/hosts.Manually add
/etc/hostsentries to workaround the problem:Steps to reproduce
/etc/hosts.Expected behavior
After rebooting the node is online.
Actual behavior
The node remains offline.
Components
See also
Cloud init docs:
Discussions:
Thanks to @nrauso @lucagasparini