Project

General

Profile

coordination #93609

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #80150: [epic] Scale out openQA: Easier openQA setup

[epic] openqa-bootstrap support on Leap 15.3

Added by okurz 4 months ago. Updated 28 days ago.

Status:
Blocked
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2021-06-07
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)
Difficulty:

Description

Unable to guess a value for .
Please use obs:///
Example: obs://server:http/openSUSE_11.3

/usr/share/openqa/script/openqa-bootstrap --help also gives no clear example on how to do this.

Acceptance criteria

  • AC1: openqa-bootstrap on Leap 15.3 from devel:openQA passes
  • AC2: openqa-bootstrap on Leap 15.3 from official repos passes
  • AC3: Automatic test of openqa-bootstrap on Leap 15.3 exists and passes

Acceptance tests

  • AT1-1: podman run --rm -it registry.opensuse.org/opensuse/leap:15.3 sh -c 'zypper -n in curl && curl -s https://raw.githubusercontent.com/os-autoinst/openQA/master/script/openqa-bootstrap | bash -x'
  • AT2-1: podman run --rm -it registry.opensuse.org/opensuse/leap:15.3 sh -c 'zypper -n in openQA-bootstrap && /usr/share/openqa/script/openqa-bootstrap'

Suggestions

  • One problem is that https://build.opensuse.org/project/show/devel:openQA shows the repository "openSUSE_Leap_15.3" but openqa-bootstrap looks for just "Leap_15.3".
  • I suggest to first ensure that openqa-bootstrap on Leap works with the "curl … | sh" way as this way we can ensure we use the most recent bootstrap script. Then ensure to provide maintenance updates to Leap to fix the version included in official repos. Or, if this turns out to be not feasible at least update http://open.qa/docs/#bootstrapping to explain that the official package within Leap can not be used. In this case at best also propose deletion of openQA packages from official Leap repos.
  • For automatic tests of openqa-bootstrap on Leap: There is already https://openqa.opensuse.org/tests?match=openqa_bootstrap on Tumbleweed. The same should be part of Leap tests as long as we have according packages within Leap

Subtasks

action #95317: openqa-bootstrap on Leap 15.3 from devel:openQA passesResolvedmkittler

action #95320: openqa-bootstrap on Leap 15.3 from official repos passesResolvedmkittler

action #95323: openqa-bootstrap support on Leap 15.3 - automatic testNew


Related issues

Blocked by openQA Project - action #91752: jenkins: Multiple missing fields and errors in configuration of openQA-in-openQAResolved2021-04-26

Copied from openQA Project - coordination #93501: openqa-bootstrap fails to guess a value for platform on Leap 15.3Resolved2021-06-07

History

#1 Updated by okurz 4 months ago

  • Copied from coordination #93501: openqa-bootstrap fails to guess a value for platform on Leap 15.3 added

#2 Updated by mkittler 3 months ago

  • Assignee set to mkittler

#3 Updated by mkittler 3 months ago

PR: https://github.com/os-autoinst/openQA/pull/3961


Note that the acceptance tests won't work because a working systemd-setup is required to run the script:

+ systemctl enable --now apache2
Created symlink /etc/systemd/system/httpd.service → /usr/lib/systemd/system/apache2.service.
Created symlink /etc/systemd/system/apache.service → /usr/lib/systemd/system/apache2.service.
Created symlink /etc/systemd/system/multi-user.target.wants/apache2.service → /usr/lib/systemd/system/apache2.service.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl enable --now openqa-webui
Created symlink /etc/systemd/system/multi-user.target.wants/openqa-webui.service → /usr/lib/systemd/system/openqa-webui.service.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ systemctl enable --now openqa-scheduler
Created symlink /etc/systemd/system/multi-user.target.wants/openqa-scheduler.service → /usr/lib/systemd/system/openqa-scheduler.service.
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
+ curl -sI http://localhost/
+ grep 200
+ sleep 3
+ curl -sI http://localhost/
+ grep 200
+ sleep 3
…

There are also further problems when using Docker:

++ hostname
/usr/share/openqa/script/configure-web-proxy: line 26: hostname: command not found
+ sed 's/#ServerName.*$/ServerName /' /etc/apache2/vhosts.d/openqa.conf.template
+ sed -i -e 's/#*.*method.*=.*$/method = Fake/' /etc/openqa/openqa.ini
+ ping -c1 download.suse.de.
bash: line 43: ping: command not found

However, these could actually considered bugs as these could be avoided by specifying the dependencies for these tools correctly.

But at least the run within Docker confirms that the fix regarding the repository works.

#4 Updated by mkittler 3 months ago

  • Status changed from Workable to In Progress

The workaround basically works but doesn't cover the internal CA yet, PR: https://github.com/os-autoinst/openQA/pull/3966

#5 Updated by mkittler 3 months ago

The PR has been merged. Apart from systemd/dbus not being available within the container AT1-1 passes now.

I suppose for AT2-1 I need to wait until the package makes it way to TW and then submit it to openSUSE:Backports:SLE-15-SP3:Update/openQA (judging by osc sm output, see https://en.opensuse.org/openSUSE:Maintenance_update_process).

#6 Updated by openqa_review 3 months ago

  • Due date set to 2021-07-02

Setting due date based on mean cycle time of SUSE QE Tools

#7 Updated by mkittler 3 months ago

  • Status changed from In Progress to Blocked

Looks like the package won't be submitted to Factory until Jenkins is fixed (see #91752).

#8 Updated by mkittler 3 months ago

  • Related to action #91752: jenkins: Multiple missing fields and errors in configuration of openQA-in-openQA added

#9 Updated by mkittler 3 months ago

  • Related to deleted (action #91752: jenkins: Multiple missing fields and errors in configuration of openQA-in-openQA)

#10 Updated by mkittler 3 months ago

  • Blocked by action #91752: jenkins: Multiple missing fields and errors in configuration of openQA-in-openQA added

#11 Updated by okurz 3 months ago

  • Status changed from Blocked to Feedback

blocker #91752 resolved

#12 Updated by mkittler 3 months ago

I've been creating: https://build.opensuse.org/request/show/901354 (which is now depending on https://build.opensuse.org/request/show/901704)

I'm not directly submitting the version from Factory because otherwise https://bugzilla.opensuse.org/show_bug.cgi?id=1187425 wouldn't be referenced in the changelog.

#13 Updated by mkittler 3 months ago

The SR has been merged but the container image is still at dd2749ac3 so AC2 isn't covered yet. I guess I'll have to wait until the container image is updated.

#14 Updated by okurz 3 months ago

IIUC we are waiting for either a fix for zypper or the updated openQA package to arrive as maintenance update in Leap 15.3

According to https://bugzilla.opensuse.org/show_bug.cgi?id=1187425#c12 we are waiting for the release of a maintenance update for zypper bringing zypper up to version >= 1.14.47 on Leap 15.3. Right now the bug mentions SRs for SLE e.g. https://build.suse.de/request/show/244090 for SLE15-SP3 but the SR is not yet accepted.

podman run --pull=always --rm -it registry.opensuse.org/opensuse/leap:15.3 /bin/sh -c "rpm -q zypper" returns

zypper-1.14.45-10.1.x86_64

so not yet the updated version. I suggest that we explain in our documentation the current limitations for openqa-bootstrap on Leap 15.3 and then wait (longer, expected weeks) for the maintenance updates to arrive

mkittler by the way, what you are doing is doing actual implementation in relation to an epic when epics should rather be the coordinating tasks and actual implementation done only in subtasks.

#15 Updated by mkittler 3 months ago

So I should have been creating a subtask before doing anything (besides "coordination")?

Btw, I don't know what I need to do so https://build.opensuse.org/package/show/openSUSE:Maintenance:16611/openQA.openSUSE_Backports_SLE-15-SP3_Update actually lands on https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3:Update/openQA so I cannot really help with the coordination part.

#16 Updated by okurz 3 months ago

mkittler wrote:

So I should have been creating a subtask before doing anything (besides "coordination")?

Yes

Btw, I don't know what I need to do so https://build.opensuse.org/package/show/openSUSE:Maintenance:16611/openQA.openSUSE_Backports_SLE-15-SP3_Update actually lands on https://build.opensuse.org/package/show/openSUSE:Backports:SLE-15-SP3:Update/openQA so I cannot really help with the coordination part.

I don't think you need to do anything for that. I suggest that we explain in our documentation the current limitations for openqa-bootstrap on Leap 15.3 and then wait (longer, expected weeks) for the maintenance updates to arrive

#17 Updated by cdywan 3 months ago

Does "wait" mean leaving this open or subtasks as Marius suggested? Asking for a friend who looks at due dates.

#18 Updated by okurz 3 months ago

let me show you …

#19 Updated by okurz 3 months ago

  • Status changed from Feedback to Blocked

created subtasks and updated, see?

#20 Updated by mkittler 2 months ago

Only the automatic test is missing now.

Also available in: Atom PDF