action #132692
closed
Support SUMA engineers to setup a SUMA containers test & release pipeline
Added by jlausuch 12 months ago.
Updated 7 months ago.
- Status changed from New to In Progress
- Assignee set to ph03nix
Still waiting for Maurizio
Had a short session with Maurizio, we agreed that I will do the VRs and share the results in the PR.
Maurizio shared the container location on registry.suse.de with me and I will now perform a bunch of VRs.
For my future self:
openqa-cli api --host http://duck-norris.qe.suse.de -X POST isos ARCH=x86_64 DISTRI=sle BUILD=petrosilius GROUP=0 VERSION=15-SP5 FLAVOR=BCI-Updates CONTAINERS_UNTESTED_IMAGES=1 CONTAINER_SUMA=image BCI_IMAGE_NAME=suma-proxy-squid CONTAINER_IMAGE_TO_TEST=registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-squid CASEDIR=https://github.com/m4u9/os-autoinst-distri-opensuse.git#suma-containers2
proxy-helm needs helm
.
proxy-helm: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/charts/suse/manager/4.3/proxy-helm
The other images need podman
.
proxy-httpd-image: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-httpd
proxy-salt-broker-image: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-salt-broker
proxy-squid-image: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-squid
proxy-ssh-image: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-ssh
proxy-tftpd-image: registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/proxy-tftpd
#!/bin/bash -e
oqa_cli="openqa-cli"
IMAGES="proxy-httpd-image proxy-salt-broker-image proxy-squid-image proxy-ssh-image proxy-tftpd-image"
# suma-proxy-helm is special
$oqa_cli api --host http://duck-norris.qe.suse.de -X POST isos ARCH=x86_64 DISTRI=sle BUILD=suma-proxy-helm GROUP=0 VERSION=15-SP5 FLAVOR=BCI-Updates CONTAINERS_UNTESTED_IMAGES=1 CONTAINER_SUMA=image BCI_IMAGE_NAME=suma-proxy-helm CONTAINER_IMAGE_TO_TEST=registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/charts/suse/manager/4.3/proxy-helm CASEDIR=https://github.com/m4u9/os-autoinst-distri-opensuse.git#suma-containers2
for image in $IMAGES
do
$oqa_cli api --host http://duck-norris.qe.suse.de -X POST isos ARCH=x86_64 DISTRI=sle BUILD=suma-$image GROUP=0 VERSION=15-SP5 FLAVOR=BCI-Updates CONTAINERS_UNTESTED_IMAGES=1 CONTAINER_SUMA=image BCI_IMAGE_NAME=suma-$image CONTAINER_IMAGE_TO_TEST=registry.suse.de/suse/sle-15-sp4/update/products/manager43/update/cr/containers/suse/manager/4.3/$image CASEDIR=https://github.com/m4u9/os-autoinst-distri-opensuse.git#suma-containers2
done
I don't see any scheduled jobs in https://openqa.suse.de/group_overview/516?limit_builds=50&limit_builds=10. Looking at the latest pipeline on the crb, I see the following:
DEBUG:urllib3.connectionpool:https://openqa.suse.de:443 "POST /api/v1/isos?DISTRI=sle&VERSION=15-SP4&ARCH=x86_64&FLAVOR=Container-Image-Updates&BUILD=15-SP4_37.28&_GROUP_ID=516&CONTAINER_IMAGE_BUILD=37.28&CONTAINERS_UNTESTED_IMAGES=1&PUBLIC_CLOUD_TOOLS_HDD=publiccloud_tools_0057.qcow2&RETRY=1&CONTAINER_IMAGE_TO_TEST=registry.suse.de%2Fsuse%2Fsle-15-sp4%2Fupdate%2Fproducts%2Fmanager43%2Fupdate%2Fcr%2Ftotest%2Fcontainers%2Fsuse%2Fmanager%2F4.3%2Fproxy-httpd%3Alatest&CONTAINER_SUMA=image HTTP/1.1" 404 131
SUMA-proxy-httpd-x86_64 - error: ('POST', 'https://openqa.suse.de/api/v1/isos?DISTRI=sle&VERSION=15-SP4&ARCH=x86_64&FLAVOR=Container-Image-Updates&BUILD=15-SP4_37.28&_GROUP_ID=516&CONTAINER_IMAGE_BUILD=37.28&CONTAINERS_UNTESTED_IMAGES=1&PUBLIC_CLOUD_TOOLS_HDD=publiccloud_tools_0057.qcow2&RETRY=1&CONTAINER_IMAGE_TO_TEST=registry.suse.de%2Fsuse%2Fsle-15-sp4%2Fupdate%2Fproducts%2Fmanager43%2Fupdate%2Fcr%2Ftotest%2Fcontainers%2Fsuse%2Fmanager%2F4.3%2Fproxy-httpd%3Alatest&CONTAINER_SUMA=image', 404)
ERROR:root:('POST', 'https://openqa.suse.de/api/v1/isos?DISTRI=sle&VERSION=15-SP4&ARCH=x86_64&FLAVOR=Container-Image-Updates&BUILD=15-SP4_37.28&_GROUP_ID=516&CONTAINER_IMAGE_BUILD=37.28&CONTAINERS_UNTESTED_IMAGES=1&PUBLIC_CLOUD_TOOLS_HDD=publiccloud_tools_0057.qcow2&RETRY=1&CONTAINER_IMAGE_TO_TEST=registry.suse.de%2Fsuse%2Fsle-15-sp4%2Fupdate%2Fproducts%2Fmanager43%2Fupdate%2Fcr%2Ftotest%2Fcontainers%2Fsuse%2Fmanager%2F4.3%2Fproxy-httpd%3Alatest&CONTAINER_SUMA=image', 404)
INFO:root:Processing SUMA-proxy-salt-broker (1 architectures)
INFO:root:Processing SUMA-proxy-salt-broker-x86_64
Now checking why this one in throwing a 404.
- Status changed from In Progress to Feedback
I see pending test runs for
- SUMA-proxy-tftpd
- SUMA-proxy-ssh
- SUMA-proxy-squid
- SUMA-proxy-salt-broker
- SUMA-proxy-httpd
Gonna have a look and if they all pass then we can consider this job as done.
- Status changed from Feedback to Resolved
ph03nix wrote in #note-19:
I see pending test runs for
- SUMA-proxy-tftpd
- SUMA-proxy-ssh
- SUMA-proxy-squid
- SUMA-proxy-salt-broker
- SUMA-proxy-httpd
Gonna have a look and if they all pass then we can consider this job as done.
I see https://openqa.suse.de/tests/overview?groupid=516&version=15-SP4&build=15-SP4_40.17&distri=sle as a build or suma-proxy-httpd
, but not for other containers.
For the others: I checked https://gitlab.suse.de/qac/container-release-bot/-/jobs/2033126
INFO:root:SUMA-proxy-tftpd-x86_64: Build (CR|CR:ToTest|Release): 30.16 | 30.16 | 30.16
INFO:root:SUMA-proxy-ssh-x86_64: Build (CR|CR:ToTest|Release): 30.14 | 30.14 | 30.14
INFO:root:SUMA-proxy-squid-x86_64: Build (CR|CR:ToTest|Release): 39.15 | 39.15 | 39.15
INFO:root:SUMA-proxy-salt-broker-x86_64: Build (CR|CR:ToTest|Release): 30.18 | 30.18 | 30.18
They are all up-to-date. I think we can close the ticket as resolved.
Also available in: Atom
PDF