Bug 2015098

Summary: image registry does not remain available during upgrade
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED ERRATA QA Contact: wewang <wewang>
Severity: high Docs Contact:
Priority: high    
Version: 4.9CC: aos-bugs, wking, xiuwang
Target Milestone: ---   
Target Release: 4.8.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-02 14:42:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2005049    
Bug Blocks:    

Comment 5 W. Trevor King 2021-10-26 01:37:33 UTC
In [1], both 'Application behind service load balancer with PDB is not disrupted' and 'Image registry remain available' had outages of ~100ms.  Perhaps that remaining disruption is an ingress/service thing, and no longer a registry thing?

[1]: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.8-e2e-azure-upgrade/1452554396645724160

Comment 6 Oleg Bulatov 2021-10-27 14:05:16 UTC
This fix should be in the version that you are upgrading from. To avoid disruptions the pods that are being deleted (old pods) should stay alive for some time until all components become aware that the pod will disappear.

4.8.0-0.ci-2021-10-21-200323 doesn't have the fix. Newer runs seems to be green.

Comment 10 errata-xmlrpc 2021-11-02 14:42:06 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 (OpenShift Container Platform 4.8.18 bug fix 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/RHBA-2021:4020