Tempest failures - testtools.matchers._impl.MismatchError: content-length header does not exist'

[Larry Michel]

We're seeing some of the Tempest swift test fail due to missing content-header which is impacting the Tempest failure rate for builds with the NexentaEdge services. Tempest is requiring the content-header to be returned in the object storage tests.

It's not clear whether this is part of enforcing RFC 7230 as described in bug 1536251 but seems to be related nonetheless. We need to investigate whether this is valid requirement and if so, can this requirement be addressed?

Here's example traceback from Tempest:

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    b'Traceback (most recent call last):'
    b' File "/var/lib/tempest/tempest-11.0.0/tempest/tempest/api/object_storage/test_account_services.py", line 240, in test_list_account_metadata'
    b" self.assertHeaders(resp, 'Account', 'HEAD')"
    b' File "/var/lib/tempest/tempest-11.0.0/tempest/tempest/api/object_storage/base.py", line 95, in assertHeaders'
    b' target, method))'
    b' File "/var/lib/tempest/tempest-11.0.0/tempest/.tox/smoke/lib/python3.4/site-packages/testtools/testcase.py", line 498, in assertThat'
    b' raise mismatch_error'
    b'testtools.matchers._impl.MismatchError: content-length header does not exist'
    b''