Project

General

Profile

Actions
Copy link

action #62036

closed

[opensuse][vagrant] test fails in add_box_libvirt - Tumbleweed rolls to fast

Added by StefanBruens over 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
dancermak
Category:
Bugs in existing tests
Target version:
-
Start date:
2020-01-11
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_libvirt

According to vagrant, the latest version was 20200108.1:

curl -q https://app.vagrantup.com/openSUSE/boxes/Tumbleweed.x86_64 
{
  "description":"Tumbleweed.x86_64 Vagrant Box",
  "short_description":"Tumbleweed.x86_64 Vagrant Box",
  "name":"opensuse/Tumbleweed.x86_64",
  "versions":[{
    "version":"1.0.20200108",
    "status":"active",
    "description_html":"<p>Tumbleweed.x86_64 Vagrant images</p>\n",
    "description_markdown":"Tumbleweed.x86_64 Vagrant images\n",
    "providers":[{
      "name":"virtualbox","url":"https://vagrantcloud.com/opensuse/boxes/Tumbleweed.x86_64/versions/1.0.20200108/providers/virtualbox.box","checksum":null,"checksum_type":null
      },{
      "name":"libvirt","url":"https://vagrantcloud.com/opensuse/boxes/Tumbleweed.x86_64/versions/1.0.20200108/providers/libvirt.box","checksum":null,"checksum_type":null
    }]
}]}

while download.opensuse.org disagreed and only had 20200109.

Test suite description

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

Reproducible

Fails since (at least) Build 20191202

Expected result

Last good: (unknown) (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by okurz over 4 years ago

  • Subject changed from test fails in add_box_libvirt - Tumbleweed rolls to fast to [opensuse][vagrant] test fails in add_box_libvirt - Tumbleweed rolls to fast

something for dancermak/defolos who I could not find on this project. Latest tests in the scenario are blocked on https://bugzilla.opensuse.org/show_bug.cgi?id=1156497 however.

Actions
Copy link
 #2

Updated by dancermak about 4 years ago

This is a known issue, what you are seeing here is not Tumbleweed rolling too fast, but the publishing Jenkins pipeline being too slow and OBS already having deleted the latest build results.

A little more details about the whole vagrant publishing process:

  • On each new snapshot that gets published, a Jenkins pipeline is triggered that links the latest snapshot to Vagrant Cloud.
  • The image is however only linked to download.o.o, it is not uploaded to Vagrant Cloud. So if the Jenkins pipeline gets delayed, then Vagrant Cloud hasn't been notified yet about the new image. But OBS has already removed the old image that Vagrant Cloud knows about.

What is weird about this though is the following: the order is wrong here. I would expect this to occur if the Tumbleweed image gets published, the Jenkins pipeline gets delayed and then openQA runs. But openQA should run before the image gets published. I guess that this has been a fluke in the Jenkins pipeline, as the latest test worked again.

We could stomp out this issue by using a different image in the test, e.g. centos/7 as they upload their images to Vagrant Cloud and should be available.

Actions
Copy link
 #3

Updated by dancermak about 4 years ago

  • Status changed from New to Workable
  • Assignee set to dancermak
Actions
Copy link
 #4

Updated by okurz almost 4 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/1241093

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

Updated by okurz almost 4 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/1257492

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

Updated by dancermak over 3 years ago

  • Status changed from Workable to Resolved

This issue should not occur anymore, as we are now uploading the vagrant boxes to vagrant cloud directly.

Actions
Copy link

Also available in: Atom PDF