Bug 2069759
| Summary: | Ramen needs to improve reporting of status when s3 gateway is down | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Pratik Surve <prsurve> |
| Component: | odf-dr | Assignee: | rakesh <rgowdege> |
| odf-dr sub component: | ramen | QA Contact: | krishnaram Karthick <kramdoss> |
| Status: | ASSIGNED --- | Docs Contact: | |
| Severity: | unspecified | ||
| Priority: | low | CC: | kramdoss, kseeger, mmuench, muagarwa, odf-bz-bot, rgowdege, sheggodu, srangana |
| Version: | 4.10 | Flags: | kramdoss:
needinfo+
|
| 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: | 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: | |||
Tracked upstream in: https://github.com/RamenDR/ramen/issues/749 |
Description of problem (please be detailed as possible and provide log snippests): Ramen needs to improve reporting of status when s3 gateway is down Version of all relevant components (if applicable): OCP version:- 4.10.0-0.nightly-2022-03-23-153617 ODF version:- 4.10.0-208 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? 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? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: status: conditions: - lastTransitionTime: "2022-03-29T15:20:42Z" message: "DRPolicy not valid s3profile-vmware-dccp-one-ocs-storagecluster: failed to list objects in bucket odrbucket-49ce0a14a91e:/odr-policy-east-west-rpo-5m, SerializationError: failed to unmarshal error message\n\tstatus code: 504, request id: , host id: \ncaused by: UnmarshalError: failed to unmarshal error message\n\t00000000 \ 3c 68 74 6d 6c 3e 3c 62 6f 64 79 3e 3c 68 31 3e |<html><body><h1>|\n00000010 \ 35 30 34 20 47 61 74 65 77 61 79 20 54 69 6d 65 |504 Gateway Time|\n00000020 \ 2d 6f 75 74 3c 2f 68 31 3e 0a 54 68 65 20 73 65 |-out</h1>.The se|\n00000030 \ 72 76 65 72 20 64 69 64 6e 27 74 20 72 65 73 70 |rver didn't resp|\n00000040 \ 6f 6e 64 20 69 6e 20 74 69 6d 65 2e 0a 3c 2f 62 |ond in time..</b|\n00000050 \ 6f 64 79 3e 3c 2f 68 74 6d 6c 3e 0a |ody></html>.|\n\ncaused by: expected element type <Error> but have <html>" observedGeneration: 4 reason: Error status: "False" type: Available - lastTransitionTime: "2022-03-25T07:14:38Z" message: Ready observedGeneration: 4 reason: Success status: "True" type: PeerReady Expected results: status should be formatted to user readable format Additional info: