Bug 1884380

Summary: [4.5 upgrade]registry is not accessible for over 1 min during upgrade
Product: OpenShift Container Platform Reporter: Hongkai Liu <hongkliu>
Component: Image RegistryAssignee: Oleg Bulatov <obulatov>
Status: CLOSED DEFERRED QA Contact: Wenjing Zheng <wzheng>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs
Target Milestone: ---Keywords: Upgrades
Target Release: 4.7.0   
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: 2020-10-22 11:47:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hongkai Liu 2020-10-01 19:58:27 UTC
Description of problem:
During the upgrade from 4.5.13 to 4.5.14, our blackbox probe failed over 1 min.
The upgrade is successful.

Here is the alert:
https://coreos.slack.com/archives/CHY2E1BL4/p1601539296044100

Version-Release number of selected component (if applicable):


How reproducible:
It is the 2nd time it happened to buildl01 (an OCP cluster in CI infra).

Is it expected behaviour?

I will upload must-gather later.

Comment 2 Oleg Bulatov 2020-10-02 20:31:40 UTC
Is the probe a part of OpenShift? If not, how does it look like?

Comment 4 Oleg Bulatov 2020-10-22 11:47:58 UTC
Apparently we never checked how the registry behaves during upgrades. Moving to Jira for further investigation: https://issues.redhat.com/browse/IR-152