1798487 – [CNV-2.3] Unable use use deploy from marketplace script - mismatch in HCO resource name

Bug 1798487 - [CNV-2.3] Unable use use deploy from marketplace script - mismatch in HCO resource name

Summary: [CNV-2.3] Unable use use deploy from marketplace script - mismatch in HCO res...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Container Native Virtualization (CNV)
Classification:	Red Hat
Component:	Installation
Sub Component:
Version:	2.3.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	2.3.0
Assignee:	Simone Tiraboschi
QA Contact:	Lukas Bednar
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2020-02-05 13:31 UTC by Lukas Bednar
Modified:	2020-05-28 09:41 UTC (History)
CC List:	4 users (show)
Fixed In Version:	hyperconverged-cluster-operator-container-v2.3.0-43
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-05-04 19:10:37 UTC
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	kubevirt hyperconverged-cluster-operator pull 425	0	None	closed	Fix the name of hyperconverged resource in deploy scripts	2020-05-28 09:35:44 UTC
Red Hat Product Errata	RHEA-2020:2011	0	None	None	None	2020-05-04 19:10:49 UTC

Description Lukas Bednar 2020-02-05 13:31:04 UTC

Description of problem:

https://raw.githubusercontent.com/kubevirt/hyperconverged-cluster-operator/master/deploy/deploy_marketplace.sh

Execution above script results in error:

Error from server (NotFound): hyperconvergeds.hco.kubevirt.io "hyperconverged-cluster" not found

because hyperconverged-cluster has been renamed to kubevirt-hyperconverged.


Version-Release number of selected component (if applicable):
cnv-2.3 
registry-proxy.engineering.redhat.com/rh-osbs/container-native-virtualization-hyperconverged-cluster-operator@sha256:7a9e780eb2509859ae47a5d2bb0f28a34af72076cda76364c9d6c555ff2c557b



How reproducible: 100%


Steps to Reproduce:
1. Deploy CNV-2.3 using above mentioned script
2.
3.

Actual results: Failing to finish deployment


Expected results: Successful deployment


Additional info:

[cloud-user@ocp-psi-executor ~]$ oc describe -n openshift-cnv hyperconverged   kubevirt-hyperconverged
Name:         kubevirt-hyperconverged
Namespace:    openshift-cnv
Labels:       <none>
Annotations:  <none>
API Version:  hco.kubevirt.io/v1alpha1
Kind:         HyperConverged
Metadata:
  Creation Timestamp:  2020-02-05T11:11:43Z
  Generation:          1
  Resource Version:    25488
  Self Link:           /apis/hco.kubevirt.io/v1alpha1/namespaces/openshift-cnv/hyperconvergeds/kubevirt-hyperconverged
  UID:                 a4905b35-5976-471d-9632-c642abf58fe3
Spec:
  Bare Metal Platform:  true
Status:
  Conditions:
    Last Heartbeat Time:   2020-02-05T11:11:43Z
    Last Transition Time:  2020-02-05T11:11:43Z
    Message:               Request does not match expected name (hyperconverged-cluster) and namespace (openshift-cnv)
    Reason:                InvalidRequest
    Status:                False
    Type:                  ReconcileComplete
Events:                    <none>

Comment 1 Lukas Bednar 2020-02-06 08:56:31 UTC

it worked with hyperconverged-cluster-operator-container-v2.3.0-43

Comment 2 Nelly Credi 2020-02-17 08:19:32 UTC

Please add fixed in version

Comment 5 errata-xmlrpc 2020-05-04 19:10:37 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, 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/RHEA-2020:2011

Comment 6 Simone Tiraboschi 2020-05-28 09:41:18 UTC

Removing old need info.

Note You need to log in before you can comment on or make changes to this bug.