Bug 1990624
| Summary: | noobaa stuck trying to show the Objects in Bucket via UI | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | khover |
| Component: | Multi-Cloud Object Gateway | Assignee: | Nimrod Becker <nbecker> |
| Status: | CLOSED WONTFIX | QA Contact: | Raz Tamir <ratamir> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.7 | CC: | assingh, etamir, hnallurv, khover, nbecker, ocs-bugs, odf-bz-bot |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-09 12:55:12 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: | |||
Description of problem (please be detailed as possible and provide log snippests): OCS case # 02992513 noobaa stuck trying to show the Objects in Bucket via UI 2021-08-05T15:43:06.397087209Z ESC[32mAug-5 15:43:06.396ESC[35m [WebServer/36] ESC[31m[ERROR]ESC[39m CONSOLE:: RPC._on_request: ERROR srv object_api.list_objects_admin reqid 762@wss://noobaa-mgmt-opens hift-storage.apps.ocplab.ar.bsch(ujv38r8f4.1p) connid ws://[::ffff:10.128.2.1]:42636/(1fnm34bzni) TypeError: Cannot read property 'endsWith' of null 2021-08-05T15:43:06.397087209Z at should_proxy (/root/node_modules/noobaa-core/src/util/http_utils.js:365:52) 2021-08-05T15:43:06.397087209Z at _get_http_agent (/root/node_modules/noobaa-core/src/util/http_utils.js:407:30) 2021-08-05T15:43:06.397087209Z at Object.get_unsecured_agent (/root/node_modules/noobaa-core/src/util/http_utils.js:389:12) 2021-08-05T15:43:06.397087209Z at Object.get_signed_url (/root/node_modules/noobaa-core/src/util/cloud_utils.js:39:31) 2021-08-05T15:43:06.397087209Z at /root/node_modules/noobaa-core/src/server/object_services/object_server.js:1213:49 2021-08-05T15:43:06.397087209Z at arrayMap (/root/node_modules/noobaa-core/node_modules/lodash/lodash.js:639:23) 2021-08-05T15:43:06.397087209Z at Function.map (/root/node_modules/noobaa-core/node_modules/lodash/lodash.js:9580:14) 2021-08-05T15:43:06.397087209Z at Object.list_objects_admin (/root/node_modules/noobaa-core/src/server/object_services/object_server.js:1203:28) 2021-08-05T15:43:06.397087209Z at runMicrotasks (<anonymous>) 2021-08-05T15:43:06.397087209Z at processTicksAndRejections (internal/process/task_queues.js:93:5) 2021-08-05T15:43:06.545002490Z ESC[32mAug-5 15:43:06.544ESC[35m [BGWorkers/32] ESC[36m [L0]ESC[39m core.server.bg_services.mirror_writer:: no buckets with mirror policy. nothing to do 2021-08-05T15:43:06.546034091Z ESC[32mAug-5 15:43:06.545ESC[35m [WebServer/36] ESC[36m [L0]ESC[39m core.server.node_services.nodes_monitor:: could not find node for root path, taking the first in the list. drives = [object Object] 2021-08-05T15:43:06.559725354Z ESC[32mAug-5 15:43:06.559ESC[35m [WebServer/36] ESC[36m [L0]ESC[39m core.server.object_services.md_store:: find_objects: { bucket: 60ff0e516287dc002a973dc6, deleted: ESC[1mnullESC[22m, version_past: ESC[1mnullESC[22m, delete_marker: ESC[1mnullESC[22m } Version of all relevant components (if applicable): ocs-operator.v4.7.2 OpenShift Container Storage 4.7.2 Succeeded quay-operator.v3.5.4 Red Hat Quay 3.5.4 quay-operator.v3.5.3 Succeeded noobaa version to 5.7.0 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)? Can this issue reproducible? Unsure Can this issue reproduce from the UI? Happening currently in dev env 4.7.2 and same behavior Prod env (OCS 4.6) If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: