Bug 1973686

Summary: single-node upgrade: some controller might go unavailable
Product: OpenShift Container Platform Reporter: Fabio Bertinatto <fbertina>
Component: Test FrameworkAssignee: Devan Goodwin <dgoodwin>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: aos-bugs, ccoleman, dgoodwin, fbertina, jsafrane, pmuller, wduan, wking
Target Milestone: ---Keywords: Upgrades
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: 1940940 Environment:
Last Closed: 2022-02-02 18:43:20 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: 1940940    
Bug Blocks:    

Comment 1 Petr Muller 2021-10-19 09:53:48 UTC
Moving to Test Framework (component for OCP tests/ CI jobs) as discussed via Slack

Comment 2 Devan Goodwin 2021-11-09 14:26:44 UTC
Fabio could you carry this fix forward to the target release this was cloned for?

Comment 3 Fabio Bertinatto 2021-11-10 14:22:30 UTC
@Devan, which fix do you mean?

This ticket is about allowing single-node upgrade e2e jobs to tolerate operators going unavailable.

Comment 4 Devan Goodwin 2021-11-17 14:36:02 UTC
Fabio sorry we thought this was a clone to have a fix backported.

Do you have anyone planning to look at this change?

Comment 5 Fabio Bertinatto 2021-11-18 14:21:49 UTC
@Devan, no problem, thanks for the reply.

We aren't not planning to look into this change. We created this ticket and assigned it to Test Infrastructure team hoping someone more familiar with CI would adjust the single-node upgrade jobs to tolerate operators going Available=false. Apparently it was agreed on Slack that this ticket belongs to Test Framework team.

Just to give you more context, in the description of this ticket there's an explanation of why I think Available=false operators is OK in SNO upgrade jobs. Specifically, IMO the following test is not useful in those jobs:

> should not change condition/Available 

I'm assigning the ticket back to you, but feel free to reassign it or close it if you folks don't agree with this change.