QA » openQA Project

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.

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).

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.

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.

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.

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.

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

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

let me show you …

Only the automatic test is missing now.