Several tempest tests for heat are failed

Bug #1605563 reported by Sofiia Andriichenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Won't Fix
High
Oleksii Chuprykov

Bug Description

Detailed bug description:
9.1 snapshot #36
test_acl
test_created_containers
test_metadata
test_created_resource

Configuration:
Settings:
Storage Backends - Ceph RBD for volumes (Cinder), Ceph RBD for ephemeral volumes (Nova), Ceph RBD for images (Glance), Ceph RadosGW for objects (Swift API)
Additional services - 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
In tab Settings->Security check enable TLS for OpenStack public endpoints, HTTPS for Horizon

Nodes: controller, compute, Ceph, 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.orchestration.stacks.test_swift_resources.SwiftResourcesTestJSON.test_acl

Expected results:
Test is passed

Actual result:
Test is Failed
(see comments)

Reproducibility:
See attachment

Workaround:
---

Impact:
---

Description of the environment:
See (Detailed bug description)

Additional information:
Trace:

Traceback (most recent call last):

  File "/home/rally/.rally/tempest/for-deployment-65e9b809-3914-4369-8a01-71373cf27f1d/tempest/test.py", line 273, in setUpClass

    six.reraise(etype, value, trace)

  File "/home/rally/.rally/tempest/for-deployment-65e9b809-3914-4369-8a01-71373cf27f1d/tempest/test.py", line 266, in setUpClass

    cls.resource_setup()

  File "/home/rally/.rally/tempest/for-deployment-65e9b809-3914-4369-8a01-71373cf27f1d/tempest/api/orchestration/stacks/test_swift_resources.py", line 56, in resource_setup

    cls.client.wait_for_stack_status(cls.stack_id, 'CREATE_COMPLETE')

  File "/home/rally/.rally/tempest/for-deployment-65e9b809-3914-4369-8a01-71373cf27f1d/tempest/services/orchestration/json/orchestration_client.py", line 174, in wait_for_stack_status

    stack_status_reason=body['stack_status_reason'])

tempest.exceptions.StackBuildErrorException: Stack 226190c5-a149-4143-be43-661e425f2957 is in CREATE_FAILED status due to 'Resource CREATE failed: ClientException: resources.SwiftContainerWebsite: Container PUT failed: https://public.fuel.local:8080/swift/v1/tempest-heat-419345149-SwiftContainerWebsite-g4fjewr3isg5 401 Unauthorized AccessDenied'

Tags: area-heat
Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :
description: updated
Changed in mos:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → MOS Heat (mos-heat)
Revision history for this message
Sofiia Andriichenko (sandriichenko) wrote :
Revision history for this message
Oleksii Chuprykov (ochuprykov) wrote :

This is because of reauthentication_auth_method = trusts in heat.conf. Without this option everything is ok. It seems, that radosgw can't work with trusted tokens , and we use exactly these tokens if reauthentication_auth_method set to trusts while interacting with other services.
Filed another bug https://bugs.launchpad.net/mos/+bug/1610972 for ceph team.

Changed in mos:
assignee: MOS Heat (mos-heat) → Oleksii Chuprykov (ochuprykov)
Revision history for this message
Oleksii Chuprykov (ochuprykov) wrote :

As explained here https://bugs.launchpad.net/mos/+bug/1610972, current version of RadosGW in MOS9.0 doesn't support keystone v3 therefore can't work with trust tokens. We should run heat without reauthentication_auth_method = trusts. Filed bug for fuel team to turn of reauthentication https://bugs.launchpad.net/fuel/+bug/1611031 .
As we don't plan to ship new version of RadosGW with MOS9.0, I set it to Won't Fix.

Changed in mos:
status: Confirmed → Won't Fix
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.