action #166175
open
[qe-core][jeos][rpi] test fails in firstrun
Added by zluo 3 months ago.
Updated 15 days ago.
Category:
Bugs in existing tests
- Assignee changed from mloviska to zluo
- Assignee changed from zluo to pherranz
@pherranz can you help to answer the question, ist this hdd image related issue #164144?
We didn't see firstrun was broken before at useradd, thanks!
- Assignee changed from pherranz to zluo
Well the image creation has remained the same AFAIK, I've just enabled the 15-SP7 tests, not changed the test itself. As I can see, the firstrun test is already being ran in the image creation, although the creation of the bernhard user is already done. Maybe it's redundant to run firstrun again?
for record:
it works for sles 15 sp6. So this is broken now.
We had an issue with partition label 'dos', that broke also some tests (I cannot recall where, but I think it is another related issue with kiwi template change?). And there is indeed another change in workflow for Selfinstaller for Micro 6.1.
A new user will be created extra for allowing to access to cockpit WebUI. We can compare with an issue on Tumbleweed: https://progress.opensuse.org/issues/165800
- Tags set to bugbusters
- Target version set to QE-Core: Ready
- Assignee changed from zluo to rfan1
- Status changed from New to In Progress
I would suggest to change the schedule.. instead of firstrun, execute boot_to_desktop or similar..
- Status changed from In Progress to Workable
- Assignee deleted (
rfan1)
@szarate Please help to assign this ticket to someone who is enable or can solve this issue. This is blocking further testing, thanks!
This is an autogenerated message for openQA integration by the openqa_review script:
This bug is still referenced in a failing openQA test: jeos-realhw-RPi@RPi3B
https://openqa.suse.de/tests/15822912#step/firstrun/1
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Also available in: Atom
PDF