Project

General

Profile

Actions

action #108064

closed

Test fails in btrfs_autocompletion - System management is locked by the application with pid 1658 (zypper).

Added by jlausuch over 2 years ago. Updated 21 days ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2022-03-09
Due date:
% Done:

0%

Estimated time:

Description

Observation

openQA test in scenario sle-12-SP5-JeOS-for-kvm-and-xen-Updates-x86_64-jeos-filesystem@64bit-virtio-vga fails in
btrfs_autocompletion

However, looking at autoinst-log.txt, zypper retries to install it and fails with

2022-03-09 02:20:32 <5> linux(1658) [zypp] Exception.cc(log):166 MediaCurl.cc(evaluateCurlCode):1135 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/23206/SUSE_Updates_SLE-SERVER_12-SP5_x86_64/'
  2022-03-09 02:20:32 <5> linux(1658) [zypp] Exception.cc(log):166 MediaCurl.cc(doGetFileCopyFile):1591 RETHROW:  File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/23206/SUSE_Updates_SLE-SERVER_12-SP5_x86_64/'
  2022-03-09 02:20:32 <5> linux(1658) [zypp] Exception.cc(log):166 MediaMultiCurl.cc(doGetFileCopy):1363 RETHROW:  File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/23206/SUSE_Updates_SLE-SERVER_12-SP5_x86_64/'
...

So, I'm not sure if it's a test issue or network issue... but it appears quite often lately.

Test suite description

Filesystems JeOS test suite. Maintainer: qa-c

Reproducible

Fails since (at least) Build 20220309-1 (current job)

Expected result

Last good: 20220308-1 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 2 (1 open1 closed)

Related to openQA Tests - action #107062: Multiple failures due to network issuesFeedbackjstehlik2021-09-27

Actions
Related to openQA Project - action #103791: After module failure, the console is broken size:MResolvedlivdywan2021-12-09

Actions
Actions #1

Updated by jlausuch over 2 years ago

  • Project changed from openQA Tests to 208
  • Category deleted (Bugs in existing tests)
Actions #2

Updated by jlausuch over 2 years ago

  • Related to action #107062: Multiple failures due to network issues added
Actions #3

Updated by jlausuch over 2 years ago

Actions #5

Updated by mloviska over 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to mloviska
  • Priority changed from Normal to High

Setting high as it affects Maintenance jobs

Actions #6

Updated by jlausuch over 2 years ago

  • Related to action #103791: After module failure, the console is broken size:M added
Actions #7

Updated by jlausuch over 2 years ago

In this one https://openqa.suse.de/tests/8322911#step/btrfs_autocompletion/4
zypper --non-interactive refs Server_Applications_Module_15_SP3_x86_64

https://openqa.suse.de/tests/8322915#step/btrfs_autocompletion/4
zypper --non-interactive refs Basesystem_Module_15_SP3_x86_64

So, for sure, the previous module snapper_jeos_cli leaves the system in some state where some operations are still running. The idea would be to wait at the end of that module until any zypper|SUSEConnect|rollback operations is happening.

Actions #8

Updated by mloviska over 2 years ago

  • Status changed from In Progress to Feedback
Actions #9

Updated by mloviska over 2 years ago

  • Status changed from Feedback to Resolved
Actions #10

Updated by jlausuch over 2 years ago

  • Status changed from Resolved to In Progress

Looks like that check was not enough...
https://openqa.suse.de/tests/8332025#step/btrfs_autocompletion/2
Maybe adding at the end of the test another loop for waiting for any zypper operation?

Actions #11

Updated by mloviska over 2 years ago

jlausuch wrote:

Looks like that check was not enough...
https://openqa.suse.de/tests/8332025#step/btrfs_autocompletion/2
Maybe adding at the end of the test another loop for waiting for any zypper operation?

Nice catch! Thanks! It has exhausted all attempts and the file was still there https://openqa.suse.de/tests/8332025#step/snapper_jeos_cli/147 and https://openqa.suse.de/tests/8332025#step/snapper_jeos_cli/143. So maybe I should increase the sleep time or number of attempts?

Actions #12

Updated by mloviska over 2 years ago

  • Status changed from In Progress to Feedback

Let's hope the TO and number of attempts are enough now

Actions #13

Updated by jlausuch over 2 years ago

mloviska wrote:

Let's hope the TO and number of attempts are enough now

crossing fingers!

Actions #14

Updated by mloviska over 2 years ago

Haven't seen this for 3 weeks. Can we close it ?

Actions #15

Updated by jlausuch over 2 years ago

  • Status changed from Feedback to Resolved

Yes, looks like the fix works. Thanks for taking care!

Actions #16

Updated by ph03nix 29 days ago

  • Tags changed from bug to MinimalVM
Actions #17

Updated by ph03nix 21 days ago

  • Project changed from 208 to Containers and images
Actions

Also available in: Atom PDF