testnode: do not start rpcbind on precise

rpcbind does not provide a way to be managed with upstart on precise.
This creates a var we can use to toggle this task on and off per distro
as the other distros we support are ok with starting and enabling rpcbind.

Signed-off-by: Andrew Schoen <aschoen@redhat.com>

diff --git a/roles/testnode/defaults/main.yml b/roles/testnode/defaults/main.yml
index 48d40237417b5f6797f1c7569ee8e8a3e405827b..808a3d7d9a087a4f7e5df4db78e13146ca7da7e1 100644 (file)
--- a/roles/testnode/defaults/main.yml
+++ b/roles/testnode/defaults/main.yml
@@ -18,3 +18,7 @@ packages_to_upgrade: []
 # the user teuthology will use
 teuthology_user: "ubuntu"
 xfstests_user: "fsgqa"
+
+# some distros need to start rpcbind before
+# trying to use nfs while others don't.
+start_rpcbind: true

diff --git a/roles/testnode/handlers/main.yml b/roles/testnode/handlers/main.yml
index b33c1e3c5c8ccd85b317848cbce02afefec1f395..d8e634dcacce877a6dacc81fcd32938004732fce 100644 (file)
--- a/roles/testnode/handlers/main.yml
+++ b/roles/testnode/handlers/main.yml
@@ -14,6 +14,7 @@
     name: rpcbind
     state: started
     enabled: yes
+  when: start_rpcbind
 
 - name: restart nfs-server
   service:

diff --git a/roles/testnode/vars/ubuntu_12.04.yml b/roles/testnode/vars/ubuntu_12.04.yml
index 34e8e21ad4981bdc881244860a92adcaa5c149e2..cbe46e3149371a04046ae512a3adf8ac7310b497 100644 (file)
--- a/roles/testnode/vars/ubuntu_12.04.yml
+++ b/roles/testnode/vars/ubuntu_12.04.yml
@@ -9,3 +9,7 @@ packages:
   - ltp-kernel-test
   - libmpich2-3
   - kvm
+
+# on precise rpcbind does not provide a way to
+# be managed with upstart
+start_rpcbind: false