Bug 1962604

Summary:	CNV 2.6 -> 4.8 upgrade: extra set of HPP resources when using custom CR name
Product:	Container Native Virtualization (CNV)	Reporter:	Alex Kalenyuk <akalenyu>
Component:	Storage	Assignee:	Alex Kalenyuk <akalenyu>
Status:	CLOSED ERRATA	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.8.0	CC:	cnv-qe-bugs, yadu
Target Milestone:	---
Target Release:	4.8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	hostpath-provisioner-rhel8-operator v4.8.0-14	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-27 14:32:06 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 Alex Kalenyuk 2021-05-20 10:58:31 UTC

Description of problem:
When upgrading from CNV 2.6 -> 4.8, user will get an extra set of HPP resources (2 DaemonSets acting on PVCs) if using a custom CR namae, due to recently introduced change

Version-Release number of selected component (if applicable):
CNV 2.6 -> 4.8

How reproducible:
100%

Steps to Reproduce:
1. Use a custom CR name for the HPP resource (!= 'hostpath-provisioner')
2. Upgrade to 4.8

Actual results:
An extra set of resources is created

Expected results:
Resources are upgraded

Additional info:
- This is expected due to how we handled bug 1923243 (HPP resources will now use fixed names instead of CR-dependent names)
- To solve this we will delete the user's 'old' 2.6 resources and we are guaranteed the new ones will be created

Comment 2 Kevin Alon Goldblatt 2021-06-23 14:23:21 UTC

Currently BLOCKED by https://projects.engineering.redhat.com/browse/CLOUDDST-7114.
Waiting for downstream build

Comment 4 Kevin Alon Goldblatt 2021-06-30 13:08:52 UTC

Verified with automated TC: https://code.engineering.redhat.com/gerrit/c/cnv-tests/+/245416

Comment 7 errata-xmlrpc 2021-07-27 14:32: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 (Moderate: OpenShift Virtualization 4.8.0 Images), 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/RHSA-2021:2920