Bug 1907139 - HPP operator reports upgrade successful even though hostpath-provisioner pods are not upgraded
Summary: HPP operator reports upgrade successful even though hostpath-provisioner pods...
Keywords:
Status: CLOSED DUPLICATE of bug 1907138
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 2.5.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: 2.5.3
Assignee: Alexander Wels
QA Contact: Qixuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-13 09:25 UTC by Ruth Netser
Modified: 2020-12-14 14:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-14 14:17:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ruth Netser 2020-12-13 09:25:43 UTC 
Description of problem:
Upgrade CNV 2.4.4 -> 2.5.2
Bug 1907138 led to hostpath-provisioner not being upgraded.
However, HPP operator reported in its conditions that everything is fine (available=true, degraded=false, progressing=false, upgradeable=true)

Version-Release number of selected component (if applicable):
CNV 2.4.4 - > CNV 2.5.2

How reproducible:
100% (seen on one cluster)


Steps to Reproduce:
1. Upgrade CNV 2.4.4 to CNV 2.5.2
2. When upgrade is reported as completed, check all CNV pods

Actual results:
CNV upgrade is reported as completed

Expected results:
HPP operator should not report its conditions that everything is ok but indicate that the pods failed to upgrade and progressing=true

Additional info:
Comment 1 Adam Litke 2020-12-14 14:15:52 UTC 
I think there are two fixes needed:
1. Properly report upgrade failure when it occurs
2. Convert old useNamingPrefix string value to boolean automatically on upgrade
Comment 2 Adam Litke 2020-12-14 14:17:25 UTC 
Marking this as a dupe of 1907138 since the issues are tightly related and will likely be fixed in a single PR.
Comment 3 Adam Litke 2020-12-14 14:17:40 UTC 

*** This bug has been marked as a duplicate of bug 1907138 ***
Note You need to log in before you can comment on or make changes to this bug.