glusterfs driver CI failing on maintenance branches due to incompatible tempest version
Bug #1524642 reported by
Csaba Henk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack-plugin-glusterfs |
Fix Released
|
High
|
Csaba Henk |
Bug Description
This bug is essentially https:/
The fix, https:/
We need a branch-aware conditional tempest checkout.
Changed in devstack-plugin-glusterfs: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Csaba Henk (chenk) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/255712 /git.openstack. org/cgit/ openstack/ devstack- plugin- glusterfs/ commit/ ?id=92c20721210 cb0c3649ad9a21c d7c76f9cc92b12
Committed: https:/
Submitter: Jenkins
Branch: master
commit 92c20721210cb0c 3649ad9a21cd7c7 6f9cc92b12
Author: Ramana Raja <email address hidden>
Date: Mon Nov 23 21:30:24 2015 +0530
manila: branch aware Tempest checkout
Another take on the problem described
in 5b4dd3c, ie. Manila Tempest update
in
https:/ /github. com/openstack/ manila/ commit/ 6b8319e32a94c22 8ff4258cf31dcd6 c271350e1c? diff=unified# diff-e0705abec5 6bf0f83781d686e 109d63eR63
Instead of checking out $MANILA_ TEMPEST_ COMMIT
blindly (ie. even if it's unset), we add a
fallback to the Tempest commit used prior to
5b4dd3c.
Change-Id: Idec3924a1b5476 683e5520f83df85 61d0bd0ccfd
Closes-Bug: #1524642