Overview
Request 657957 superseded
- Created by ganghe
- In state superseded
- Superseded by 665788
- Open review for factory-staging
Request History
ganghe created request
licensedigger accepted review
ok
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
staging-bot set openSUSE:Factory:Staging:E as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:E"
staging-bot accepted review
Picked openSUSE:Factory:Staging:E
jengelh accepted review
repo-checker accepted review
cycle and install check passed
dimstar_suse accepted review
Removing from openSUSE:Factory:Staging:E, re-evaluation needed
dimstar_suse approved review
Removing from openSUSE:Factory:Staging:E, re-evaluation needed
dimstar_suse added factory-staging as a reviewer
Requesting new staging review
dimstar_suse superseded request
superseded by 665788
This might be the cause for https://openqa.opensuse.org/tests/817604#step/await_install/21
Hello Guys,
Please help to review this request, which includes some useful patches to handle lvm2 ontop md related problems.
Thanks Gang
This will be in the staging process like any other package - the first attempts revealed it possibly breaking some of the openQA tests; after removing lvm2 from the stagnig project the test started passing again, which implies that the assumption was correct.
As such: as long as the tests won't pass, this package won't be able to be accepted
The failure can be observed in
https://openqa.opensuse.org/tests/817604#step/await_install/21
This does only happen in the more complex scenarios we have, like the test mentioned above, which install the system on a cryptlvm partition.
Checking the various log files, the system seems to be stalling while running
lvm vgs --noheadings -o pv_name system
(which in turn is executed by dracut)I just wonder if the last lvm2 packages did the similar testings and encountered this problem?
It did have the same testing - without the issue.
The issue only appeared in the staging project where this request was added; all other stagings/products undergo the same test suite