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: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubu
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~17.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~17.04.1) zesty; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.10.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream snapshot.
This bug was fixed in the package cloud-init -
0.7.9-113-g513e99e0-0ubuntu1~16.04.1
---
cloud-init (0.7.9-113-g513e99e0-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium
* debian/update-grub-legacy-ec2: fix early exit failure no /etc/fstab
file. (LP: #1682160)
* New upstream
Verified yakkety and zesty:
$ for release in yakkety zesty; do ref=$release-proposed; lxc init $ref $name;
lxc start $name; sleep 10; lxc exec $name -- git clone -b ubuntu/xenial
https://git.launchpad.net/cloud-init; lxc exec $name -- apt install python2.7
tox -y; lxc exec $name -- mv /sbin/blki
Validated no /sbin/blkid leaks from altcloud unit tests in xenial:
$ name=test-proposed
$ release=xenial
$ ref=$release-proposed
$ ./lxc-proposed-snapshot --proposed --publish $release $ref
$ lxc init $ref $name
Creating test-proposed
$ lxc exec $name -- git clone -b ubuntu/xenial
https://git.la
Hello Joshua, 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-113-g513e99e0-0ubuntu1~17.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing this
Hello Joshua, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.10.1 in a few hours, and then in
the -proposed repository.
Please help us by testing th
Hello Joshua, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.9-113-g513e99e0-0ubuntu1~16.04.1 in a few hours, and then in
the -proposed repository.
Please help us by testing thi
** Changed in: cloud-init
Status: Invalid => Fix Committed
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636531
Title:
unittests
** Also affects: cloud-init (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ub
** Description changed:
- Running the unittests on our slave s390x system, the blkid command
- fails. Running it manually returns the following:
+ === Begin SRU Template ===
+ [Impact]
+ Unit test updates to avoid leaking blkid calls from
tests/unittests/test_datasource/test_altcloud.py.
+
+ [T
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636531
Title:
unittests blkid command fails on slave s390x
To manage
13 matches
Mail list logo
