Project

General

Profile

Actions

action #91968

closed

[opensuse][vagrant] virtualbox 6.1.20: File "vboxautostart.service" is replaced by "vboxautostart-service.service"

Added by dimstar almost 3 years ago. Updated almost 3 years ago.

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

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-extra_tests_vagrant@64bit fails in
add_box_virtualbox

Virtualbox upstream renamed the service file, which in turn makes our test fail (still referencing the old name)

Test suite description

Maintainer: dancermak. Test vagrant, vagrant plugins and the vagrant boxes

Reproducible

Fails since (at least) Build 20210427

Expected result

Last good: 20210426 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from virtualbox 6.1.20: File "vboxautostart.service" is replaced by "vboxautostart-service.service" to [opensuse][vagrant] virtualbox 6.1.20: File "vboxautostart.service" is replaced by "vboxautostart-service.service"
  • Start date deleted (2021-04-29)
Actions #2

Updated by dancermak almost 3 years ago

  • Status changed from New to In Progress
Actions #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: extra_tests_vagrant
https://openqa.opensuse.org/tests/1766969

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 #4

Updated by dancermak almost 3 years ago

  • Status changed from In Progress to Resolved

The underlying issue has been resolved, the remaining failures are the existing vagrant test flakiness.

Actions #5

Updated by okurz almost 3 years ago

Just setting the ticket to "Resolved" won't stop the reminders in case tests are still failing and referencing this ticket

Actions #6

Updated by dancermak almost 3 years ago

okurz wrote:

Just setting the ticket to "Resolved" won't stop the reminders in case tests are still failing and referencing this ticket

Could someone remove that reference then please? It is not correct anymore.

Actions #7

Updated by okurz almost 3 years ago

Maybe that was achieved already. Following the openQA job url in #91968#note-3 https://openqa.opensuse.org/tests/1766969#comments does not reference this ticket. Maybe someone removed that comment again. Following the most recent job within the same scenario we end up on
https://openqa.opensuse.org/tests/1766969#next_previous
which fails but does not reference a progress ticket but a product bug, https://bugzilla.opensuse.org/show_bug.cgi?id=1180358 … which is assigned to dcermak@suse.com and has many openQA reminder comments as well :D So I guess it can actually be ok that you set the progress ticket to "Resolved".

Actions

Also available in: Atom PDF