OpenStack DBaaS (Trove)

During a run of the int-tests, replication tests fail because the auth-token is stale

  1. Series juno
  2. Bug #1394831
Bug #1394831 reported by Nikhil Manchanda
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Fix Released
Medium
Nikhil Manchanda
OpenStack DBaaS (Trove) 2015.1.0 "kilo"
Juno
Fix Released
Medium
Nikhil Manchanda
OpenStack DBaaS (Trove) 2014.2.3

Bug Description

Currently the replication tests use the shared dbaas-client, which uses the auth token that was created when the client was first created (when the int-tests first started running). This causes the replication tests to fail with "Unauthorized" since the auth-token can be stale.

This results in a situation like: http://logs.openstack.org/26/134126/9/check/gate-trove-functional-dsvm-mysql/e47907c/logs/screen-tr-tmgr.txt.gz which causes failures in the int-test runs.

Nikhil Manchanda (slicknik)
Changed in trove:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Nikhil Manchanda (slicknik)
milestone: none → kilo-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/136219

Changed in trove:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (master)

Reviewed: https://review.openstack.org/136219
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=500613e68f365596dcec4c0466978be409be99ee
Submitter: Jenkins
Branch: master

commit 500613e68f365596dcec4c0466978be409be99ee
Author: Nikhil Manchanda <email address hidden>
Date: Thu Nov 20 19:03:27 2014 -0800

    Ensure Replication Tests do not use a stale token

    Fixed the replication tests to re-authenticate the common test dbaas
    client in order to ensure that we do not use a stale auth_token when
    running the replication tests.

    Change-Id: I37a2a4b7dca056e84b48c66cbe3b8c8fb6a2f1db
    Closes-bug: 1394831

Changed in trove:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in trove:
status: Fix Committed → Fix Released
Revision history for this message
Alan Pevec (apevec) wrote :

Juno backport https://review.openstack.org/172337

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to trove (stable/juno)

Reviewed: https://review.openstack.org/172337
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=4579e037b971e789273082c4b42538ffa666e89e
Submitter: Jenkins
Branch: stable/juno

commit 4579e037b971e789273082c4b42538ffa666e89e
Author: Nikhil Manchanda <email address hidden>
Date: Thu Nov 20 19:03:27 2014 -0800

    Ensure Replication Tests do not use a stale token

    Fixed the replication tests to re-authenticate the common test dbaas
    client in order to ensure that we do not use a stale auth_token when
    running the replication tests.

    Change-Id: I37a2a4b7dca056e84b48c66cbe3b8c8fb6a2f1db
    Closes-bug: 1394831
    (cherry picked from commit 500613e68f365596dcec4c0466978be409be99ee)

Thierry Carrez (ttx)
Changed in trove:
milestone: kilo-1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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