CI/scenario004: configuring tempest when ceph-rgw is deployed doesn't work

Bug #1711198 reported by Emilien Macchi on 2017-08-16
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
High
Arx Cruz

Bug Description

When trying to configure tempest on scenario004, it doesn't work because tempest-config tool tries to talk with Swift API but the actual endpoint is Ceph RGW API:

http://logs.openstack.org/13/491113/2/check/gate-tripleo-ci-centos-7-scenario004-multinode-oooq/6c61bd9/logs/undercloud/home/jenkins/tempest_output.log.txt.gz#_2017-08-15_04_25_47

We need to make tempest-config smart enough to understand that object-store tests should not be enabled if Ceph RGW is enabled, and we should check some Swift API resource if we want to enable it (like healthcheck).

Tags: ci Edit Tag help
Changed in tripleo:
assignee: nobody → Arx Cruz (arxcruz)
Arx Cruz (arxcruz) wrote :

You just need to pass object-storage-feature-enabled.discoverability to False in order to fix it.
The test_boot_volume_pattern will fail because cinder isn't deployed in scenario004. There's a bug in tempest that doesn't check for cider before run the test.

Changed in tripleo:
milestone: pike-rc1 → pike-rc2
Arx Cruz (arxcruz) wrote :
Changed in tripleo:
status: Triaged → Fix Released
status: Fix Released → In Progress
Emilien Macchi (emilienm) wrote :

Closing it, we know it works now. Thanks for the work done!

Changed in tripleo:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers