Comment 5 for bug 1982007
Revision history for this message
| Lukas Piwowarski (lukas-piwowarski) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hi, I'm sorry but I was unable to resolve this issue. For me it came done to the fact that tempest received error code 502 (Bad gateway). I have tested both tests on my local environment (using devstack) and they worked fine. Because of that it seems to me that this is not really an issue with tempest but rather an issue with the environment.
I think it would help to see:
- tempest.conf
- Log file that contains tempest output (I couldn't find it here: https:/
What I am curious about is whether tempest contacted the correct Keystone API endpoint. If it did not make call to correct Keystone API endpoint then it is tempest issue. In contrast, if it did contact the correct Kyestone API endpoint then it is probably not tempest issue.