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 Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1691517
Title:
centos7 unit tests fail due to hard coded mkfs.ext4
Status in cloud-init:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Status in cloud-init source package in Yakkety:
Fix Released
Status in cloud-init source package in Zesty:
Fix Released
Bug description:
=== Begin SRU Template ===
[Impact]
Unit tests for cloud-init did not run successfully in a centos environment.
This is really just failure of the unit tests.
The fix was to no longer expect /sbin/mkfs.ext4 but to mock the
checking.
[Test Case]
Test of ubuntu package in centos is non-trivial and/or not useful.
The proposed test case is to just run the trunk tests at the
uploaded git commit in a lxc container (the environment that originally
found the issue).
$ lxc launch images:centos/7 c7
$ sleep 10; # let it boot
$ lxc exec c7 -- /bin/sh -xe <<"EOF"
yum install --assumeyes epel-release
yum install --assumeyes pyserial python-argparse python-cheetah
python-configobj python-jinja2 python-jsonpatch python-oauthlib
python-prettytable python-requests python-six python-pip PyYAML git file
e2fsprogs
pip install contextlib2 httpretty mock nose pep8 unittest2
git clone https://git.launchpad.net/cloud-init
cd cloud-init
git checkout 16a7302f
nosetests tests/unittests
EOF
[Regression Potential]
No runtime regression potential.
Unit test only changes.
[Other Info]
Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=951863c21
=== End SRU Template ===
A recent merge that added a mkfs.ext4 tests has a hard coded location
for the binary of mkfs.ext4. The result is that on centos 7, which has
the command in a different location than Ubuntu, is a failed test:
https://paste.ubuntu.com/24589593/
Steps to reproduce:
lxc launch images:centos/7 c7
lxc exec c7 bash
yum install --assumeyes epel-release
yum install --assumeyes pyserial python-argparse python-cheetah
python-configobj python-jinja2 python-jsonpatch python-oauthlib
python-prettytable python-requests python-six python-pip PyYAML git file
e2fsprogs
pip install contextlib2 httpretty mock nose pep8 unittest2
git clone https://git.launchpad.net/cloud-init
cd cloud-init
nosetests tests/unittests
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1691517/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
