Grenade job fails to get tempest config
Bug #1650482 reported by
Valeriy Ponomaryov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Critical
|
Valeriy Ponomaryov |
Bug Description
Recent commit [1] to grenade project changed logic of getting tempest config in unsafe way.
And now our grenade job fails to get tempest config.
Logs:
Changed in manila: | |
importance: | Undecided → Critical |
assignee: | nobody → Valeriy Ponomaryov (vponomaryov) |
description: | updated |
Changed in manila: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/411796 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=3ede2d1c489 62654ba187ef578 81999f2fedef0e
Committed: https:/
Submitter: Jenkins
Branch: master
commit 3ede2d1c4896265 4ba187ef5788199 9f2fedef0e
Author: vponomaryov <email address hidden>
Date: Fri Dec 16 10:45:50 2016 +0200
[Grenade] Do not run tempest tests
Since tempest is not used in manila grenade logic skip run of its
tests.
Change-Id: I6c45448ec286fe 6c365b4e9edcce5 6501e5c87bd
Closes-Bug: #1650482