Vivid raid1 smoke test fail to mount root partition
Bug #1443988 reported by
Diogo Matsubara
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Test Cases |
New
|
Undecided
|
Unassigned |
Bug Description
Vivid's raid1 smoke test[1] fails with the following error:
FAIL: testRootMount (__main_
---
Traceback (most recent call last):
File "test.py", line 39, in testRootMount
"/ partition not in raid device")
AssertionError: / partition not in raid device
[1] http://
To post a comment you must log in.
I ran into a weird issue debugging this test failure. I added the following change http:// pastebin. ubuntu. com/10961577/ to the test case, so I could see what the `df -h` output was, then kicked another test run here: http:// d-jenkins. ubuntu- ci:8080/ view/Vivid/ view/Smoke% 20Testing/ job/vivid- server- amd64-smoke- raid1/140/ artifact/ utah-36792- vivid-server- amd64_raid1. run_2015- 05-01_11- 05-09.yaml/ *view*/
The output from my debug command shows the root file systems is mounted to /dev/md0 which is what the test case expects but when the subsequent `df -h /` command runs the output returned is different and shows the device by uuid: /dev/disk/ by-uuid/ 28e0ef45- c224-40b5- a0e7-49fde0bb55 28 which obviously won't match the test expectation. So what is confusing is why I get different outputs from df depending on what parameters I pass to the command.