-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.13, 4.12, 4.11, 4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
During re-installation of NodeHealthCheck operator to another namespace was created second subscription of SelfNodeRemediation operator
Version-Release number of selected component (if applicable):
4.11, 4.12, 4.13, 4.14
How reproducible:
100%
Steps to Reproduce:
1. Install NodeHealthCheck operator in openshift-operators namespace (verified that NodeHealthCheck and SelfNodeRemediation operators were installed) 2. Uninstall NodeHealthCheck (verify that SelfNodeRemediation operator still presented) 3. Install NHC in test-remediation namespace apiVersion: v1 kind: Namespace metadata: name: test-remediation --- apiVersion: operators.coreos.com/v1 kind: OperatorGroup metadata: name: remediation-group namespace: test-remediation --- apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: node-healthcheck-operator namespace: test-remediation spec: channel: stable name: node-healthcheck-operator source: redhat-operators sourceNamespace: openshift-marketplace
Actual results:
SelfNodeRemediation subscription was created in test-remediation namespace
Expected results:
Only NodeHealthCheck subscription was created in test-remediation namespace, because SelfNodeRemediation subscription was already presented in a cluster
Additional info:
$ oc get sub -A NAMESPACE NAME PACKAGE SOURCE CHANNEL openshift-operators self-node-remediation-stable-redhat-operators-openshift-marketplace self-node-remediation redhat-operators stable test-remediation node-healthcheck-operator node-healthcheck-operator redhat-operators stable test-remediation self-node-remediation-stable-redhat-operators-openshift-marketplace self-node-remediation redhat-operators stable