From 00613cd4f31c87e37ebe0d6201979338b201a815 Mon Sep 17 00:00:00 2001 From: Mario Loria Date: Wed, 11 Mar 2015 21:36:44 -0400 Subject: [PATCH] Setting the actual passno and dump defaults, and warning user of consequences in nulling Using ansible 1.8.4, I found that these two options actually work slightly different than advertised. --- lib/ansible/modules/system/mount.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lib/ansible/modules/system/mount.py b/lib/ansible/modules/system/mount.py index d415d65b0d5..e11d497220b 100644 --- a/lib/ansible/modules/system/mount.py +++ b/lib/ansible/modules/system/mount.py @@ -51,14 +51,14 @@ options: default: null dump: description: - - dump (see fstab(8)) + - "dump (see fstab(8)), Note that if nulled, C(state=present) will cease to work and duplicate entries will be made with subsequent runs." required: false - default: null + default: 0 passno: description: - - passno (see fstab(8)) + - "passno (see fstab(8)), Note that if nulled, C(state=present) will cease to work and duplicate entries will be made with subsequent runs." required: false - default: null + default: 0 state: description: - If C(mounted) or C(unmounted), the device will be actively mounted or unmounted