Skip to content
openstack operator image builder

Fix timing issues and hardcoded CR name in restore script #851

Sign in to view logs

Fix timing issues and hardcoded CR name in restore script

Fix timing issues and hardcoded CR name in restore script #851

Triggered via push January 29, 2026 16:42
@stuggistuggi
pushed 05ab087
backup_restore
Status Failure
Total duration 3m 57s
Artifacts –

build-openstack-operator.yaml

on: push
call-build-workflow  /  check-secrets
3s
call-build-workflow / check-secrets
call-build-workflow  /  Build openstack-operator image using buildah
3m 24s
call-build-workflow / Build openstack-operator image using buildah
call-build-workflow  /  openstack-operator-bundle
20s
call-build-workflow / openstack-operator-bundle
call-build-workflow  /  operator-index
0s
call-build-workflow / operator-index
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
call-build-workflow / openstack-operator-bundle
Error: podman exited with code 125 Error: not logged into registry.redhat.io
call-build-workflow / openstack-operator-bundle
Error: podman exited with code 125 Error: authenticating creds for "registry.redhat.io": Requesting bearer token: invalid status code from registry 403 (Forbidden)
call-build-workflow / openstack-operator-bundle
Failed to cache operator-sdk v1.41.1: ReserveCacheError: Unable to reserve cache with key operator-sdk_v1.41.1_linux_amd64_github, another job may be creating this cache.
call-build-workflow / openstack-operator-bundle
Failed to check cache for operator-sdk v1.41.1: Error: Cache service responded with 400