Bug 1917252 - [Backport][4.6] Too strict Content-Length header check refuses valid upload requests
Summary: [Backport][4.6] Too strict Content-Length header check refuses valid upload r...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.6
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: ---
: OCS 4.6.4
Assignee: Nimrod Becker
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On: 1902685
Blocks: 1915336
TreeView+ depends on / blocked
 
Reported: 2021-01-18 08:09 UTC by Michal Minar
Modified: 2023-09-15 00:58 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of: 1902685
Environment:
Last Closed: 2021-04-08 10:29:00 UTC
Embargoed:


Attachments (Terms of Use)
log from the successful DI backup job to 4.6.6 NooBaa (12.15 KB, text/plain)
2021-03-25 19:13 UTC, Michal Minar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-core pull 6409 0 None closed Backport to 5.6: Fix content-length header check 2021-03-15 15:38:03 UTC
Red Hat Product Errata RHBA-2021:1134 0 None None None 2021-04-08 10:29:28 UTC

Comment 8 Raz Tamir 2021-03-15 09:23:43 UTC
Hey Michal,

I'm approving this BZ to be backported to 4.6.4 based on your help to verify it once there.
@miminar thanks for your help

Comment 15 Elad 2021-03-24 14:04:15 UTC
Hi Michal, 

This bug is now fixed with v4.6.4-311.ci. Would you be able to help with the verification?

Thanks

Comment 16 Michal Minar 2021-03-24 14:12:42 UTC
Hi Elad,

I'm working on it. I should have the results tomorrow.

Best regards,
Michal

Comment 17 Michal Minar 2021-03-25 19:13:28 UTC
Created attachment 1766401 [details]
log from the successful DI backup job to 4.6.6 NooBaa

The result of: `oc logs -c dlog-admin default-tbm6xvh-backup-dlog-q4fgc`

Comment 18 Michal Minar 2021-03-25 19:25:05 UTC
Works like a charm.

    # oc get voracluster.sap.com -o json | jq '.items[] | .spec.version'
    {
      "component": "3.1.7",
      "package": "3.1.21"
    }
    # oc get datahubs.installers.datahub.sap.com -o json | jq -r '.items[] | .spec.package'
    3.1.21
    # oc get pods -nsdi --sort-by='{.metadata.creationTimestamp}' | grep backup | tail -n 6
    default-tbm6xvh-backup-hana-v2b7z                                 0/2     Completed   0          11m
    datahub-periodic-backup-1616699640-2vzxh                          0/1     Completed   0          4m45s
    default-v6go3b9-backup-vrep-layer-snapshot-wvlzk                  0/1     Completed   0          4m41s
    default-v6go3b9-backup-hana-rxq7q                                 0/2     Completed   0          4m41s
    default-v6go3b9-backup-k8s-sdlxh                                  0/1     Completed   0          4m41s
    default-v6go3b9-backup-dlog-x6pk9                                 0/2     Completed   0          4m40s
    # oc get -n openshift-marketplace catalogsource/ocs-catalogsource -o json | jq -r '.spec.image'
    quay.io/rhceph-dev/ocs-registry:latest-stable-4.6.4
    # oc get -n openshift-storage subscription/ocs-operator -o json | jq '.spec'
    {
      "channel": "stable-4.6",
      "installPlanApproval": "Automatic",
      "name": "ocs-operator",
      "source": "ocs-catalogsource",
      "sourceNamespace": "openshift-marketplace",
      "startingCSV": "ocs-operator.v4.6.4-316.ci"
    }

Looks good to me. Thanks!
Over to you Raz.

Comment 19 Elad 2021-03-29 14:42:06 UTC
Thanks!

Comment 23 errata-xmlrpc 2021-04-08 10:29:00 UTC
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 (Red Hat OpenShift Container Storage 4.6.4 container 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/RHBA-2021:1134

Comment 24 Red Hat Bugzilla 2023-09-15 00:58:27 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.