action #41030
[qam] test fails in updates_packagekit_kde - zypper update requires additional install step
0%
Description
Observation¶
openQA test in scenario opensuse-15.0-DVD-Updates-x86_64-install_with_updates_kde@uefi-2G fails in
updates_packagekit_kde
Reproducible¶
Fails since (at least) Build 20180913-1
Expected result¶
Last good: 20180912-4 (or more recent)
Further details¶
Always latest result in this scenario: latest
Related issues
History
#1
Updated by pcervinka over 4 years ago
Updated by Updates contain zypper update, incident 8725. Update will install zypper first, than it tries to install the rest.
Code in updates_available-tray is not designed for this case.
I will try to implement fix.
#2
Updated by okurz over 4 years ago
Updated by Please keep other tickets regarding updates_packagekit_kde in mind: https://progress.opensuse.org/projects/openqatests/issues?utf8=%E2%9C%93&set_filter=1&f%5B%5D=status_id&op%5Bstatus_id%5D=o&f%5B%5D=subject&op%5Bsubject%5D=%7E&v%5Bsubject%5D%5B%5D=updates_packagekit&f%5B%5D=&c%5B%5D=subject&c%5B%5D=project&c%5B%5D=status&c%5B%5D=assigned_to&c%5B%5D=fixed_version&c%5B%5D=is_private&c%5B%5D=due_date&c%5B%5D=relations&group_by=
#3
Updated by pcervinka over 4 years ago
- Subject changed from [qam] test fails in updates_packagekit_kde to [qam] test fails in updates_packagekit_kde - zypper update requires additional install step
#5
Updated by AndreasStieger over 4 years ago
Updated by We had successful runs with this PR merged.
#6
Updated by pcervinka over 4 years ago
- Status changed from In Progress to Feedback
Wait few for more days to see, if there is no side effect. I will also try to recheck soft-failed bugs in updates_packagekit_kde, there seems to be no progress on them. Maybe it is time to revise the code of the test(from the long term point of view).
#7
Updated by pcervinka over 4 years ago
- Related to action #41396: [qam] Revise updates_packagekit_kde added
#8
Updated by pcervinka over 4 years ago
- Status changed from Feedback to Resolved
Seems to be after several ooo runs.
#9
Updated by sebchlad over 4 years ago
Updated by - Project changed from openQA Tests to SUSE QA
- Category deleted (
Bugs in existing tests) - Target version changed from 445 to 457
#10
Updated by okurz over 4 years ago
- Project changed from SUSE QA to openQA Tests
- Category set to Bugs in existing tests
- Target version deleted (
457)
not quite sure why you still do this but moving the tickets into a private subproject will hide it and this makes a problem, especially for "openSUSE only" tickets. Did you consider using maybe the top-level public QA project?
#11
Updated by pcervinka over 4 years ago
To track work in particular team where the work was done.
#12
Updated by okurz over 4 years ago
That's what I assumed but I do not understand how you "track work" which would restrict you to a single project. As I suggested, why not use the top-level public QA project?