Project

General

Profile

Actions

action #168865

closed

salt-states-openqa | Failed pipeline for master | pkg.installed package vagrant not found

Added by livdywan about 1 month ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
Regressions/Crashes
Start date:
Due date:
2024-11-08
% Done:

0%

Estimated time:

Description

Observation

https://gitlab.suse.de/openqa/salt-states-openqa/-/jobs/3284605

    Function: pkg.installed
      Result: False
     Comment: Attempt 1: Returned a result of "False", with the following comment: "An error was encountered while installing package(s): Zypper command failure: Package 'vagrant' not found.
              Package 'vagrant-libvirt' not found.Loading repository data...
              Reading installed packages..."
              Attempt 2: Returned a result of "False", with the following comment: "An error was encountered while installing package(s): Zypper command failure: Package 'vagrant' not found.
              Package 'vagrant-libvirt' not found.Loading repository data...
              Reading installed packages..."
              Attempt 3: Returned a result of "False", with the following comment: "An error was encountered while installing package(s): Zypper command failure: Package 'vagrant' not found.
              Package 'vagrant-libvirt' not found.Loading repository data...
              Reading installed packages..."
              Attempt 4: Returned a result of "False", with the following comment: "An error was encountered while installing package(s): Zypper command failure: Package 'vagrant' not found.
              Package 'vagrant-libvirt' not found.Loading repository data...
              Reading installed packages..."
              An error was encountered while installing package(s): Zypper command failure: Package 'vagrant' not found.
              Package 'vagrant-libvirt' not found.Loading repository data...
              Reading installed packages...

I saw it only because it also occurs in pipelines (e.g. https://gitlab.suse.de/xren/salt-states-openqa/-/jobs/3284547).

Acceptance Criteria

  • AC1:

Suggestions


Related issues 1 (0 open1 closed)

Copied to openQA Infrastructure (public) - action #170257: salt-pillars-openqa | Failed deployment on openqa-piworker.qe.nue2.suse.org size:SResolvedmkittler

Actions
Actions #1

Updated by livdywan about 1 month ago

  • Status changed from New to In Progress
  • Assignee set to livdywan

Investigating.

Actions #2

Updated by livdywan about 1 month ago

I couldn't find any recent change related to this that would explain why this is an issue now. Surely I'm missing something obvious? 🤔

Actions #3

Updated by jbaier_cz about 1 month ago

livdywan wrote in #note-2:

I couldn't find any recent change related to this that would explain why this is an issue now. Surely I'm missing something obvious? 🤔

I guess https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/3ATHXIRH6WX2ROKWUUJUK4RLYWI55IRU/ can explain at least some bits?

Actions #4

Updated by livdywan about 1 month ago

jbaier_cz wrote in #note-3:

livdywan wrote in #note-2:

I couldn't find any recent change related to this that would explain why this is an issue now. Surely I'm missing something obvious? 🤔

I guess https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/3ATHXIRH6WX2ROKWUUJUK4RLYWI55IRU/ can explain at least some bits?

Ack. Not sure how it then took 2 months for the change to propagate but that would explain it.

Maybe the solution is to use a Leap15.5 container then.

Actions #5

Updated by openqa_review about 1 month ago

  • Due date set to 2024-11-08

Setting due date based on mean cycle time of SUSE QE Tools

Actions #7

Updated by livdywan about 1 month ago

  • Status changed from In Progress to Resolved
Actions #8

Updated by gpathak 8 days ago

  • Copied to action #170257: salt-pillars-openqa | Failed deployment on openqa-piworker.qe.nue2.suse.org size:S added
Actions

Also available in: Atom PDF