Bug 2251741
| Summary: | MCG endpoint minCount and maxCount in ocs-storagecluster are ignored | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Vijay Avuthu <vavuthu> |
| Component: | ocs-operator | Assignee: | Vineet <vbadrina> |
| Status: | CLOSED ERRATA | QA Contact: | Vijay Avuthu <vavuthu> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | unspecified | CC: | odf-bz-bot, vavuthu, vbadrina |
| Target Milestone: | --- | Keywords: | Automation, Regression |
| Target Release: | ODF 4.15.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 4.15.0-103 | Doc Type: | No Doc Update |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-03-19 15:29:14 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: | |||
live cluster: https://url.corp.redhat.com/88dccd9 Verified:
ocs-registry:4.15.0-104
2024-01-07 11:53:58 06:23:58 - MainThread - tests.conftest - INFO - Changing minimum Noobaa endpoints to 2
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.ocs.ocp - INFO - Command: patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"minCount":2}}}}' --type merge
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-storage patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"minCount":2}}}}' --type merge
2024-01-07 11:53:58 06:23:58 - MainThread - tests.conftest - INFO - Changing maximum Noobaa endpoints to 2
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.ocs.ocp - INFO - Command: patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"maxCount":2}}}}' --type merge
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc -n openshift-storage patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"maxCount":2}}}}' --type merge
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig -n openshift-storage get Pod -n openshift-storage --selector=noobaa-s3=noobaa -o yaml
2024-01-07 11:53:58 06:23:58 - MainThread - tests.conftest - INFO - Waiting for the NooBaa endpoints to stabilize. Current ready count: 1
2024-01-07 11:53:58 06:23:58 - MainThread - ocs_ci.utility.utils - INFO - Going to sleep for 30 seconds before next iteration
2024-01-07 11:54:30 06:24:28 - MainThread - ocs_ci.utility.utils - INFO - Executing command: oc --kubeconfig /home/jenkins/current-cluster-dir/openshift-cluster-dir/auth/kubeconfig -n openshift-storage get Pod -n openshift-storage --selector=noobaa-s3=noobaa -o yaml
2024-01-07 11:54:30 06:24:28 - MainThread - tests.conftest - INFO - NooBaa endpoints stabilized. Ready endpoints: 2
job: https://url.corp.redhat.com/d517e4d
logs: https://url.corp.redhat.com/f3899f4
No doc text changes as it was a regression 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 (Important: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix update), 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-2024:1383 |
Description of problem (please be detailed as possible and provide log snippests): changing the endpoint of minCount and maxCount for noobaa is not reflecting Version of all relevant components (if applicable): ocs-registry:4.15.0-69 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 2/2 Can this issue reproducible? Yes Can this issue reproduce from the UI? NA If this is a regression, please provide more details to justify this: Yes Steps to Reproduce: 1. install ocs-ci and run acceptance suite 2. failed test acse: tests/manage/mcg/test_bucket_creation.py::TestBucketCreation::test_bucket_creation[3-S3-DEFAULT-BACKINGSTORE] or chnage min and max endpoints with below commands $ oc -n openshift-storage patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"minCount":2}}}}' --type merge storagecluster.ocs.openshift.io/ocs-storagecluster patched $ oc -n openshift-storage patch storagecluster ocs-storagecluster -n openshift-storage -p '{"spec":{"multiCloudGateway":{"endpoints":{"maxCount":2}}}}' --type merge storagecluster.ocs.openshift.io/ocs-storagecluster patched Actual results: $ oc get pods --selector=noobaa-s3=noobaa NAME READY STATUS RESTARTS AGE noobaa-endpoint-5b46798df-xpqbp 1/1 Running 0 25m Expected results: end points should be 2 Additional info: $ oc get storagecluster ocs-storagecluster -o yaml | grep multi -A3 multiCloudGateway: endpoints: maxCount: 2 minCount: 2