cloud-init not initing...

[david garvey]

I am seeing systemd reset here.
[root@sdo-img-rhel79-test-apr30 cloud-init_debug]# dmesg | grep -i term
[ 133.522528] systemd-journald[103]: Received SIGTERM from PID 1 (systemd).
[root@sdo-img-rhel79-test-apr30 cloud-init_debug]# dmesg > dmesg.txt
[root@sdo-img-rhel79-test-apr30 cloud-init_debug]#

[Brett Holman (holmanb)]

Hi David,

Thanks for reporting.

Can you please clarify what you expected to happen vs what happened and how this relates to cloud-init?

The bug description shows systemd-journald received a signal from systemd, but I don't understand why this is being reported to cloud-init.

A quick note:

You are running cloud-init v19.4, which is pretty old. Many upstream bugfixes and features have been added that have not been backported to this version.

[david garvey (dgarvey)]

Hi Brett,

This looks like our gcp sdk and or anisble gcp modules might need to be updated. We where able to successfully build a working cloud-init vm using the GCE web Ui and gcloud console. I will update you on our progess.

[david garvey (dgarvey)]

Hi Brett,

I updated our sdk and ansible modules used for create the test vm and it works fine on first boot.

[root@sdo-rhel-test-dave ~]# cloud-init query userdata | grep test_user_data.txt
  - echo "test" > /tmp/test_user_data.txt
[root@sdo-rhel-test-dave ~]# cloud-id
gce
[root@sdo-rhel-test-dave ~]#

root@cloud-sdk:~/infrastructure-ansible# ansible --version
[DEPRECATION WARNING]: Ansible will require Python 3.8 or newer on the controller starting with Ansible 2.12. Current version:
3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]. This feature will be removed from ansible-core in version 2.12. Deprecation
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ansible [core 2.11.11]
  config file = /root/infrastructure-ansible/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.7/dist-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]
  jinja version = 3.1.2
  libyaml = True
root@cloud-sdk:~/infrastructure-ansible# gcloud --version
Google Cloud SDK 384.0.0
alpha 2022.05.02
app-engine-go 1.9.72
app-engine-java 1.9.96
app-engine-python 1.9.100
app-engine-python-extras 1.9.96
beta 2022.05.02
bigtable
bq 2.0.74
bundled-python3-unix 3.8.11
cbt 0.12.0
cloud-datastore-emulator 2.2.0
cloud-firestore-emulator 1.14.3
cloud-spanner-emulator 1.4.2
core 2022.05.02
datalab 20190610
gsutil 5.10
kpt 1.0.0-beta.13
local-extract 1.5.2
pubsub-emulator 0.6.0

[Brett Holman (holmanb)]

dgarvey: Thanks for reporting back. I'm glad you figured it out.

It sounds like this has been resolved. Since I don't think this was an issue with cloud-init, I'm marking it as "Invalid". Please reopen this bug with more details if you believe that further action is required for cloud-init.

Regards,
Brett Holman

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/3972