Temporarily stop using rax for py3k-precise nodes

* modules/openstack_project/templates/nodepool/nodepool.yaml.erb:
The py3k-precise nodes in rax regions are exhibiting an odd behavior
when using pip to upgrade setuptools along with other requirements
inside a pypy-based virtualenv. This is causing most pypy unit test
jobs run there to fail. Temporarily cease building new nodes of this
type in those locations for now, which will limit jobs to running on
the ones we've seen work successfully. This can be reverted once the
underlying discrepancy is determined and resolved.

Change-Id: I38156258a7a9b42cf536725fbaf75c7ddfa7bbd7
This commit is contained in:
Jeremy Stanley 2014-03-10 21:00:42 +00:00
parent 33c0824569
commit a9e6dc5723

View File

@ -358,9 +358,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -410,9 +407,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -462,9 +456,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -514,9 +505,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -566,9 +554,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -618,9 +603,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3
@ -670,9 +652,6 @@ targets:
- name: py3k-precise
min-ready: 1
providers:
- name: rax-iad
- name: rax-dfw
- name: rax-ord
- name: hpcloud-az1
- name: hpcloud-az2
- name: hpcloud-az3