Activity log for bug #1691517

Date Who What changed Old value New value Message
2017-05-17 17:42:47 Joshua Powers bug added bug
2017-05-17 17:44:28 Joshua Powers description 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 --asumeyes python-pip yum install --assumeyes git python-pip file e2fsprogs pip install setuptools tox virtualenv contextlib2 httpretty mock nose pep8 unittest2 git clone https://git.launchpad.net/cloud-init cd cloud-init tox 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 --asumeyes python-pip yum install --assumeyes git python-pip file e2fsprogs pip install setuptools tox virtualenv contextlib2 httpretty mock nose pep8 unittest2 git clone https://git.launchpad.net/cloud-init cd cloud-init nosetests tests/unittests
2017-05-17 17:49:50 Joshua Powers description 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 --asumeyes python-pip yum install --assumeyes git python-pip file e2fsprogs pip install setuptools tox virtualenv contextlib2 httpretty mock nose pep8 unittest2 git clone https://git.launchpad.net/cloud-init cd cloud-init nosetests tests/unittests 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
2017-05-17 20:36:06 Scott Moser cloud-init: status New Confirmed
2017-05-17 20:36:09 Scott Moser cloud-init: importance Undecided Medium
2017-05-17 20:36:19 Scott Moser cloud-init: assignee Joshua Powers (powersj)
2017-05-17 20:36:29 Scott Moser merge proposal linked https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/324201
2017-05-17 20:37:12 Scott Moser cloud-init: status Confirmed Fix Committed
2017-05-26 20:32:35 Scott Moser bug task added cloud-init (Ubuntu)
2017-05-26 20:32:47 Scott Moser cloud-init (Ubuntu): status New Fix Released
2017-05-26 20:32:53 Scott Moser cloud-init (Ubuntu): importance Undecided Medium
2017-05-26 20:33:13 Scott Moser nominated for series Ubuntu Zesty
2017-05-26 20:33:13 Scott Moser bug task added cloud-init (Ubuntu Zesty)
2017-05-26 20:33:13 Scott Moser nominated for series Ubuntu Yakkety
2017-05-26 20:33:13 Scott Moser bug task added cloud-init (Ubuntu Yakkety)
2017-05-26 20:33:13 Scott Moser nominated for series Ubuntu Xenial
2017-05-26 20:33:13 Scott Moser bug task added cloud-init (Ubuntu Xenial)
2017-05-26 20:37:00 Scott Moser cloud-init (Ubuntu Xenial): status New Confirmed
2017-05-26 20:37:03 Scott Moser cloud-init (Ubuntu Xenial): importance Undecided Medium
2017-05-26 20:37:06 Scott Moser cloud-init (Ubuntu Zesty): importance Undecided Medium
2017-05-26 20:37:09 Scott Moser cloud-init (Ubuntu Yakkety): importance Undecided Medium
2017-05-26 20:37:11 Scott Moser cloud-init (Ubuntu Zesty): status New Confirmed
2017-05-26 20:37:14 Scott Moser cloud-init (Ubuntu Yakkety): status New Confirmed
2017-06-02 17:49:28 Scott Moser description 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 http://pad.lv/1691517 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1691517 === 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
2017-06-02 18:56:20 Scott Moser description http://pad.lv/1691517 https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1691517 === 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 === 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
2017-06-13 18:08:02 Brian Murray cloud-init (Ubuntu Zesty): status Confirmed Fix Committed
2017-06-13 18:08:05 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2017-06-13 18:08:10 Brian Murray bug added subscriber SRU Verification
2017-06-13 18:08:14 Brian Murray tags verification-needed
2017-06-13 18:55:27 Brian Murray cloud-init (Ubuntu Yakkety): status Confirmed Fix Committed
2017-06-13 19:08:57 Brian Murray cloud-init (Ubuntu Xenial): status Confirmed Fix Committed
2017-06-14 01:51:51 Chad Smith tags verification-needed verification-done-xenial verification-done-yakkety verification-done-zesty
2017-06-27 15:51:34 Launchpad Janitor cloud-init (Ubuntu Zesty): status Fix Committed Fix Released
2017-06-27 15:52:46 Steve Langasek removed subscriber Ubuntu Stable Release Updates Team
2017-06-27 15:54:02 Launchpad Janitor cloud-init (Ubuntu Yakkety): status Fix Committed Fix Released
2017-06-27 15:54:45 Launchpad Janitor cloud-init (Ubuntu Xenial): status Fix Committed Fix Released
2017-07-27 22:52:28 Joshua Powers cloud-init: assignee Joshua Powers (powersj)
2017-09-23 02:32:45 Scott Moser cloud-init: status Fix Committed Fix Released
2023-05-11 01:52:48 James Falcon bug watch added https://github.com/canonical/cloud-init/issues/2893