action #30085
closed[functional][u][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update
Added by AndreasStieger over 6 years ago. Updated about 6 years ago.
0%
Description
Observation¶
openQA test in scenario opensuse-42.3-Updates-x86_64-gnome@64bit-2G fails in
updates_packagekit_gpk
updates_packagekit_gpk
PackageKit does not tell the user that the application needs to be restarted, that is boo#1075260
But if PackageKit does show this dialog (screen tag updates_restart_application), the test would would simply click the OK button.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/tests/update/updates_packagekit_gpk.pm#L56-L58
However this does not seem to restart the packagekit daemon to reload libzypp (org.freedesktop.PackageKit.SuggestDaemonQuit)
Hence the subsequent failure to install a maintenance update that otherwise installs with and updated libzypp/zypper.
The request is to adjust the tests so that the packagekit daemon is restarted in this instance, or some other means to have PackakeKit use the new libzypp.
Reproducible¶
Fails since (at least) Build 20180108-4
Expected result¶
Last good: 20180108-3 (or more recent)
(not good, the issue was uncovered due to the release of a gimp maintenance update exposing this.)
Further details¶
Always latest result in this scenario: latest
Updated by AndreasStieger over 6 years ago
- Status changed from New to Closed
Updated by okurz over 6 years ago
- Status changed from Closed to In Progress
- Assignee set to AndreasStieger
- Priority changed from Normal to High
looks like updates_packagekit_gpk is borked https://openqa.opensuse.org/tests/590665
caused by astieger's change to try to quit packagekit. In xfce it seems the desktop runner is now hidden behind the update applet view
@astieger can you explain (again) why the test should try to meddle with internals of packagekit? IIUC your test code is actually a workaround for https://bugzilla.opensuse.org/show_bug.cgi?id=1075260 so I assume we are missing a record_soft_failure here, correct?
Updated by okurz over 6 years ago
- Has duplicate action #30787: [openSUSE Leap] [functional]test fails in updates_packagekit_gpk - restart computer is required added
Updated by AndreasStieger over 6 years ago
- Status changed from In Progress to Workable
- Assignee changed from AndreasStieger to jorauch
Yes this is a workaround for boo#1075260, also for the fact that a restart of the viewer does not restart PackageKit. Since this is a bug, a soft failure may be reported here.
Updated by okurz over 6 years ago
- Subject changed from test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update to [functional][fast]test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update
- Due date set to 2018-01-30
- Target version set to Milestone 13
In https://openqa.opensuse.org/tests/592767#step/updates_packagekit_gpk/21 it looks like the desktop runner is started and in the mean time the update viewer starts and getting the focus. See the task bar, the desktop runner is still running in the background.
Updated by lnussel over 6 years ago
Any update here? It's a bit annoying to have the xfce test red all the time :)
Updated by jorauch over 6 years ago
- Subject changed from [functional][fast]test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update to [functional][fast][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update
Looks fine for 10 days:
https://openqa.opensuse.org/tests/607929
Also on xfce:
https://openqa.opensuse.org/tests/607997#step/prepare_system_for_update_tests/1
Updated by jorauch over 6 years ago
- Status changed from Workable to Feedback
- Assignee changed from jorauch to AndreasStieger
Not sure what to do here anymore, can this be closed?
Updated by AndreasStieger over 6 years ago
- Assignee changed from AndreasStieger to jorauch
Well I am good with how it is for Leap 42.3 maintenance, but I think Ludwig had issues with Leap 15.0 test, and Oliver did not like the committed solution.
Updated by jorauch over 6 years ago
- Status changed from Feedback to In Progress
In the recent build we have only needle issues, will take a look during the day
https://openqa.opensuse.org/tests/609450#step/updates_packagekit_gpk/37
https://openqa.opensuse.org/tests/609459#step/updates_packagekit_kde/7
Updated by jorauch over 6 years ago
Created needle to detect "Reboot needed" without focus and restarted for Leap 15 XFCE:
https://openqa.opensuse.org/tests/610831#settings
Also created needle for KDE Test, but it got retriggered before:
https://openqa.opensuse.org/tests/609459
Might need to be restarted again
Updated by jorauch over 6 years ago
- Status changed from In Progress to Feedback
- Assignee changed from jorauch to lnussel
Both runs went fine, I guess we can close this?
Updated by mlin7442 about 6 years ago
on xfce it still seems does not work https://openqa.opensuse.org/tests/620664
Updated by riafarov about 6 years ago
- Due date changed from 2018-02-27 to 2018-03-13
Updated by okurz about 6 years ago
- Due date changed from 2018-03-13 to 2018-03-27
- Status changed from Feedback to Workable
- Assignee changed from lnussel to jorauch
- Target version changed from Milestone 14 to Milestone 15
@jorauch please make sure the test module works reliable in all cases (needs statistics to prove)
Updated by mgriessmeier about 6 years ago
- Subject changed from [functional][fast][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update to [functional][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update
Updated by jorauch about 6 years ago
- Status changed from Workable to In Progress
created new needle for xfce
Updated by okurz about 6 years ago
- Related to action #31327: [functional][opensuse][u][sporadic]test fails in updates_packagekit_kde - part 1 added
Updated by riafarov about 6 years ago
- Status changed from In Progress to Workable
Updated by riafarov about 6 years ago
- Related to action #16432: [functional][u][medium]test fails in updates_packagekit_kde assuming "install updates" when there are no more added
Updated by riafarov about 6 years ago
- Status changed from Workable to In Progress
- Assignee set to riafarov
Updated by riafarov about 6 years ago
Mentioned issues look more like a bug (failed to process request: https://openqa.opensuse.org/tests/578453#step/updates_packagekit_gpk/21).
In recent failures there is soft cpu lockup https://openqa.opensuse.org/tests/634883#step/updates_packagekit_gpk/10
In one case it looks like we are not waiting enough https://openqa.opensuse.org/tests/632188#step/updates_packagekit_gpk/16 , but in serial output it's again:
[ 3592.202110] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
[ 3620.202113] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
[ 3648.202117] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
[ 3676.202114] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
[ 3704.202109] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
[ 3732.202108] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u2:5:3194]
Checking if can improve logging.
Also 2 of the failures are on the same worker: https://openqa.opensuse.org/tests/632188#step/updates_packagekit_gpk/11 , namely openqaworker1:3
Here is the bug opened for that kernel version: https://bugzilla.suse.com/show_bug.cgi?id=1052258 I doubt we can do anything about it in the test, as machine becomes non responsive. I'll introduce die to point to that bug before we run the test itself as in most of the cases we have it before system stops responding completely.
Updated by mgriessmeier about 6 years ago
- Due date changed from 2018-03-27 to 2018-04-10
Updated by okurz about 6 years ago
- Subject changed from [functional][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update to [functional][u][medium] test fails in updates_packagekit_gpk - no restarting packagekit daemon after libzypp update
Updated by riafarov about 6 years ago
- Status changed from In Progress to Feedback
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/4704
Using new api call didn't work for me, will try later in other scenarios.
Updated by riafarov about 6 years ago
- Status changed from Feedback to Resolved
So, improvements to detect cpu soft lockups goes to another ticket, as I don't want to spend to much time on optional thing which is not part of this ticket. Then we schedule it and do it right.
See https://progress.opensuse.org/issues/34006
Updated by riafarov about 6 years ago
- Related to action #34006: [opensuse][functional][u] detect cpu soft lockup on leap 42.3 added