Project

General

Profile

Actions
Copy link

action #170257

closed

salt-pillars-openqa | Failed deployment on openqa-piworker.qe.nue2.suse.org size:S

Added by gpathak 8 days ago. Updated 7 days ago.

Status:
Resolved
Priority:
High
Assignee:
mkittler
Category:
Regressions/Crashes
Target version:
openQA Project (public) - Ready
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:
alert, salt, gitlab, infra

Description

Observation

https://gitlab.suse.de/openqa/salt-pillars-openqa/-/jobs/3425302

Summary for openqa-piworker.qe.nue2.suse.org
--------------
Succeeded: 324 (changed=4)
Failed:      3
--------------
Total states run:     327
Total run time:    66.495 s
openqa-piworker.qe.nue2.suse.org:
    Error: pkgrepo.managed
openqa-piworker.qe.nue2.suse.org:
    Error: pkg.latest
openqa-piworker.qe.nue2.suse.org:
    Error: pkgrepo.managed

Maybe related to #169564

Suggestions

  • Check details of linked error. Probably missing access to some repository but with wireguard tunnel we should have access. So maybe transient and works after refreshing zypper repos once explicitly?
  • Look into the error details regarding "datastructure in python"
  • Problem might also be linked to not trusted repo
  • Remove it from salt for now as mitigation if no easy/quick fix can be found

Related issues 1 (0 open — 1 closed)

Copied from openQA Infrastructure (public) - action #168865: salt-states-openqa | Failed pipeline for master | pkg.installed package vagrant not foundResolvedlivdywan2024-11-08

Actions
Actions
Copy link
 #1

Updated by gpathak 8 days ago

  • Copied from action #168865: salt-states-openqa | Failed pipeline for master | pkg.installed package vagrant not found added
Actions
Copy link
 #2

Updated by okurz 8 days ago

  • Subject changed from salt-pillars-openqa | Failed deployment on openqa-piworker.qe.nue2.suse.org to salt-pillars-openqa | Failed deployment on openqa-piworker.qe.nue2.suse.org size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by okurz 8 days ago

  • Parent task changed from #169564 to #166598
Actions
Copy link
 #4

Updated by mkittler 7 days ago

  • Status changed from Workable to In Progress
Actions
Copy link
 #5

Updated by mkittler 7 days ago

  • Status changed from In Progress to Resolved

I ran sudo salt 'openqa-piworker.qe.nue2.suse.org' state.apply two times and it worked both times. Then I also ran sudo zypper ref --force to check manually whether there are any broken repos but there were none. So I'm not sure what caused this failure.

The actual error messages are:

----------
          ID: security-sensor.repo
    Function: pkgrepo.managed
      Result: False
     Comment: Failed to configure repo 'security-sensor.repo': refresh_db() got multiple values for keyword argument 'root'
     Started: 10:13:15.590537
    Duration: 738.083 ms
…
----------
          ID: security-sensor.repo
    Function: pkg.latest
        Name: velociraptor-client
      Result: False
     Comment: One or more requisite failed: security_sensor.security-sensor.repo
     Started: 10:13:16.337478
    Duration: 0.019 ms
…
          ID: SUSE_CA
    Function: pkgrepo.managed
      Result: False
     Comment: Failed to configure repo 'SUSE_CA': refresh_db() got multiple values for keyword argument 'root'
     Started: 10:13:34.166110
    Duration: 718.863 ms

So it doesn't look like a network problem but a programming mistake in Salt (because this is actually an error from Python about wrong parameter-passing that a user is probably never expected so see). I also found https://github.com/saltstack/salt/issues/64118 and https://github.com/saltstack/salt/issues/35764 which are about a similar problems.

These specific states worked when I re-ran the state.apply as mentioned before. So I wouldn't make a big deal out of it and consider this ticket resolved. If we see the problem again we can re-open.

Actions
Copy link

Also available in: Atom PDF