Comment 8 for bug 1458532

Leontiy, let me clarify how authentication works here. I will use that picture as an illustration:
https://docs.google.com/drawings/d/1Sr-ZC45-6GUSjLL0NKUPASEBwScTC9orYLJAlF2Wvck/edit?usp=sharing

Indeed, Rally creates Heat client with token, username and password, so that the client can later regenerate the token if it expires. But, when Heat client makes an API call to Heat (1st api call), it passes token only. When later Heat needs to do api call to an OpenStack component, e.g. Cinder (2nd api call), the call might fail because the token already expired. Cinder client can not regenerate the token as it does not have username/password. Hence the whole stack creation fails.

IMO, the right way to fix this is to ensure that Rally sends requests to Heat with 'fresh' tokens (not older than 10-20 minutes) and rely on Heat that it can finish stack creation in the remaining time (40-50 minutes).

I am assuming that Heat Rally tests are Heat team area and hence assigning this bug to them. Fixing tests is not release related, so I moving this bug to 7.0.