Bug 2102349

Summary: [upgrade] 4.10.3->4.11.0 upgrade is not progressing due to tekton-tasks-operator
Product: Container Native Virtualization (CNV) Reporter: Debarati Basu-Nag <dbasunag>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED NOTABUG QA Contact: Natalie Gavrielov <ngavrilo>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.11.0CC: cnv-qe-bugs, dholler, fmatouschek, ocohen, stirabos, ycui
Target Milestone: ---   
Target Release: ---   
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: 2022-06-30 13:54:43 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:
Bug Depends On:    
Bug Blocks: 2088472    

Comment 2 Dominik Holler 2022-06-30 11:23:32 UTC
In the attached hco operator log I see "Cluster type = openshift","version":"4.10.20" in the beginning, and later "Start upgrading from version 4.10.3 to version 4.11.0".
In the Steps to Reproduce is written "1. Run cnv upgrade from 4.10.3->4.11.0"
Can you please help me to understand the scenario?
Is it expected that CNV 4.11 is working on an openshift 4.10.20 cluster?
Does other operators work, or is the tekton-tasks-operator the first operator which is updated and already fails?

Is this issue reproducible during an upgrade from openshift 4.10 with cnv 4.10 to openshift 4.11, which will trigger the upgrade to cnv 4.11 after the upgrade to openshift 4.11?

Comment 5 Debarati Basu-Nag 2022-06-30 12:40:36 UTC
I just checked. This scheduled upgrade job is wrong. It is supposed to start with OCP 4.11 -> install cnv 4.10 -> install knmstate 4.11 -> upgrade CNV to 4.11. It is currently not doing this. So this is not a bug. I will close it.

Comment 6 Dominik Holler 2022-06-30 13:24:02 UTC
Is this bug still open by intention, or can it be closed?

Comment 7 Oren Cohen 2022-06-30 13:54:43 UTC
closing as "not a bug"

Comment 8 Red Hat Bugzilla 2023-09-15 01:56:29 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days