Project

General

Profile

Actions

action #128927

closed

OSD deployment changelog repeatedly mentions old os-autoinst changes, is a worker outdated and unable to install newer packages? size:M

Added by okurz 12 months ago. Updated 12 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
2023-05-08
Due date:
% Done:

0%

Estimated time:

Description

Observation

Recent example from 2023-05-08:

You can find the details on https://gitlab.suse.de/openqa/osd-deployment/-/jobs/1558014
As always, if you encounter problems, please file tickets on https://progress.opensuse.org.
Have fun, your QA tools team


 * Sun May 07 2023 okurz@suse.com
 - Update to version 4.6.1683294886.8a7e554:
   *


os-autoinst changes:
 * Sun May 07 2023 okurz@suse.com
 - Update to version 4.6.1683277334.0688448:
   * Enable VNC endian conversion when worker is big-endian
   * Add support for serial device of s390x in testapi
   * dist: Fix unresolved dependency on chattr in OBS
   * Show initialization errors of `isotovideo` again
   * Test sending forced VNC update request explicitly
   * container: Distinguish jq and non-jq variants in BuildTag
   * Drop setting of TESSDATA_PREFIX in invoke-tests
   * Replace Perl::Critic::{Freenode,Community}
   * Add workaround to prevent `t/29-backend-generalhw.t` being unstable
   * Cover all code of `console.pm`
   * Fix CMake warning about ordering
   * ci: Improve marking uncoverable statements
   * Drop Leap-15.3 from OBS CI

I have seen the oldest os-autoinst changes mentioned here in before, e.g. "Drop Leap-15.3 from OBS CI". I assume we have the same problem that we had already in the past where at least one worker was unable to update packages due to ppc64le builds failing on devel:openQA

Acceptance criteria

  • AC1: The problematic worker instance is receiving updates again with the same frequency as other workers

Suggestions

  • Look into devel:openQA for build failures and fix them
  • DONE Find the old ticket about "changelog" -> #124658
  • Look into the deployment pipeline details
  • Check that all salt machines are up-to-date or fix the found problem(s)

Related issues 2 (0 open2 closed)

Related to openQA Infrastructure - action #120372: OSD deployment fails presumably when handling the changelogResolvedokurz2022-11-14

Actions
Related to openQA Infrastructure - action #124658: [osd-deployment] missing os-autoinst changes in deployment and changelog emails , build failure on ppc64le in OBS size:MResolvedmkittler2023-02-16

Actions
Actions

Also available in: Atom PDF