-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
ACM 2.10.0
-
False
-
None
-
False
-
Not Selected
- Proposed title of this feature request
Configure clustercurator to detect the version installed in a gitops model
2. What is the nature and description of the request?
This RFE is related to this bug ACM-12926
If we recreate a clusterCurator which was finished before with the same desiredUpdate ,then it will crash by a panic. :
oc logs curator-job-xxxxx-xxxxx -c upgrade-cluster
I0724 15:57:22.192543 1 curator.go:86] Mode: upgrade-cluster Cluster
I0724 15:57:22.397413 1 curator.go:111] Found clusterCurator resource "idpcloudpre1" ✓
I0724 15:57:23.193869 1 hive.go:258] * Initiate Upgrade
I0724 15:57:23.193886 1 hive.go:259] Looking up managedclusterinfo idpcloudpre1
I0724 15:57:23.199175 1 hive.go:552] kubevendor: OpenShift
E0724 15:57:23.404998 1 curator.go:407] Provided version is not valid
panic: Provided version is not valid [recovered]
panic: Provided version is not valid
goroutine 1 [running]:
main.curatorRun.func1()
/remote-source/app/cmd/curator/curator.go:150 +0x23d
panic({0x175fe20?, 0xc00012d020?})
/usr/lib/golang/src/runtime/panic.go:914 +0x21f
main.curatorRun(0x0?, {0x1c4e020?, 0xc0002635f0}, {0x7ffd1f851e1d, 0xc}, {0xc0002e2010, 0xc})
/remote-source/app/cmd/curator/curator.go:408 +0x2bb6
main.main()
/remote-source/app/cmd/curator/curator.go:66 +0x1bf
3. Why does the customer need this? (List the business requirements here)
The idea is that the update itself detects the version it is in and in case it is already in the desired version does nothing, or sends a message informing about it and that this is compatible with a gitops model, adding annotations or labels would not be practical for this model.
4. List any affected packages or components.
ACM
