Split infracloud baremetal into separate playbook run
Currently puppet fails to run on our baremetal servers for infracloud. While this is an issue, it should not block puppet from running on our controller or compute nodes. Change-Id: I190af6cfc63006cb03686cd501998e4e06d350b1 Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This commit is contained in:
@@ -1,8 +1,4 @@
|
||||
---
|
||||
- hosts: "baremetal*.ic.openstack.org:!disabled"
|
||||
gather_facts: true
|
||||
roles:
|
||||
- role: puppet
|
||||
- hosts: "controller*.ic.openstack.org:!disabled"
|
||||
gather_facts: true
|
||||
roles:
|
||||
|
5
playbooks/remote_puppet_infracloud_baremetal.yaml
Normal file
5
playbooks/remote_puppet_infracloud_baremetal.yaml
Normal file
@@ -0,0 +1,5 @@
|
||||
---
|
||||
- hosts: "baremetal*.ic.openstack.org:!disabled"
|
||||
gather_facts: true
|
||||
roles:
|
||||
- role: puppet
|
@@ -30,4 +30,5 @@ set +e
|
||||
# Run all the ansible playbooks under timeout to prevent them from getting
|
||||
# stuck if they are oomkilled
|
||||
|
||||
timeout -k 2m 120m ansible-playbook -f 10 ${ANSIBLE_PLAYBOOKS}/remote_puppet_infracloud_baremetal.yaml
|
||||
timeout -k 2m 120m ansible-playbook -f 10 ${ANSIBLE_PLAYBOOKS}/remote_puppet_infracloud.yaml
|
||||
|
Reference in New Issue
Block a user