Bug 1946244 - Providing an invalid imageSetRef in clusterdeployment resource does not result in error to operator
Summary: Providing an invalid imageSetRef in clusterdeployment resource does not resu...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: rhacm-2.2.3
Assignee: cahl
QA Contact: Hui Chen
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-05 13:53 UTC by Lars Kellogg-Stedman
Modified: 2022-01-09 04:38 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-05 19:56:40 UTC
Target Upstream Version:
Embargoed:
ming: rhacm-2.2.z+
juhsu: rhacm-2.3+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 11175 0 None None None 2021-04-05 22:19:00 UTC

Description Lars Kellogg-Stedman 2021-04-05 13:53:07 UTC 
Ran into this with a bare metal install using ACM 2.2.0.

It is possible to submit a clusterdeployment with a missing or invalid imageSetRef value. This will cause the cluster install to fail, but the UI provides no feedback to the operator indicating the nature of the failure.

We eventually discovered the source of the problem by inspecting the status field of the clusterdeployment resource, but it would have saved us time and frustration if this problem was exposed in the ACM UI.
Comment 1 cahl 2021-04-08 20:09:03 UTC 
We are always looking for feedback on how to improve the product so thanks for submitting this.

Can you give me a bit more detail for the recreate scenario?  How were you creating the invalid imageSetRef?

What did you see on the UI, do you have a screen capture?
Comment 2 Scott Berens 2021-04-19 14:47:07 UTC 
fixed in 2.2.3 and 2.3
Note You need to log in before you can comment on or make changes to this bug.