Tempest test test_container_synchronization is failed

Bug #1591175 reported by Sofiia Andriichenko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Status tracked in 10.0.x
10.0.x
Confirmed
High
Kostiantyn Danylov
8.0.x
Confirmed
High
Kostiantyn Danylov
9.x
Confirmed
High
Kostiantyn Danylov

Bug Description

Configuration:
    ISO: 9.0 mos iso #452
Settings:
Compute - QEMU.
Network - Neutron with VLAN segmentation.
Storage Backends - LVM
Additional services - Install Ironic, Install Sahara

In tab Settings->Compute check Nova quotas
In tab Settings->OpenStack Services check enable Install Ceilometer and Aodh
In tab Networks->Other check enable Neutron DVR

Nodes: controller, compute, ironic,cinder, Telemetry - MongoDB
Steps to reproduce:
    1. Deploy ISO in configuration see (Detailed bug description)
    2. Navigate to controller node
    3. Install git (use apt-get install git)
    4. Clone script to deploy rally + tempest
       # git clone https://github.com/obutenko/mos-rally-verify.git
    5. Navigate to the https://github.com/obutenko/mos-rally-verify
    6. Execute necessary steps to deploy tempest
    7. Tun test in debug mode
        #rally --debug verify start --regex tempest.api.object_storage.test_container_sync_middleware.ContainerSyncMiddlewareTest.test_container_synchronization

Expected results:
Test is passed

Actual result:
Test is Failed
(see comments)

Reproducibility:
See attachment

Workaround:
---

Impact:
---

Additional information:
Traceback (most recent call last):

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/test.py", line 158, in wrapper

    return func(*func_args, **func_kwargs)

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/api/object_storage/test_container_sync_middleware.py", line 52, in test_container_synchronization

    self._test_container_synchronization(make_headers)

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/api/object_storage/test_container_sync.py", line 110, in _test_container_synchronization

    cont, params=params)

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/services/object_storage/container_client.py", line 160, in list_container_contents

    resp, body = self.get(url, headers={})

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/lib/common/rest_client.py", line 274, in get

    return self.request('GET', url, extra_headers, headers)

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/lib/common/rest_client.py", line 641, in request

    resp, resp_body)

  File "/home/rally/.rally/tempest/for-deployment-ccd279e2-e373-430c-826b-8bd97fa9e419/tempest/lib/common/rest_client.py", line 684, in _error_checker

    raise exceptions.Unauthorized(resp_body, resp=resp)

tempest.lib.exceptions.Unauthorized: Unauthorized

Details: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>

snapshot https://drive.google.com/a/mirantis.com/file/d/0BxPLDs6wcpbDTkFsVGhlT1gtdTg/view?usp=sharing

Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :
Revision history for this message
Oleksiy Butenko (obutenko) wrote :

bug reproduced only on ci and can't reproduce manual

Changed in mos:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → MOS Swift (mos-swift)
milestone: none → 9.0
Revision history for this message
Alyona Kiseleva (akiselyova) wrote :

From Swift logs I see, that authorization really was failed. May be, tempest use incorrect token, or something like this. I'll try to find, where mistake take place.

Dina Belova (dbelova)
Changed in mos:
assignee: MOS Swift (mos-swift) → Alyona Kiseleva (akiselyova)
milestone: 9.0 → 9.0-updates
Revision history for this message
Timur Nurlygayanov (tnurlygayanov) wrote :

Ok, do we have any updates?

tags: added: move-to-9.2
Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

@Timur: Please close it as incomplete if there are no updates on how to reproduce this.

Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :

reproduced only on ci for 9.2 snapshot #430

trace:
Traceback (most recent call last):
  File "tempest/test.py", line 119, in wrapper
    return func(*func_args, **func_kwargs)
  File "tempest/api/object_storage/test_container_sync_middleware.py", line 52, in test_container_synchronization
    self._test_container_synchronization(make_headers)
  File "tempest/api/object_storage/test_container_sync.py", line 110, in _test_container_synchronization
    cont, params=params)
  File "tempest/services/object_storage/container_client.py", line 160, in list_container_contents
    resp, body = self.get(url, headers={})
  File "tempest/lib/common/rest_client.py", line 291, in get
    return self.request('GET', url, extra_headers, headers)
  File "tempest/lib/common/rest_client.py", line 664, in request
    self._error_checker(resp, resp_body)
  File "tempest/lib/common/rest_client.py", line 751, in _error_checker
    raise exceptions.Unauthorized(resp_body, resp=resp)
tempest.lib.exceptions.Unauthorized: Unauthorized
Details: <html><h1>Unauthorized</h1><p>This server could not verify that you are authorized to access the document you requested.</p></html>

Snapshot: https://drive.google.com/a/mirantis.com/file/d/0BxPLDs6wcpbDY3NDRmZCSUJpR0U/view?usp=sharing

Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

More time is needed to get this issue fixed - retargeted to 9.3

Revision history for this message
Yury Tregubov (ytregubov) wrote :

Quite stable reproduction is seen on mos10. The latest one is available on #1415 build: https://mirantis.testrail.com/index.php?/tests/view/30220349

Feel free to ask me for reproduction.

Revision history for this message
Vladimir Jigulin (vjigulin) wrote :

Probably same issue: #1555015

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.