Project

General

Profile

Actions
Copy link

action #120372

closed

OSD deployment fails presumably when handling the changelog

Added by mkittler over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
okurz
Category:
-
Target version:
openQA Project - Ready
Start date:
2022-11-14
Due date:
% Done:

0%

Estimated time:

Description

Observation

The deployment fails with:

++ ssh openqa.suse.de 'set -xo pipefail;      sudo salt -C '\''worker2*'\'' cmd.run '\''rpm -q --changelog os-autoinst'\'' | sed '\''s/^    //'\'' > /tmp/os-autoinst-before_changelog &&      sudo salt -C '\''G@roles:worker'\'' cmd.run '\''rpm -qa | grep "\(os-autoinst\|openQA\)" > /tmp/osd-deployment_rpm_q'\'''
+ sudo salt -C 'worker2*' cmd.run 'rpm -q --changelog os-autoinst'
+ sed 's/^    //'
.ERROR: No return received

(https://gitlab.suse.de/openqa/osd-deployment/-/jobs/1238261)

Further notes

Related issues 1 (0 open — 1 closed)

Related to openQA Infrastructure - action #128927: OSD deployment changelog repeatedly mentions old os-autoinst changes, is a worker outdated and unable to install newer packages? size:MResolvedmkittler2023-05-08

Actions
Actions
Copy link
 #1

Updated by okurz over 1 year ago

Well, we removed worker2 from salt so that should explain it :)

We could change the approach to pick the first salt worker that is currently in the list and responding.

Actions
Copy link
 #2

Updated by okurz over 1 year ago

  • Due date set to 2022-12-02
  • Status changed from New to Feedback
  • Assignee set to okurz
Actions
Copy link
 #3

Updated by livdywan over 1 year ago

okurz wrote:

https://gitlab.suse.de/openqa/osd-deployment/-/merge_requests/51

I feel like we should rethink the purpose of this. Using a random worker to look rpm changelogs can't tell us if the deployment was consistent. We could equally get changelogs straight from OBS.

Actions
Copy link
 #4

Updated by mkittler over 1 year ago

  • Assignee deleted (okurz)
  • Target version deleted (Ready)

This isn't to validate whether the deployment was consistent. It is to obtain some changelogs for the mail (that are at least valid for a subset of workers). Note that OBS is not necessarily in sync with what we've deployed as well (e.g. a new package might have been built in the meantime). Besides, OBS doesn't know what our last installed version was so we still needed to track at least that.

Actions
Copy link
 #5

Updated by mkittler over 1 year ago

  • Assignee set to okurz
  • Target version set to Ready
Actions
Copy link
 #6

Updated by okurz over 1 year ago

  • Status changed from Feedback to In Progress
Actions
Copy link
 #7

Updated by okurz over 1 year ago

I introduced one problem that the $() was executed prematurely in the CI environment instead of on the remote host. https://gitlab.suse.de/openqa/osd-deployment/-/commit/982c8f2c1b8cf177263526d2c11c5de2cecae5ea should fix that. https://gitlab.suse.de/openqa/osd-deployment/-/jobs/1240298 confirmed.

Actions
Copy link
 #8

Updated by okurz over 1 year ago

  • Due date deleted (2022-12-02)
  • Status changed from In Progress to Resolved
Actions
Copy link
 #9

Updated by okurz 12 months ago

  • Related to action #128927: OSD deployment changelog repeatedly mentions old os-autoinst changes, is a worker outdated and unable to install newer packages? size:M added
Actions
Copy link

Also available in: Atom PDF