Failed to start Initial cloud-init job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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-
Candidate: 21.1-19-
Version table:
*** 21.1-19-
500 http://
100 /var/lib/
0.7.7~bzr1212-
500 http://
$ systemctl status cloud-init
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Fri 2021-04-16 04:13:33 CEST; 4min 3s ago
Process: 1037 ExecStart=
Main PID: 1037 (code=exited, status=1/FAILURE)
Apr 16 04:13:33 crow16 cloud-init[1037]: File "/usr/lib/
Apr 16 04:13:33 crow16 cloud-init[1037]: self._store_
Apr 16 04:13:33 crow16 cloud-init[1037]: File "/usr/lib/
Apr 16 04:13:33 crow16 cloud-init[1037]: return self.vendordata
Apr 16 04:13:33 crow16 cloud-init[1037]: AttributeError: 'DataSourceDigi
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.
This issue is being tracked upstream at https:/ /bugs.launchpad .net/cloud- init/+bug/ 1922739