provision fail when running ansible 2.9.x

[avisiedo]

Hi all,

I have tried to run setup.sh script from pki and ipa directories and I have got the error below:

$ vagrant up
Bringing machine 'pki_server' up with 'libvirt' provider...
==> pki_server: Box 'cheimes/dogtag-f25' could not be found. Attempting to find and install...
    pki_server: Box Provider: libvirt
    pki_server: Box Version: >= 0
==> pki_server: Loading metadata for box 'cheimes/dogtag-f25'
    pki_server: URL: https://vagrantcloud.com/cheimes/dogtag-f25
==> pki_server: Adding box 'cheimes/dogtag-f25' (v10.3.5.2017021300) for provider: libvirt
    pki_server: Downloading: https://vagrantcloud.com/cheimes/boxes/dogtag-f25/versions/10.3.5.2017021300/providers/libvirt.box
    pki_server: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
==> pki_server: Successfully added box 'cheimes/dogtag-f25' (v10.3.5.2017021300) for 'libvirt'!
==> pki_server: Uploading base box image as volume into libvirt storage...
==> pki_server: Creating image (snapshot of base box volume).
==> pki_server: Creating domain with the following settings...
==> pki_server:  -- Name:              pki_pki_server
==> pki_server:  -- Domain type:       kvm
==> pki_server:  -- Cpus:              2
==> pki_server:  -- Feature:           acpi
==> pki_server:  -- Feature:           apic
==> pki_server:  -- Feature:           pae
==> pki_server:  -- Memory:            1024M
==> pki_server:  -- Management MAC:    
==> pki_server:  -- Loader:            
==> pki_server:  -- Nvram:             
==> pki_server:  -- Base box:          cheimes/dogtag-f25
==> pki_server:  -- Storage pool:      default
==> pki_server:  -- Image:             /var/lib/libvirt/images/pki_pki_server.img (6G)
==> pki_server:  -- Volume Cache:      default
==> pki_server:  -- Kernel:            
==> pki_server:  -- Initrd:            
==> pki_server:  -- Graphics Type:     vnc
==> pki_server:  -- Graphics Port:     -1
==> pki_server:  -- Graphics IP:       127.0.0.1
==> pki_server:  -- Graphics Password: Not defined
==> pki_server:  -- Video Type:        cirrus
==> pki_server:  -- Video VRAM:        9216
==> pki_server:  -- Sound Type:	
==> pki_server:  -- Keymap:            en-us
==> pki_server:  -- TPM Path:          
==> pki_server:  -- INPUT:             type=mouse, bus=ps2
==> pki_server: Creating shared folders metadata...
==> pki_server: Starting domain.
==> pki_server: Waiting for domain to get an IP address...
==> pki_server: Waiting for SSH to become available...
    pki_server: 
    pki_server: Vagrant insecure key detected. Vagrant will automatically replace
    pki_server: this with a newly generated keypair for better security.
    pki_server: 
    pki_server: Inserting generated public key within guest...
    pki_server: Removing insecure key from the guest if it's present...
    pki_server: Key inserted! Disconnecting and reconnecting using new SSH key...
==> pki_server: Setting hostname...
==> pki_server: Configuring and enabling network interfaces...
    pki_server: SSH address: 192.168.121.16:22
    pki_server: SSH username: vagrant
    pki_server: SSH auth method: private key
==> pki_server: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.9.2).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    pki_server: Running ansible-playbook...
[WARNING]: Found both group and host with same name: pki_server

ERROR! Unexpected Exception, this is probably a bug: 'CallbackModule' object has no attribute 'set_options'
to see the full traceback, use -vvv
Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I have fixed by reinstalling ansible in the virtualenv, but forcing a version 2.8.x (this works for the Vagrant descriptor at pki directory).

pip install "ansible>=2.8.0,<2.9.0"

After that I provisioned the VM again with vagrant provision, and everything worked properly.

Probably internal changes on ansible 2.9.0 brake some functionalities (or some bug exists).

I guess that it could be needed to report that ansible 2.9.x is not supported yet to address users about this situation.

I was running the above on a centos7 vm, using ansible 2.9.2 (I installed ansible using pip instead of the yum package).