Project

General

Profile

Actions

action #97310

closed

[migration] test fails in patch_sle

Added by acarvajal over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-08-20
Due date:
% Done:

100%

Estimated time:
12.00 h
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP4-Full-x86_64-migration_offline_dvd_sles4sap15sp1@64bit-2gbram-cirrus fails in
patch_sle

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 16.3

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

It seems the second call to zypper -n patch --with-interactive in the tests/update/patch_sle test module (called from utils::fully_patch_system), is triggering a restart of GDM in this scenario (SLES for SAP Applications 15-SP1 to 15-SP4 migration, while working on 15-SP1 before the migration); as a result, the SUT which was working on the root console in tty6 finds itself switched to the graphical interface, and further commands from the test suit fail.

A call to select_console('root-console'); after the call to fully_patch_system should fix this issue.

[  795.203462] systemd-logind[15291]: New session c1 of user gdm.
[  795.228885] systemd-logind[15291]: New session 1 of user root.
[  795.240190] systemd[1]: Reloading.
[  795.417614] at-spi-bus-launcher[2747]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
[  795.419214] at-spi-bus-launcher[2747]:       after 29 requests (29 known processed) with 0 events remaining.
[  795.434746] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
[  795.436468] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' exited with code 1
[  795.452644] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
[  795.454741] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
[  795.456720] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
[  795.458497] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
[  795.466021] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
[  795.480932] polkitd[15263]: Unregistered Authentication Agent for unix-session:c1 (system bus name :1.69, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
[  795.574399] gnome-session-binary[2743]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
[  795.676551] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.XSettings.desktop' exited with code 1
[  795.678269] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Power.desktop' exited with code 1
[  795.679724] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.MediaKeys.desktop' exited with code 1
[  795.712191] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Color.desktop' exited with code 1
[  795.713646] systemd[2720]: Stopping D-Bus User Message Bus...
[  795.727792] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
[  795.729832] systemd[2720]: Stopped D-Bus User Message Bus.
[  795.737029] gnome-session-binary[2743]: WARNING: App 'org.gnome.SettingsDaemon.A11yKeyboard.desktop' exited with code 1
[  795.738706] systemd[2720]: Started D-Bus User Message Bus.
[  795.748667] gdm-launch-environment][2673]: pam_unix(gdm-launch-environment:session): session closed for user gdm
[  795.754586] gdm[1996]: Child process 2673 was already dead.
[  795.755827] gdm[1996]: Unable to kill session worker process
[  795.849000] systemd[1]: Started User Manager for UID 1001.
[  795.851882] systemd[1]: Started User Manager for UID 0.
[  795.854743] systemd[1]: Started User Runtime Directory /run/user/1002.
[  795.979279] systemd-logind[15291]: Session c1 logged out. Waiting for processes to exit.
[  795.992563] [RPM][15292]: install lvm2-2.02.180-12.40.1.x86_64: success
[  796.013198] systemd-logind[15291]: New session c2 of user gdm.
[  796.022124] systemd[1]: Starting User Runtime Directory /run/user/1001...
[  796.023665] systemd[1]: Starting User Runtime Directory /run/user/0...
[  796.051135] systemd[1]: Starting User Runtime Directory /run/user/470...
[  797.267405] systemd-logind[15291]: Removed session c1.
[  797.283177] systemd[1]: Started User Runtime Directory /run/user/1001.
[  797.284907] systemd[1]: Started User Runtime Directory /run/user/0.
[  797.293950] systemd[1]: Started User Runtime Directory /run/user/470.
[  797.295194] systemd[1]: Reloading.
[  797.719490] systemd[1]: Started Session c2 of user gdm.
[  797.745425] systemd[1]: Closed LVM2 poll daemon socket.
[  797.748013] systemd[1]: Stopping LVM2 poll daemon socket.
[  797.749054] systemd[1]: Listening on LVM2 poll daemon socket.
[  797.755053] systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[  797.772914] gdm-launch-environment][15332]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Actions #1

Updated by acarvajal over 2 years ago

Issue is also impacting online migration from SLES for SAP Applications 15-SP1 to 15-SP4, in the test module migration/online_migration/zypper_patch: https://openqa.suse.de/tests/6888274#step/zypper_patch/13

Whatever fix is submitted in the test code, should also include this second module.

Actions #2

Updated by maritawerner over 2 years ago

  • Subject changed from test fails in patch_sle to [migration] test fails in patch_sle
Actions #3

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/6993384

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The label in the openQA scenario is removed
Actions #4

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7124405

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #5

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7261138

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #6

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7429167

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #7

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7583384

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #8

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7655238

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #9

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7763850

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #10

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_offline_dvd_sles4sap15sp1
https://openqa.suse.de/tests/7815865

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #11

Updated by leli over 2 years ago

  • Assignee set to leli
Actions #12

Updated by leli over 2 years ago

I have created a branch to add select_console before sync, it works. https://openqa.nue.suse.com/tests/7882530#step/start_install/2

Now just don't know what cause restart GDM, next is to make the test code change according this, need to find a suitable condition for sap migration test.

Actions #13

Updated by zcjia over 2 years ago

leli wrote:

I have created a branch to add select_console before sync, it works. https://openqa.nue.suse.com/tests/7882530#step/start_install/2

Now just don't know what cause restart GDM, next is to make the test code change according this, need to find a suitable condition for sap migration test.

The restart of GDM is caused by the upgrade of "polkit", and we consider it as expected behavior instead of bug. So please add your fix that "use select_console before sync".

Actions #14

Updated by leli over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50
  • Estimated time set to 12.00 h
Actions #15

Updated by leli over 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

PR merged. Let's keep an eye on it for next build.

Actions #16

Updated by openqa_review over 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_online_zypper_sles4sap15sp1
https://openqa.suse.de/tests/7929302

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #17

Updated by okurz over 2 years ago

  • Status changed from Resolved to Feedback

^

Actions #18

Updated by openqa_review about 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_online_zypper_sles4sap15sp1
https://openqa.suse.de/tests/8019195

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234
Actions #19

Updated by dzedro about 2 years ago

The latest failures are new issue, probably bug. GDM is started while zypper -n patch --with-interactive -l is running, and the following cmd reboot is not executed in GDM, next assert_screen then can't find bootloader/grub2.
I it happening only on SAP ?
https://openqa.suse.de/tests/8126122 x86_64
https://openqa.suse.de/tests/8125367 ppc64le

Actions #20

Updated by leli about 2 years ago

dzedro wrote:

The latest failures are new issue, probably bug. GDM is started while zypper -n patch --with-interactive -l is running, and the following cmd reboot is not executed in GDM, next assert_screen then can't find bootloader/grub2.
I it happening only on SAP ?
https://openqa.suse.de/tests/8126122 x86_64
https://openqa.suse.de/tests/8125367 ppc64le

Yes, this is not the original issue any more, suggest to open a new ticket to track it.

Actions #21

Updated by openqa_review about 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_online_zypper_sles4sap15sp1
https://openqa.suse.de/tests/8207078

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. 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.

Actions #22

Updated by openqa_review about 2 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: migration_online_zypper_sles4sap15sp1
https://openqa.suse.de/tests/8375251#step/zypper_patch/1

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
  3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions #23

Updated by leli almost 2 years ago

  • Status changed from Feedback to In Progress
  • % Done changed from 100 to 50
Actions #24

Updated by leli almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

PR merged.

Actions

Also available in: Atom PDF