Bug 1923744 - 4.6->4.7 update has pruner fail: error: unable to find the remote registry host: no managed image found
Summary: 4.6->4.7 update has pruner fail: error: unable to find the remote registry ho...
Keywords:
Status: CLOSED DUPLICATE of bug 1923993
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Oleg Bulatov
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-01 18:50 UTC by W. Trevor King
Modified: 2021-02-02 11:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-02 11:49:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description W. Trevor King 2021-02-01 18:50:27 UTC
4.6.15 -> 4.7.0-0.ci-2021-01-31-192525 update CI failed [1]

  [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial] 

with:

  Cluster did not complete upgrade: timed out waiting for the condition: Cluster operator image-registry is reporting a failure: ImagePrunerDegraded: Job has reached the specified backoff limit

Pruner logs were just [2]:

  error: unable to find the remote registry host: no managed image found

[1]: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade-4.6-stable-to-4.7-ci/1356020621175164928
[2]: https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade-4.6-stable-to-4.7-ci/1356020621175164928/artifacts/e2e-gcp-upgrade/gather-extra/artifacts/pods/openshift-image-registry_image-pruner-1612137600-rnthl_image-pruner.log

Comment 1 Oleg Bulatov 2021-02-02 11:49:02 UTC
The job has started before midnight, at midnight the cronjob was executed (4.6) and failed (because of BZ 1887010). We have fixed this problem in 4.7, but we also need to fix it in 4.6.

*** This bug has been marked as a duplicate of bug 1923993 ***


Note You need to log in before you can comment on or make changes to this bug.