This bug was fixed in the package cloud-init -
0.7.9-233-ge586fe35-0ubuntu1~16.04.2
---
cloud-init (0.7.9-233-ge586fe35-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium
* cherry-pick a2f8ce9c: Do not provide systemd-fsck drop-in which
could cause systemd ordering loops (LP: #1
This bug was fixed in the package cloud-init -
0.7.9-233-ge586fe35-0ubuntu1~17.04.2
---
cloud-init (0.7.9-233-ge586fe35-0ubuntu1~17.04.2) zesty; urgency=medium
* cherry-pick a2f8ce9c: Do not provide systemd-fsck drop-in which
could cause systemd ordering cycles (LP: #1717477).
## launch instance on OpenStack
$ cat /etc/cloud/build.info
build_name: server
serial: 20170922
$ git clone http://git.launchpad.net/~smoser/cloud-init/+git/sru-infy
$ sudo apt-get update -q && sudo apt-get install -q cloud-init
cloud-init is already the newest version (0.7.9-233-ge586fe35-0ubun
## launched instance on Openstack
$ cat /etc/cloud/build.info
build_name: server
serial: 20170929
$ git clone http://git.launchpad.net/~smoser/cloud-init/+git/sru-info
$ sudo apt-get update -q && sudo apt-get install -q cloud-init
..
cloud-init is already the newest version (0.7.9-233-ge586fe35-0
This bug is believed to be fixed in cloud-init in 17.1. If this is still
a problem for you, please make a comment and set the state back to New
Thank you.
** Changed in: cloud-init
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Hello thermoman, or anyone else affected,
Accepted cloud-init into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-233-ge586fe35-0ubuntu1~17.04.2 in a few hours, and then in
the -proposed repository.
Please help us by testing t
Since this basically re-introduces LP: #1691489, we need to remember to
revert the 'Fix Released' fields for each series in that bug once this
goes out to -updates.
** Changed in: cloud-init (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed-xenial
--
This bug was fixed in the package cloud-init - 0.7.9-280-ge626966e-
0ubuntu1
---
cloud-init (0.7.9-280-ge626966e-0ubuntu1) artful; urgency=medium
* debian/rules: install rsyslog file with 0644 mode instead of 0755.
* debian/rules, debian/apport-launcher.py: add an apport hook. (LP
** Changed in: cloud-init (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu Zesty)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu Artful)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu Xenial)
Assi
** Description changed:
+ http://pad.lv/1717477
+ https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1717477
+
+ === Begin SRU Template ===
+ [Impact]
+ Cloud-init's inclusion of a systemd drop-in file
+ /lib/systemd/system/systemd-fsck@.service.d/cloud-init.conf
+ Caused a regression on
** Merge proposal linked:
https://code.launchpad.net/~rbalint/cloud-init/+git/cloud-init/+merge/330842
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717477
Title:
cloud-init generates ordering c
I suggest reverting the commit causing the regression and fixing LP:
#1691489 in an other way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717477
Title:
cloud-init generates ordering cycle via Af
** Attachment added: "journalctl -o short-precise after"
https://bugs.launchpad.net/cloud-init/+bug/1717477/+attachment/4950748/+files/journal-short-precise-after.txt
** Description changed:
We're running several machines with
- cloud-init_0.7.9-153-g16a7302f-0ubuntu1~16.04.2
+ cloud
13 matches
Mail list logo
