Failed to start Initial cloud-init job

[glitsj16]

A recent upgrade of the cloud-init package breaks the service. This happens on a DigitalOcean instance running Ubuntu 16.04 LTS. Downgrading and pinning the cloud-init package keeps things from breaking, but obviously that's only a crude hack.

$ lsb_release -rd
Description: Ubuntu 16.04.7 LTS
Release: 16.04

$ apt-cache policy cloud-init
cloud-init:
Installed: 21.1-19-gbad84ad4-0ubuntu1~16.04.1
Candidate: 21.1-19-gbad84ad4-0ubuntu1~16.04.1
Version table:
*** 21.1-19-gbad84ad4-0ubuntu1~16.04.1 500
    500 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 Packages
    100 /var/lib/dpkg/status
0.7.7~bzr1212-0ubuntu1 500
    500 http://mirrors.digitalocean.com/ubuntu xenial/main amd64 Packages

$ systemctl status cloud-init
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2021-04-16 04:13:33 CEST; 4min 3s ago
Process: 1037 ExecStart=/usr/bin/cloud-init init (code=exited, status=1/FAILURE)
Main PID: 1037 (code=exited, status=1/FAILURE)

Apr 16 04:13:33 crow16 cloud-init[1037]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 371, in update
Apr 16 04:13:33 crow16 cloud-init[1037]: self._store_raw_vendordata(self.datasource.get_vendordata2_raw(),
Apr 16 04:13:33 crow16 cloud-init[1037]: File "/usr/lib/python3/dist-packages/cloudinit/sources/__init__.py", line 506, in get_vendordata2_raw
Apr 16 04:13:33 crow16 cloud-init[1037]: return self.vendordata2_raw
Apr 16 04:13:33 crow16 cloud-init[1037]: AttributeError: 'DataSourceDigitalOcean' object has no attribute 'vendordata2_raw'
Apr 16 04:13:33 crow16 cloud-init[1037]: ------------------------------------------------------------
Apr 16 04:13:33 crow16 systemd[1]: cloud-init.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 04:13:33 crow16 systemd[1]: Failed to start Initial cloud-init job (metadata service crawler).
Apr 16 04:13:33 crow16 systemd[1]: cloud-init.service: Unit entered failed state.
Apr 16 04:13:33 crow16 systemd[1]: cloud-init.service: Failed with result 'exit-code'.

For the record, I see the exact same failure messages when installing the cloud-init package from the official xenial-updates repo.

[James Falcon (falcojr)]

This issue is being tracked upstream at https://bugs.launchpad.net/cloud-init/+bug/1922739