Bug 2173717 - Unsupported format of Transfer-Encoding header
Summary: Unsupported format of Transfer-Encoding header
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ga
: 17.1
Assignee: Lukas Piwowarski
QA Contact: Martin Kopec
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-27 18:10 UTC by Filip Hubík
Modified: 2023-08-16 01:14 UTC (History)
4 users (show)

Fixed In Version: openstack-tempest-33.0.0-1.20230308130919.1580f6f.el9ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 01:13:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1982874 0 None None None 2023-02-28 08:40:06 UTC
OpenStack gerrit 857333 0 None MERGED Remove transfer-encoding headers from test 2023-02-28 08:40:06 UTC
Red Hat Issue Tracker OSP-22707 0 None None None 2023-02-27 18:11:54 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:14:40 UTC

Description Filip Hubík 2023-02-27 18:10:15 UTC
Description of problem:

During Tempest run, tempest.api.object_storage.test_object_services.ObjectTest.test_create_object_with_transfer_encoding fails with error:

...
     Response - Headers: {'content-type': 'text/plain', 'content-length': '78', 'x-trans-id': 'tx254375a31aa74e0fb0324-0063eef5cc', 'x-openstack-request-id': 'tx254375a31aa74e0fb0324-0063eef5cc', 'date': 'Fri, 17 Feb 2023 03:34:36 GMT', 'connection': 'close', 'status': '501', 'content-location': 'http://10.0.0.138:8080/v1/AUTH_aca6d604b53e46f1b2861f493c076c70/tempest-TestContainer-870338229/tempest-TestObject-897321110'}
        Body: b'Unsupported Transfer-Coding header value specified in Transfer-Encoding header'
}}}

Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/tempest/api/object_storage/test_object_services.py", line 190, in test_create_object_with_transfer_encoding
    resp, _ = self.object_client.create_object(
  File "/usr/lib/python3.9/site-packages/tempest/lib/services/object_storage/object_client.py", line 51, in create_object
    resp, body = self.put(url, data, headers, chunked=chunked)
  File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 363, in put
    return self.request('PUT', url, extra_headers, headers, body, chunked)
  File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 720, in request
    self._error_checker(resp, resp_body)
  File "/usr/lib/python3.9/site-packages/tempest/lib/common/rest_client.py", line 893, in _error_checker
    raise exceptions.NotImplemented(resp_body, resp=resp,
tempest.lib.exceptions.NotImplemented: Got NotImplemented error
Details: b'Unsupported Transfer-Coding header value specified in Transfer-Encoding header'

Version-Release number of selected component (if applicable):
OSP17.1

Additional info:
* likely related to already reported issue: https://bugs.launchpad.net/tripleo/+bug/1982874
** possible solutions seem to be urllib bump and/or openstack-tempest fix?

Comment 5 Filip Hubík 2023-03-14 11:20:15 UTC
uc $ python -m testtools.run tempest.api.object_storage.test_object_services.ObjectTest.test_create_object_with_transfer_encoding

RHOS-17.1-RHEL-9-20230301.n.1, 32.0.0-1.20221003160712.bc12bd4.el9ost: FAIL
RHOS-17.1-RHEL-9-20230301.n.1, 33.0.0-1.20230308130919.1580f6f.el9ost manually installed on top of^: PASS

Fix verified. To be unskipped in CI asap.

Comment 13 errata-xmlrpc 2023-08-16 01:13:59 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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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/RHEA-2023:4577


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