From 2d1aec1dcb4652960e9522df26545deb8c9cba32 Mon Sep 17 00:00:00 2001 From: Sean Dague Date: Wed, 16 Apr 2014 18:20:57 -0400 Subject: [PATCH] pull grenade-dsvm-neutron from gate queue because it's non voting grenade-dsvm-neutron is not going to pass for a while because it's found a substantial issue with the neutron migration models when it comes to turning on services in an extant environment. We should pull it off the gate queue (leave it in check only) to save nodes a noise in elastic-recheck gate failures. Change-Id: Ie7ccff10dd515e26fa6865114cb6ccc55177d5c5 --- modules/openstack_project/files/zuul/layout.yaml | 2 -- 1 file changed, 2 deletions(-) diff --git a/modules/openstack_project/files/zuul/layout.yaml b/modules/openstack_project/files/zuul/layout.yaml index 6db3afc001..908ed2fe62 100644 --- a/modules/openstack_project/files/zuul/layout.yaml +++ b/modules/openstack_project/files/zuul/layout.yaml @@ -254,7 +254,6 @@ project-templates: - 'gate-tempest-dsvm-full' - 'gate-tempest-dsvm-neutron' - 'gate-grenade-dsvm' - - 'gate-grenade-dsvm-neutron' - name: integrated-gate-neutron check: @@ -268,7 +267,6 @@ project-templates: - 'gate-tempest-dsvm-neutron' - 'gate-tempest-dsvm-neutron-pg' - 'gate-tempest-dsvm-neutron-large-ops' - - 'gate-grenade-dsvm-neutron' - name: python3-jobs check: