action #120372
closed
OSD deployment fails presumably when handling the changelog
Added by mkittler over 1 year ago.
Updated over 1 year ago.
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¶
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.
- Due date set to 2022-12-02
- Status changed from New to Feedback
- Assignee set to okurz
- 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.
- Assignee set to okurz
- Target version set to Ready
- Status changed from Feedback to In Progress
- Due date deleted (
2022-12-02)
- Status changed from In Progress to Resolved
- 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
Also available in: Atom
PDF