wily-desktop-amd64-smoke-lvm is failing

[Iain Lane]

See

  https://jenkins.qa.ubuntu.com/view/wily/view/Smoke%20Testing/job/wily-desktop-amd64-smoke-lvm/

this job hasn't passed so far in wily.

Can you help to investigate what's going on? I can't read the output well enough to tell what's going on (or it doesn't say). Is it running the actual test scripts? They seem to be lp:ubuntu-test-cases/server/testsuites/lvm/test_*/test.py

After we've got it fixed, can we please hook this up to image promotion (pending to current)? Currently https://jenkins.qa.ubuntu.com/view/wily/view/Smoke%20Testing/job/wily-desktop-amd64-smoke-default/ is green despite lvm being red.

[Iain Lane (laney)]

psivaa, assigning to you but feel free to punt if you're not the person to look at this

[Para Siva (psivaa)]

Hi Laney,
Thanks for the report, i've had a look at it and see that it's similar to https://bugs.launchpad.net/ubuntu-test-cases/+bug/1443999 on the server iso testing.

Basically these bugs needs changes to the preseed and the post installation tests accordingly in https://code.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/desktop. I offered https://code.launchpad.net/~psivaa/ubuntu-test-cases/lvm-grub-preseed-fix for that server bug, which is again not complete and for a full fix this needs further investigation on the testing side, which I'm afraid I can not justify spending time on. But I guess, the MP would give you an idea where the issue actually is. I'd be more than happy to run the test if you'd be able to make changes to the preseed and/or to the test cases though.

Assigning the bug to you again, since infrastructure has no problem running these tests and it's not an issue with utah.

[Mathieu Trudel-Lapierre (cyphermox)]

I don't think the preseed is to blame for this: the system successfully boots after install and is in the process of installing some random packages from utah configs before it reaches the lvm tests.

What it looks to me is like an error in the lvm test itself which fails because the mount output is now different than how it was when the test was written. The test expects the first line in the output of mount to start with '/dev/mapper' [1]. It no longer appears to be the case on wily desktop or server:

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=4061376k,nr_inodes=1015344,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=815696k,mode=755)
/dev/mapper/ubuntu--vg-root on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
[...]

I will boot a few Trusty VMs to compare, and if the mount command behaves the same there, I'll update the test.

[1] http://bazaar.launchpad.net/~ubuntu-server-dev/utah/server-tests-quantal/view/head:/testsuites/lvm/test_root_mount/test.py

[Mathieu Trudel-Lapierre (cyphermox)]

Filed a merge request with a proposed fix which won't break the Trusty tests:

https://code.launchpad.net/~mathieu-tl/utah/server-tests-lvm/+merge/264993

[Para Siva (psivaa)]

JFYI: with the fix merged to lp:ubuntu-test-cases/server, the desktop lvm tests are passing.

[Iain Lane (laney)]

Well done cyphermox - now can we make sure that this test blocks pending->current promotion please? It wasn't before (i.e. it wasn't affecting the status of this group https://jenkins.qa.ubuntu.com/view/wily/view/Smoke%20Testing/job/wily-desktop-amd64-smoke-default/)