Or how about just disable the flag which will skip snapshot manage tests for CI where it should not run.
Flag in Devtsack is TEMPEST_VOLUME_MANAGE_SNAPSHOT which can be set to False on CI. I added the same on ceph gate jobs [1] and similarly can be added on CI side if ok? ..1 https://review.openstack.org/#/c/421073/ -gmann On Tue, Jan 17, 2017 at 4:32 AM, Sean McGinnis <sean.mcgin...@gmx.com> wrote: > On Mon, Jan 16, 2017 at 08:52:34AM +0100, Silvan Kaiser wrote: > > Apoorva, Sean, > > after some time i managed to bring up Quobyte CI last friday which tested > > fine [1,2,3] for a short time and then ran into the same issues with > > manage_snapshot > > related tempest tests Apoorva describes (Starting chronologically at > [4]). > > From here i see two steps: > > a) look into the reason for the issue with manage_snapshot tests > > b) a short note on how to proceed for marking drivers with reinstated CIs > > Hey Sylvan, > > As mentioned, if the CI requirements can be met yet this cycle, we can > just do a revert for the patch that set the unsupported flag. That > should be a quick and easy one to get through once we see the CI is > back and stable. > > Thanks! > Sean > > > back as supported is much appreciated > > Best > > Silvan > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
