New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unittests blkid command fails on slave s390x #2749
Comments
Launchpad user Joshua Powers(powersj) wrote on 2017-04-11T15:41:17.197550+00:00 Fixed by modifying the jenkins env. path to include /home/jenkins/bin:/home/jenkins/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin:/snap/bin |
Launchpad user Steve Langasek(vorlon) wrote on 2017-05-08T19:04:21.634468+00:00 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 this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Steve Langasek(vorlon) wrote on 2017-05-11T20:29:44.969082+00:00 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 this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Steve Langasek(vorlon) wrote on 2017-05-11T20:36:43.415458+00:00 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 new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! |
Launchpad user Chad Smith(chad.smith) wrote on 2017-05-11T21:07:22.940210+00:00 Validated no /sbin/blkid leaks from altcloud unit tests in xenial: $ name=test-proposed None reportedroot@test-proposed:~/cloud-init# /sbin/blkid |
Launchpad user Chad Smith(chad.smith) wrote on 2017-05-12T19:46:25.475830+00:00 Verified yakkety and zesty: reating proposed-test no LEAKED calls reported. Checking that blkid was properly hijackedroot@proposed-test: no LEAKED calls reported. Checking that blkid was properly hijackedroot@proposed-test: |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-05-17T02:58:17.479191+00:00 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
-- Scott Moser smoser@ubuntu.com Thu, 27 Apr 2017 12:51:04 -0400 |
Launchpad user Chris Halse Rogers(raof) wrote on 2017-05-17T02:58:43.613609+00:00 The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-05-17T03:07:38.254895+00:00 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
-- Scott Moser smoser@ubuntu.com Thu, 27 Apr 2017 13:38:40 -0400 |
Launchpad user Launchpad Janitor(janitor) wrote on 2017-05-17T03:14:07.523948+00:00 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
-- Scott Moser smoser@ubuntu.com Thu, 27 Apr 2017 15:09:31 -0400 |
Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:14:12.056494+00:00 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. |
This bug was originally filed in Launchpad as LP: #1636531
Launchpad details
Launchpad user Joshua Powers(powersj) wrote on 2016-10-25T14:40:14.712344+00:00
=== Begin SRU Template ===
[Impact]
Unit test updates to avoid leaking blkid calls from tests/unittests/test_datasource/test_altcloud.py.
[Test Case]
wget https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/plain/bin/lxc-proposed-snapshot
chmod 755 lxc-proposed-snapshot
Create fake-blkid.sh
cat fake-blkid.sh
#!/bin/bash
echo "LEAKED BLKID CALL"
name=proposed-test
for release in xenial yakkety zesty; do
ref=$release-proposed;
./lxc-proposed-snapshot --proposed --publish $release $ref;
lxc init $ref $name;
lxc start $name;
sleep 10;
lxc exec $name -- mv /sbin/blkid /sbin/blkid.orig;
chmod 755 fake-blkid.sh;
lxc file push fake-blkid.sh $name/sbin/blkid;
lxc exec $name -- git clone -b ubuntu/xenial https://git.launchpad.net/cloud-init;
lxc exec $name -- sudo apt install tox -y;
tox -e py27 tests/unittests/test_datasource/test_altcloud.py | grep 'LEAKED BLKID';
done
[Regression Potential]
None. Unit test changes only
[Other Info]
=== End SRU Template ===
Running the unittests on our slave s390x system, the blkid command fails. Running it manually returns the following:
jenkins@s1lp04:
$ blkid -tLABEL=CDROM -odevice$ echo $?jenkins@s1lp04:
2
jenkins@s1lp04:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
dasda 94:0 0 20.6G 0 disk
|-dasda1 94:1 0 19.7G 0 part /
`-dasda2 94:2 0 953.5M 0 part [SWAP]
Full run output:
https://jenkins.ubuntu.com/server/job/cloud-init-ci/nodes=s390x/53/console
The text was updated successfully, but these errors were encountered: