We shouldn't really be changing the config of the cloud we're testing - that stops us being run against actual prod clouds. Instead we should have some set of profiles we test against - and then run different jobs for different profiles, avoiding the problem entirely. -Rob On 13 November 2013 15:23, Zhi Kun Liu <liuzhikun at gmail.com> wrote: > Hi all, > > In Tempest, we have some testcases that disable/enable services or agents. > e.g. > https://review.openstack.org/#/c/55271/1/tempest/api/compute/admin/test_services.py > test_service_enable_disable > test_disable_service_with_disable_reason > > Since Tempest run in parallel for now, I'm afraid of these testcases have > possible impact on other tests. Anyone has ideas about it? Should we remove > such testcases? > > Regards, > Zhi Kun > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Robert Collins <rbtcollins at hp.com> Distinguished Technologist HP Converged Cloud