Project

General

Profile

Actions

action #105951

closed

[qe-core]test fails in rmt_feature -repository errors sle15-sp[0123] - 'zypper -n in rmt-server' failed with code 107

Added by martinsmac about 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-qam_rmt@64bit fails in
rmt_feature

Test suite description

Testsuite maintained at https://gitlab.suse.de/qa-maintenance/qam-openqa-yml. Meant for scheduling rmt tests on QAM Updates

Reproducible

Fails since (at least) Build 20220204-1

Expected result

Last good: 20220203-1 (or more recent)

Further details

Always latest result in this scenario: latest

sle-15-SP3-Server-DVD-Updates-x86_64-Build20220204-1-qam_rmt@64bit
sle-15-SP2-Server-DVD-Updates-x86_64-Build20220204-1-qam_rmt@64bit
sle-15-SP1-Server-DVD-Updates-x86_64-Build20220204-1-qam_rmt@64bit
sle-15-Server-DVD-Updates-x86_64-Build20220204-1-qam_rmt@64bit

2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22647/SUSE_Updates_SLE-Module-Server-Applications_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22634/SUSE_Updates_SLE-Module-Python2_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22561/SUSE_Updates_SLE-Module-Containers_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22621/SUSE_Updates_SLE-Module-Containers_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22369/SUSE_Updates_SLE-Module-Desktop-Applications_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22179/SUSE_Updates_SLE-Module-Web-Scripting_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22434/SUSE_Updates_SLE-Module-Legacy_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22652/SUSE_Updates_SLE-Module-Legacy_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22672/SUSE_Updates_SLE-Product-SLES_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22287/SUSE_Updates_SLE-Module-Basesystem_15-SP3_x86_64/'
2022-02-04 02:42:13 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22369/SUSE_Updates_SLE-Module-Basesystem_15-SP3_x86_64/'
2022-02-04 02:42:14 <5> susetest(2736) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW:    File '/media.1/media' not found on medium 'https://updates.suse.com/SUSE/Updates/SLE-Module-Web-Scripting/15-SP3/x86_64/update?WgYNEIW7cjGFjfFVsxchDlava6vdoo7ksh640hDg1LYx93dr6xfrHnTwxNcWsJQ0gNkozxqYYdmfQpE1vHBzQTpuK2wHONe8AfOI1hzX63yqVdjfNrX1lZeiFZNzRC90yUtqQg3eSs9laalvXRo04M4G4lTSm3Uz3Q' at sle/lib/utils.pm line 587.
    utils::zypper_call("in rmt-server") called at sle/lib/repo_tools.pm line 245
    repo_tools::rmt_wizard() called at sle/tests/console/rmt/rmt_feature.pm line 22
    rmt_feature::run(rmt_feature=HASH(0x5633ee784d90)) called at /usr/lib/os-autoinst/basetest.pm line 360
    eval {...} called at /usr/lib/os-autoinst/basetest.pm line 354
    basetest::runtest(rmt_feature=HASH(0x5633ee784d90)) called at /usr/lib/os-autoinst/autotest.pm line 372
    eval {...} called at /usr/lib/os-autoinst/autotest.pm line 372
    autotest::runalltests() called at /usr/lib/os-autoinst/autotest.pm line 242
    eval {...} called at /usr/lib/os-autoinst/autotest.pm line 242
    autotest::run_all() called at /usr/lib/os-autoinst/autotest.pm line 296
    autotest::__ANON__(Mojo::IOLoop::ReadWriteProcess=HASH(0x5633ef7c2f78)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
    eval {...} called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 326
    Mojo::IOLoop::ReadWriteProcess::_fork(Mojo::IOLoop::ReadWriteProcess=HASH(0x5633ef7c2f78), CODE(0x5633efb47880)) called at /usr/lib/perl5/vendor_perl/5.26.1/Mojo/IOLoop/ReadWriteProcess.pm line 488
    Mojo::IOLoop::ReadWriteProcess::start(Mojo::IOLoop::ReadWriteProcess=HASH(0x5633ef7c2f78)) called at /usr/lib/os-autoinst/autotest.pm line 298
    autotest::start_process() called at /usr/bin/isotovideo line 261
Actions #1

Updated by mgrifalconi about 2 years ago

Pinged Yutao Wang on Slack

Actions #2

Updated by tinawang123 about 2 years ago

Checked rmt_feature_zypper.log file, got error message:
2022-02-08 02:59:22 susetest(2754) [zypp::exec] abstractspawnengine.cc(checkStatus):197 Pid 2785 was killed by signal 9 (Killed; Out of memory?)
2022-02-08 02:59:22 susetest(2754) [zypp++] ZYppImpl.cc(commit):179 unloading @System repo from pool
About http://openqa.suse.de/tests/8107798#step/rmt_feature/16
2022-02-04 23:57:26 susetest(2447) [zypp-core] Exception.cc(log):186 MediaCurl.cc(evaluateCurlCode):810 THROW: File '/media.1/media' not found on medium 'http://dist.suse.de/ibs/SUSE:/Maintenance:/22316/SUSE_Updates_SLE-Product-SLES_15-SP1-LTSS_x86_64/'
It doesn't have file '/media.1/media' at this URL.
Do you think is it a bug for sles15sp1 maintain?
It seems sles15sp3 this case can pass: https://openqa.suse.de/tests/8025095#step/boot_to_desktop/1

Actions #3

Updated by tinawang123 about 2 years ago

I changed to use DEV_PATH RMT version (URL: http://download.suse.de/ibs/Devel:/SCC:/RMT/SLE_15_SP1_Update/), it still has problem:
Refer case: http://openqa.suse.de/tests/8116667#step/rmt_feature/10
[ 102.805412] systemd[2396]: Started D-Bus User Message Bus.
[ 102.820320] dbus-daemon[2486]: [session uid=0 pid=2486] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.1' (uid=0 pid=2484 comm="appstream-util install-origin Basesystem_Module_15")
[ 102.826627] systemd[2396]: Starting Virtual filesystem service...
[ 102.835758] dbus-daemon[2486]: [session uid=0 pid=2486] Successfully activated service 'org.gtk.vfs.Daemon'
[ 102.839730] systemd[2396]: Started Virtual filesystem service.
[ 104.268621] gnome-software[2373]: failed to rescan: Failed to parse /var/cache/app-info/xmls/Basesystem_Module_15_SP1_x86_64_SLE-Module-Basesystem15-SP1-Pool.xml.gz file: Error opening file /var/cache/app-info/xmls/Basesystem_Module_15_SP1_x86_64_SLE-Module-Basesystem15-SP1-Pool.xml.gz: Permission denied
[ 104.280417] gnome-software[2373]: failed to rescan: Failed to parse /var/cache/app-info/xmls/Desktop_Applications_Module_15_SP1_x86_64_SLE-Module-Desktop-Applications15-SP1-Pool.xml.gz file: Error opening file /var/cache/app-info/xmls/Desktop_Applications_Module_15_SP1_x86_64_SLE-Module-Desktop-Applications15-SP1-Pool.xml.gz: Permission denied
[ 104.292342] gnome-software[2373]: failed to rescan: Failed to parse /var/cache/app-info/xmls/Development_Tools_Module_15_SP1_x86_64_SLE-Module-DevTools15-SP1-Pool.xml.gz file: Error opening file /var/cache/app-info/xmls/Development_Tools_Module_15_SP1_x86_64_SLE-Module-DevTools15-SP1-Pool.xml.gz: Permission denied
[ 106.163549] gnome-software[2373]: failed to rescan: Failed to parse /var/cache/app-info/xmls/Server_Applications_Module_15_SP1_x86_64_SLE-Module-Server-Applications15-SP1-Pool.xml.gz file: Error opening file /var/cache/app-info/xmls/Server_Applications_Module_15_SP1_x86_64_SLE-Module-Server-Applications15-SP1-Pool.xml.gz: Permission denied

It has Permission denied.

Actions #4

Updated by mgrifalconi about 2 years ago

https://suse.slack.com/archives/C02D16TCP99/p1644330394848529

Requested info on slack about a zypper update that was immediately approved by the dashboard and that was just before rmt test started to break. Not sure if it is related

Actions #6

Updated by tjyrinki_suse about 2 years ago

  • Status changed from New to Workable
  • Start date deleted (2022-02-04)
Actions #7

Updated by mgrifalconi about 2 years ago

  • Priority changed from Normal to High
Actions #9

Updated by szarate about 2 years ago

  • Status changed from Workable to Rejected
  • Assignee set to szarate

rmt bug

Actions #10

Updated by szarate about 2 years ago

  • Subject changed from [qe-core]test fails in rmt_feature -repository errors sle15-sp[0123] to [qe-core]test fails in rmt_feature -repository errors sle15-sp[0123] - 'zypper -n in rmt-server' failed with code 107
Actions

Also available in: Atom PDF