Project

General

Profile

Actions

action #161399

closed

coordination #58184: [saga][epic][use case] full version control awareness within openQA

coordination #48641: [epic] Trigger openQA tests in pull requests of any product github pull request

Use Tumbleweed again for openqa-single-instance container size:S

Added by tinita 7 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

In #87695 we downgraded the openqa-single-instance container because Tumbleweed did not work in GitHub codespaces.

I created a bugreport here:
https://github.com/orgs/community/discussions/127083
Installing awk and tar fixes it, see https://progress.opensuse.org/issues/161399#note-6

Acceptance criteria

  • AC1: A Tumbleweed based openqa-single-instance codespaces container is used in osado and other projects where currently Leap based
  • AC2: The pure openqa-single-instance container does not explicitly install anything that's only needed in codespaces
  • AC3: openqa-single-instance container uses Tumbleweed again

Suggestions


Related issues 1 (0 open1 closed)

Copied from openQA Project (public) - action #87695: Full openQA test development, maintenance and administration from browser without the need of a local terminal size:MResolvedtinita

Actions
Actions #1

Updated by tinita 7 months ago

  • Copied from action #87695: Full openQA test development, maintenance and administration from browser without the need of a local terminal size:M added
Actions #2

Updated by okurz 7 months ago

  • Target version set to Ready
Actions #3

Updated by okurz 7 months ago

  • Status changed from New to Blocked
  • Assignee set to okurz
  • Target version changed from Ready to future

I subscribed to https://github.com/orgs/community/discussions/127083 . Let's block on that

Actions #4

Updated by okurz 6 months ago

I asked in https://matrix.to/#/!XpAJOYggtDiIfDZZBr:opensuse.org/$ps-jpbRJPTawRdS-FOGvgWNH7YQ0bEys_iE_bhBqcFs

hi guys, we observed an interesting error trying out GitHub codespaces using a Tumblweed container: https://github.com/orgs/community/discussions/127083 Trying that container just yields an error message in the user's browser session "An unexpected error occurred that requires a reload of this page.". Our internal ticket https://progress.opensuse.org/issues/161399 . Leap 15.5 works fine so we use that as workaround for now. Any idea what could cause this?

Actions #5

Updated by mpagot 6 months ago

I just tested codespace proposed in https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18324 , that is also a TW based one, and nowadays is broken in the same way:

An unexpected error occurred that requires a reload of this page.
The workbench failed to connect to the server (Error: exception was thrown by handler. exception: failed to start vs code remote server.)
Actions #6

Updated by mpagot 6 months ago

Issue in TW not to be usable for codespace is the lack of awk in the default container image

In TW

$ podman run --rm opensuse/tumbleweed:latest awk --version

Error: crun: executable file `awk` not found in $PATH: No such file or directory: OCI runtime attempted to invoke a command that was not found

In Leap

$ podman run --rm opensuse/leap:15.5 awk --version
GNU Awk 4.2.1, API: 2.0
Copyright (C) 1989, 1991-2018 Free Software Foundation......

AWK is needed by part of the codespace deployment, one of the latest part where some binary are "uploaded" in the running container to allow communication with the VScode that "host" it.

Viable solution is to change the codespace config file to get TW using a Dockerfile and then install awk as part of it (to be safe awk and tar as both are required by the codespace deployment process).

Here some "documentation" --> https://github.com/microsoft/vscode-remote-release/issues/9620
Here an example about how to fix it --> https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18324 and in particular https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18324/commits/084a5706d981dc22ca14d3ef159a8d95a4585d19

Actions #7

Updated by tinita 6 months ago

  • Description updated (diff)

Thanks @mpagot !

Discussed with @okurz .
We want to have a generic tumbleweed container working with codespaces, and build a single instance on top of that. That can also include things like os-autoinst-deps, so that people could run perltidy for example.

I updated the description.

Actions #8

Updated by tinita 6 months ago

  • Status changed from Blocked to New
  • Assignee deleted (okurz)
Actions #9

Updated by okurz 6 months ago

  • Target version changed from future to Tools - Next
Actions #10

Updated by tinita 6 months ago

  • Description updated (diff)
Actions #11

Updated by tinita 6 months ago

  • Description updated (diff)
Actions #12

Updated by okurz 6 months ago

  • Target version changed from Tools - Next to Ready
Actions #13

Updated by okurz 6 months ago

  • Target version changed from Ready to Tools - Next
Actions #14

Updated by okurz 5 months ago

  • Target version changed from Tools - Next to Ready
Actions #15

Updated by okurz 5 months ago

  • Subject changed from Use Tumbleweed again for openqa-single-instance container to Use Tumbleweed again for openqa-single-instance container size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #16

Updated by jbaier_cz 5 months ago

  • Status changed from Workable to In Progress
  • Assignee set to jbaier_cz
Actions #17

Updated by jbaier_cz 5 months ago

I created

In between the parts, the project needs to be defined in the OBS and the image needs to be build for the first time.

Actions #18

Updated by jbaier_cz 5 months ago

Apparently replace_using_package_version service needs the package inside the zypper cache during the build so a minor adjustment has to be made: https://github.com/os-autoinst/openQA/pull/5823

Actions #19

Updated by jbaier_cz 5 months ago

  • Status changed from In Progress to Feedback
Actions #20

Updated by jbaier_cz 4 months ago

  • Status changed from Feedback to Resolved

Codespaces container is in the OBS ans I was able to run codespaces from that in GitHub. Single instance container reverted to Tumbleweed and is already in OBS.

Actions

Also available in: Atom PDF