Bug 1995387 - OpenStack 4.8 -> 4.9 upgrade is permafailing periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade
Summary: OpenStack 4.8 -> 4.9 upgrade is permafailing periodic-ci-openshift-release-ma...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.9
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.9.0
Assignee: Pierre Prinetti
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-19 00:24 UTC by Stephen Benjamin
Modified: 2021-10-18 17:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1996555 (view as bug list)
Environment:
Last Closed: 2021-10-18 17:47:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift release pull 21254 0 None None None 2021-08-20 09:20:40 UTC
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:47:38 UTC

Description Stephen Benjamin 2021-08-19 00:24:13 UTC 
periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade

is failing frequently in CI, see:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.9-informing#periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade


Appears to be something fundamental in the job, it can't find the openstack-installer image:

https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-openstack-upgrade/1427346583405465600


 INFO[2021-08-16T19:10:32Z] Imported release 4.9.0-0.ci-2021-08-16-124059 created at 2021-08-16 12:41:05 +0000 UTC with 148 images to tag release:latest 
INFO[2021-08-16T19:10:32Z] Acquiring leases for test e2e-openstack-upgrade 
INFO[2021-08-16T19:10:32Z] Acquired 1 lease(s) for openstack-vexxhost-quota-slice: [633a877a-119f-4400-9407-c4bcb6ce15d7] 
INFO[2021-08-16T19:10:32Z] Running multi-stage test e2e-openstack-upgrade 
INFO[2021-08-16T19:10:34Z] Running step e2e-openstack-upgrade-ipi-install-hosted-loki. 
INFO[2021-08-16T19:10:44Z] Step e2e-openstack-upgrade-ipi-install-hosted-loki succeeded after 10s. 
INFO[2021-08-16T19:10:44Z] Running step e2e-openstack-upgrade-openstack-conf-clouds. 
INFO[2021-08-16T19:40:44Z] pod didn't start running within 30m0s: 
* Container test is not ready with reason ImagePullBackOff and message Back-off pulling image "image-registry.openshift-image-registry.svc:5000/ci-op-jrl1jbgs/stable:openstack-installer"
Found 17 events for Pod e2e-openstack-upgrade-openstack-conf-clouds:
* 0x : Successfully assigned ci-op-jrl1jbgs/e2e-openstack-upgrade-openstack-conf-clouds to ip-10-0-164-54.ec2.internal
* 1x multus: Add eth0 [10.131.21.234/23] from openshift-sdn
* 1x kubelet: Container image "gcr.io/k8s-prow/entrypoint:v20210813-7f65f6f13b" already present on machine
* 1x kubelet: Started container sidecar
* 109x kubelet: Back-off pulling image "image-registry.openshift-image-registry.svc:5000/ci-op-jrl1jbgs/stable:openstack-installer"
* 3x kubelet: Error: ImagePullBackOff 
INFO[2021-08-16T19:40:44Z] Step e2e-openstack-upgrade-openstack-conf-clouds failed after 30m0s. 
INFO[2021-08-16T19:40:44Z] Running step e2e-openstack-upgrade-openstack-gather.
Comment 2 Pierre Prinetti 2021-08-23 08:23:02 UTC 
Moving to VERIFIED because the tests now execute and don't fail any more because of a missing image.

Opened Bug 1996555 to address the failing tests.
Comment 5 errata-xmlrpc 2021-10-18 17:47:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3759
Note You need to log in before you can comment on or make changes to this bug.