Open lvnilesh opened 7 years ago
./lib/pki-authority: line 111:
declare: -g: invalid option
declare: usage:
declare [-afFirtx] [-p] [name[=value] ...]
My 10.0.1.22 is Ubuntu 16.04 not pure debian.
Strange.
ssh 10.0.1.22
root@chromebox:~# declare -gA config
root@chromebox:~#
Here is the play recap:
PLAY RECAP *********************************************************************
10.0.1.22 : ok=50 changed=0 unreachable=0 failed=1
TASK: debops.core : Create root directories ----------------------------- 2.62s
TASK: debops.apt_preferences : Remove legacy APT preferences ------------ 1.72s
TASK: debops.secret : Create secret directories on Ansible Controller --- 1.70s
TASK: debops.core : Save local facts ------------------------------------ 1.46s
TASK: debops.core : Install local fact scripts -------------------------- 1.05s
TASK: setup ------------------------------------------------------------- 0.89s
TASK: debops.apt_preferences : Remove APT preferences ------------------- 0.85s
TASK: setup ------------------------------------------------------------- 0.79s
TASK: debops.core : Install required core packages ---------------------- 0.67s
TASK: debops.dhparam : Install encryption software ---------------------- 0.63s
On Ansible Controller, you need at least bash
4.x for the debops.pki
role to work correctly.
@drybjed Would it make sense to include a check for the Bash version also on the Ansible controller so that this becomes a little bit easier to debug?
@ypid I thought about the same thing. Perhaps the pki-authority
script could check the bash
version and exit early with an error message that explains what the issue is.
Sounds good.
I am using
zsh --version
zsh 5.2 (x86_64-apple-darwin15.0.0)
@lvnilesh This doesn't really matter in the context of a script interpreter, which woul be /bin/bash
. Check your Bash version, mine is:
$ bash --version
GNU bash, version 4.3.30(1)-release (x86_64-pc-linux-gnu)
bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin15)
Copyright (C) 2007 Free Software Foundation, Inc.
First time using debops.
I ran
debops
against a target machine 10.0.1.22 in local network and noted this failure. Can you please enlighten me?