This bug is undergoing SRU verification for release into Ubuntu xenial, bionic, disco and eoan as part of cloud-init version 19.3.41. The upstream team doesn't have the configuration available to exercise this changeset effectively.
If you get a chance, please verify that this 'fix' works for you using the following procedure:
o install the "proposed" version of cloud-init on an existing Ubuntu vm, run the following on the commandline of your instance:
cat > setup_proposed.sh <<EOF
#/bin/bash
mirror=http://archive.ubuntu.com/ubuntu
echo deb \$mirror \$(lsb_release -sc)-proposed main | tee /etc/apt/sources.list.d/proposed.list
apt-get update -q;
apt-get install -qy cloud-init;
EOF
sudo ./setup_proposed.sh
# To run all of cloud-init fresh on the system
# sudo cloud-init clean --reboot --logs
If you have concerns about this changeset, please comment on the SRU process bug here:
Hello Sam,
This bug is undergoing SRU verification for release into Ubuntu xenial, bionic, disco and eoan as part of cloud-init version 19.3.41. The upstream team doesn't have the configuration available to exercise this changeset effectively.
If you get a chance, please verify that this 'fix' works for you using the following procedure: archive. ubuntu. com/ubuntu sources. list.d/ proposed. list
o install the "proposed" version of cloud-init on an existing Ubuntu vm, run the following on the commandline of your instance:
cat > setup_proposed.sh <<EOF
#/bin/bash
mirror=http://
echo deb \$mirror \$(lsb_release -sc)-proposed main | tee /etc/apt/
apt-get update -q;
apt-get install -qy cloud-init;
EOF
sudo ./setup_proposed.sh
# To run all of cloud-init fresh on the system
# sudo cloud-init clean --reboot --logs
If you have concerns about this changeset, please comment on the SRU process bug here:
https:/ /bugs.launchpad .net/ubuntu/ +source/ cloud-init/ +bug/1854872
Best regards,
The cloud-init team