openSUSE Project Management Tool

Today

16:47 openQA Infrastructure action #104992 (Resolved): [virtualization][3rd party hypervisor] vmware test run failed with credential errors

The PR with tests has been merged as well.

15:18 openQA Infrastructure action #105169 (New): Pipeline of openQABot project fails with "urllib.error.HTTPError: HTTP Error 503: Service Unavailable" causing alert/notification

## Observation
* See ticket description
* Restarting helped to let the job pass
* Pipeline: https://gitlab.suse.de...

14:56 openQA Infrastructure action #96551: Persistent records of systemd journal size:S

The change is deployed but still has no effect. I tried `systemctl restart systemd-journald`, maybe that helps.

14:11 openQA Project action #105019: Make the number of previous restarts of a job more discoverable size:M

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

12:07 openQA Project action #105019 (In Progress): Make the number of previous restarts of a job more discoverable size:M

12:02 openQA Project action #105145: osd-deployment pipelines fail because ContainersNotInitialized

I don't agree with AC1 unless the job could somehow be restarted automatically as well. Otherwise someone in the team...

12:01 openQA Infrastructure action #96551: Persistent records of systemd journal size:S

Your SR isn't effective because a GitLab issue prevented the deployment pipeline to run. I retried the pipeline now: ...

10:27 openQA Project action #103287: Ensure openQA within standard repos of Leap 15.3 is working and no problem with object method "route" size:M

It is still on the old version:
```
docker run -it registry.opensuse.org/opensuse/leap:15.3 zypper info os-autoin...

10:12 openQA Project coordination #98952 (Feedback): [epic] t/full-stack.t sporadically fails "clickElement: element not interactable" and other errors

It seems stable, PR to remove retry: https://github.com/os-autoinst/openQA/pull/4463

2022-01-19

15:49 openQA Infrastructure action #104304 (Feedback): Crosscheck results of https://github.com/os-autoinst/os-autoinst#verifying-a-runtime-environment on arm-1/2/3 vs. arm-4/5 to find out if arm-4/5 are "typing stable" size:M

Still not reproducible after 60 more runs. I suppose running the fullstack test is not a way to reproduce typing issues.