Project

General

Profile

Actions
Copy link

action #90566

open

[qe-core][opensuse] Leap 15.3 - test fails in rebootmgr - invalid url passed to zypper install

Added by lkocman about 3 years ago. Updated about 2 months ago.

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

0%

Estimated time:
Difficulty:

Description

Observation

Calling zypper install
2021-03-30 23:33:05 tukit 3.2.2 started
2021-03-30 23:33:05 Options: callext 3 zypper -R {} install update-test-trivial/update-test-interactive-5-2.1.x86_64.rpm
2021-03-30 23:33:05 Executing zypper -R /tmp/transactional-update-UbYzNU install update-test-trivial/update-test-interactive-5-2.1.x86_64.rpm:
Specified local path does not exist or is not accessible.
Problem retrieving the specified RPM file:
Malformed URI:
Please check whether the file is accessible.
Problem with the RPM file specified as 'update-test-trivial/update-test-interactive-5-2.1.x86_64.rpm', skipping.
No valid arguments specified.

openQA test in scenario opensuse-15.3-DVD-x86_64-transactional_server@64bit fails in
rebootmgr

Test suite description

Installation only of the transactional updates and read-only root fs role.

Maintainer: SergioAtSUSE slindomansilla@suse.com

Reproducible

Fails since (at least) Build 85.2

Expected result

Last good: 81.3 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz about 3 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: transactional_server
https://openqa.opensuse.org/tests/1691348

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #2

Updated by tjyrinki_suse about 3 years ago

  • Status changed from New to Resolved

This one didn't work until 13 days ago, failing every time, but now passing in the last 3 runs, so someone probably fixed something about this.

Actions
Copy link
 #3

Updated by openqa_review almost 3 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: transactional_server
https://openqa.opensuse.org/tests/1757499

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #4

Updated by okurz almost 3 years ago

  • Subject changed from Leap 15.3 - test fails in rebootmgr - invalid url passed to zypper install to [qe-core] Leap 15.3 - test fails in rebootmgr - invalid url passed to zypper install
  • Status changed from Resolved to New

openqa_review says not fixed though :/

Actions
Copy link
 #5

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qe-core] Leap 15.3 - test fails in rebootmgr - invalid url passed to zypper install to [qe-core][opensuse] Leap 15.3 - test fails in rebootmgr - invalid url passed to zypper install
  • Start date deleted (2021-03-31)

curl command not found

Actions
Copy link
 #6

Updated by openqa_review almost 3 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: transactional_server
https://openqa.opensuse.org/tests/1757499

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"
  3. The label in the openQA scenario is removed
Actions
Copy link
 #7

Updated by okurz almost 3 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: transactional_server
https://openqa.opensuse.org/tests/1757499

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
Copy link
 #8

Updated by openqa_review almost 3 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: transactional_server
https://openqa.opensuse.org/tests/1757499

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
Copy link
 #9

Updated by openqa_review almost 3 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: transactional_server
https://openqa.opensuse.org/tests/1757499

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
Copy link
 #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: transactional_server
https://openqa.opensuse.org/tests/1757499

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
Copy link
 #11

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: transactional_server
https://openqa.opensuse.org/tests/1937128

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
Copy link
 #12

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: transactional_server
https://openqa.opensuse.org/tests/1966306

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
Copy link
 #13

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: transactional_server
https://openqa.opensuse.org/tests/1992971

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
Copy link
 #14

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: transactional_server
https://openqa.opensuse.org/tests/2027626

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
Copy link
 #15

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: transactional_server
https://openqa.opensuse.org/tests/2052484

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
Copy link
 #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: transactional_server
https://openqa.opensuse.org/tests/2027626

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
Copy link
 #17

Updated by slo-gin over 1 year ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link
 #18

Updated by slo-gin about 2 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions
Copy link

Also available in: Atom PDF