yahoo-eng-team team mailing list archive

[James Falcon <1928603@xxxxxxxxxxxxxxxxxx>]

Yes, only enabling the one service would explain why cloud-init isn't
fully running. If you enable the others, cloud-init should work as
expected.

Is there a reason you can't use the cloud image as your base in packer?
Then you shouldn't have to change anything about cloud-init at all.

Since it seems this came down to a misunderstanding of how cloud-init
services works, I'm going to close this as invalid. If there's still
something about this you think is wrong in cloud-init, feel free to
change the status back to 'New'.

** Changed in: cloud-init
       Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1928603

Title:
  Init modules run, but nothing else on Opensuse 15.2 with
  vmwareguesttools

Status in cloud-init:
  Invalid

Bug description:
  Using OpenSUSE 15.2, with cloudinit + vmware guest tools nothing past
  the init stage runs and when it does, it seems to silently fail.

  VMware vcenter 7.2 with ESXi 6.3u hosts
  OpenSUSE as the cloud-init target
  /usr/bin/cloud-init 20.2-lp152.5.21.1
  Vmware guest tools installed with https://raw.githubusercontent.com/vmware/cloud-init-vmware-guestinfo/master/install.sh

  
  Cloud-init seems to think its successful but looking at the configs/logs I don't ever see anything past init run.
  Starting stage: init-network
  |`->restored from cache with run check: DataSourceVMwareGuestInfo @03.21500s +00.00500s
  .....
  Finished stage: (init-network) 01.36900 seconds

  Total Time: 1.55000 seconds

  1 boot records analyzed

  I can see my runcmd in /var/lib/cloud output as I expect, and when I run cloud-init modules it will show as run in the modules
  Starting stage: modules-config
  |`->config-locale ran successfully @307.80200s +00.00100s
  |`->config-set-passwords ran successfully @307.80400s +00.03100s
  |`->config-zypper-add-repo ran successfully @307.83600s +00.00100s
  |`->config-ntp ran successfully @307.83700s +00.00100s
  |`->config-timezone ran successfully @307.83800s +00.00100s
  |`->config-disable-ec2-metadata ran successfully @307.83900s +00.00000s
  |`->config-runcmd ran successfully @307.83900s +00.00700s
  Finished stage: (modules-config) 00.05600 seconds

  
  But I don't even see evidence my first debug line is even running at beyond what is seen debug side. 
  - [ touch, /var/log/work.log ]

  I see this debug output in the logs, but its not clear as to what happened.
  2021-05-16 19:51:54,553 - stages.py[DEBUG]: Running module runcmd (<module 'cloudinit.config.cc_runcmd' from '/usr/lib/python3.6/site-packages/cloudinit/config/cc_runcmd.py'>) with frequency once-per-instance
  2021-05-16 19:51:54,553 - handlers.py[DEBUG]: start: modules-config/config-runcmd: running config-runcmd with frequency once-per-instance
  2021-05-16 19:51:54,554 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/k3s-suse/sem/config_runcmd - wb: [644] 24 bytes
  2021-05-16 19:51:54,554 - helpers.py[DEBUG]: Running config-runcmd using lock (<FileLock using file '/var/lib/cloud/instances/k3s-suse/sem/config_runcmd'>)
  2021-05-16 19:51:54,559 - util.py[DEBUG]: Shellified 4 commands.
  2021-05-16 19:51:54,559 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/k3s-suse/scripts/runcmd - wb: [700] 156 bytes
  2021-05-16 19:51:54,560 - handlers.py[DEBUG]: finish: modules-config/config-runcmd: SUCCESS: config-runcmd ran successfully
  2021-05-16 19:51:54,560 - main.py[DEBUG]: Ran 7 modules with 0 failures

  Can confirm its absolutely seeing the args I'm trying to pass, this is me dropping from 4 commands to 1
  2021-05-16 19:59:52,642 - util.py[DEBUG]: Cloud-init v. 20.2-lp152.5.21.1 running 'single' at Sun, 16 May 2021 19:59:52 +0000. Up 82.40 seconds.
  2021-05-16 19:59:52,645 - stages.py[DEBUG]: Using distro class <class 'cloudinit.distros.opensuse.Distro'>
  2021-05-16 19:59:52,645 - stages.py[DEBUG]: Running module runcmd (<module 'cloudinit.config.cc_runcmd' from '/usr/lib/python3.6/site-packages/cloudinit/config/cc_runcmd.py'>) with frequency once-per-instance
  2021-05-16 19:59:52,646 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/k3s-suse/sem/config_runcmd - wb: [644] 25 bytes
  2021-05-16 19:59:52,646 - helpers.py[DEBUG]: Running config-runcmd using lock (<FileLock using file '/var/lib/cloud/instances/k3s-suse/sem/config_runcmd'>)
  2021-05-16 19:59:52,651 - util.py[DEBUG]: Shellified 1 commands.
  2021-05-16 19:59:52,651 - util.py[DEBUG]: Writing to /var/lib/cloud/instances/k3s-suse/scripts/runcmd - wb: [700] 37 bytes
  2021-05-16 19:59:52,652 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
  2021-05-16 19:59:52,652 - util.py[DEBUG]: Read 13 bytes from /proc/uptime

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1928603/+subscriptions