aburston
commented
5 years ago /opt/vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/util/which.rb:37: warning: Insecure world writable dir /mnt/c in PATH, mode 040777
/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan/Vagrantfile:10: warning: already initialized constant VAGRANTFILE_API_VERSION
/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan/Vagrantfile:10: warning: previous definition of VAGRANTFILE_API_VERSION was here
/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan/Vagrantfile:12: warning: already initialized constant UUID
/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan/Vagrantfile:12: warning: previous definition of UUID was here
Bringing machine 'vqfx1-pfe' up with 'virtualbox' provider...
Bringing machine 'vqfx1' up with 'virtualbox' provider...
Bringing machine 'srv11' up with 'virtualbox' provider...
Bringing machine 'srv12' up with 'virtualbox' provider...
Bringing machine 'vqfx2-pfe' up with 'virtualbox' provider...
Bringing machine 'vqfx2' up with 'virtualbox' provider...
Bringing machine 'srv21' up with 'virtualbox' provider...
Bringing machine 'srv22' up with 'virtualbox' provider...
==> vqfx1-pfe: Importing base box 'juniper/vqfx10k-pfe'...
==> vqfx1-pfe: Matching MAC address for NAT networking...
==> vqfx1-pfe: Checking if box 'juniper/vqfx10k-pfe' version '0.3.0' is up to date...
==> vqfx1-pfe: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_vqfx1-pfe_1562591115838_68723
==> vqfx1-pfe: Clearing any previously set network interfaces...
==> vqfx1-pfe: Preparing network interfaces based on configuration...
vqfx1-pfe: Adapter 1: nat
vqfx1-pfe: Adapter 2: intnet
==> vqfx1-pfe: Forwarding ports...
vqfx1-pfe: 22 (guest) => 2222 (host) (adapter 1)
==> vqfx1-pfe: Booting VM...
==> vqfx1-pfe: Waiting for machine to boot. This may take a few minutes...
vqfx1-pfe: SSH address: 127.0.0.1:2222
vqfx1-pfe: SSH username: vagrant
vqfx1-pfe: SSH auth method: private key
==> vqfx1-pfe: Machine booted and ready!
==> vqfx1-pfe: Checking for guest additions in VM...
vqfx1-pfe: No guest additions were detected on the base box for this VM! Guest
vqfx1-pfe: additions are required for forwarded ports, shared folders, host only
vqfx1-pfe: networking, and more. If SSH fails on this machine, please install
vqfx1-pfe: the guest additions and repackage the box to continue.
vqfx1-pfe:
vqfx1-pfe: This is not an error message; everything may continue to work properly,
vqfx1-pfe: in which case you may ignore this message.
==> vqfx1-pfe: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
vqfx1-pfe: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> vqfx1: Importing base box 'juniper/vqfx10k-re'...
==> vqfx1: Matching MAC address for NAT networking...
==> vqfx1: Checking if box 'juniper/vqfx10k-re' version '0.3.0' is up to date...
==> vqfx1: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_vqfx1_1562591193787_55993
==> vqfx1: Fixed port collision for 22 => 2222. Now on port 2200.
==> vqfx1: Clearing any previously set network interfaces...
==> vqfx1: Preparing network interfaces based on configuration...
vqfx1: Adapter 1: nat
vqfx1: Adapter 2: intnet
vqfx1: Adapter 3: intnet
vqfx1: Adapter 4: intnet
vqfx1: Adapter 5: intnet
vqfx1: Adapter 6: intnet
vqfx1: Adapter 7: intnet
vqfx1: Adapter 8: intnet
==> vqfx1: Forwarding ports...
vqfx1: 22 (guest) => 2200 (host) (adapter 1)
==> vqfx1: Running 'pre-boot' VM customizations...
==> vqfx1: Booting VM...
==> vqfx1: Waiting for machine to boot. This may take a few minutes...
vqfx1: SSH address: 127.0.0.1:2200
vqfx1: SSH username: vagrant
vqfx1: SSH auth method: private key
==> vqfx1: Machine booted and ready!
==> vqfx1: Checking for guest additions in VM...
vqfx1: No guest additions were detected on the base box for this VM! Guest
vqfx1: additions are required for forwarded ports, shared folders, host only
vqfx1: networking, and more. If SSH fails on this machine, please install
vqfx1: the guest additions and repackage the box to continue.
vqfx1:
vqfx1: This is not an error message; everything may continue to work properly,
vqfx1: in which case you may ignore this message.
==> vqfx1: Setting hostname...
==> vqfx1: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
vqfx1: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
TASK [Build configuration] *****************************************************
[DEPRECATION WARNING]: Distribution Ubuntu 18.04 on host vqfx1 should use
/usr/bin/python3, but is using /usr/bin/python for backward compatibility with
prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See https://docs.ansible.com/ansible/
2.8/reference_appendices/interpreter_discovery.html for more information. This
feature will be removed in version 2.12. Deprecation warnings can be disabled
by setting deprecation_warnings=False in ansible.cfg.
changed: [vqfx1]
TASK [Deploy config to device ... please wait] *********************************
[WARNING]: The value 2200 (type int) in a string field was converted to
u'2200' (type string). If this does not look like what you expect, quote the
entire value to ensure it does not change.
changed: [vqfx1]
PLAY RECAP *********************************************************************
vqfx1 : ok=2 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
==> srv11: Box 'robwc/minitrusty64' could not be found. Attempting to find and install...
srv11: Box Provider: virtualbox
srv11: Box Version: >= 0
==> srv11: Loading metadata for box 'robwc/minitrusty64'
srv11: URL: https://vagrantcloud.com/robwc/minitrusty64
==> srv11: Adding box 'robwc/minitrusty64' (v0.1.0) for provider: virtualbox
srv11: Downloading: https://vagrantcloud.com/robwc/boxes/minitrusty64/versions/0.1.0/providers/virtualbox.box
srv11: Download redirected to host: vagrantcloud-files-production.s3.amazonaws.com
==> srv11: Successfully added box 'robwc/minitrusty64' (v0.1.0) for 'virtualbox'!
==> srv11: Importing base box 'robwc/minitrusty64'...
==> srv11: Matching MAC address for NAT networking...
==> srv11: Checking if box 'robwc/minitrusty64' version '0.1.0' is up to date...
==> srv11: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_srv11_1562591561941_28330
==> srv11: Fixed port collision for 22 => 2222. Now on port 2201.
==> srv11: Clearing any previously set network interfaces...
==> srv11: Preparing network interfaces based on configuration...
srv11: Adapter 1: nat
srv11: Adapter 2: intnet
==> srv11: Forwarding ports...
srv11: 22 (guest) => 2201 (host) (adapter 1)
==> srv11: Running 'pre-boot' VM customizations...
==> srv11: Booting VM...
==> srv11: Waiting for machine to boot. This may take a few minutes...
srv11: SSH address: 127.0.0.1:2201
srv11: SSH username: vagrant
srv11: SSH auth method: private key
srv11:
srv11: Vagrant insecure key detected. Vagrant will automatically replace
srv11: this with a newly generated keypair for better security.
srv11:
srv11: Inserting generated public key within guest...
srv11: Removing insecure key from the guest if it's present...
srv11: Key inserted! Disconnecting and reconnecting using new SSH key...
==> srv11: Machine booted and ready!
==> srv11: Checking for guest additions in VM...
srv11: The guest additions on this VM do not match the installed version of
srv11: VirtualBox! In most cases this is fine, but in rare cases it can
srv11: prevent things such as shared folders from working properly. If you see
srv11: shared folder errors, please make sure the guest additions within the
srv11: virtual machine match the version of VirtualBox you have installed on
srv11: your host and reload your VM.
srv11:
srv11: Guest Additions Version: 4.3.10
srv11: VirtualBox Version: 6.0
==> srv11: Setting hostname...
==> srv11: Configuring and enabling network interfaces...
==> srv11: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
srv11: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> srv11: Running provisioner: shell...
srv11: Running: inline script
==> srv12: Box 'robwc/minitrusty64' could not be found. Attempting to find and install...
srv12: Box Provider: virtualbox
srv12: Box Version: >= 0
==> srv12: Loading metadata for box 'robwc/minitrusty64'
srv12: URL: https://vagrantcloud.com/robwc/minitrusty64
==> srv12: Adding box 'robwc/minitrusty64' (v0.1.0) for provider: virtualbox
==> srv12: Importing base box 'robwc/minitrusty64'...
==> srv12: Matching MAC address for NAT networking...
==> srv12: Checking if box 'robwc/minitrusty64' version '0.1.0' is up to date...
==> srv12: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_srv12_1562591629061_84363
==> srv12: Fixed port collision for 22 => 2222. Now on port 2202.
==> srv12: Clearing any previously set network interfaces...
==> srv12: Preparing network interfaces based on configuration...
srv12: Adapter 1: nat
srv12: Adapter 2: intnet
==> srv12: Forwarding ports...
srv12: 22 (guest) => 2202 (host) (adapter 1)
==> srv12: Running 'pre-boot' VM customizations...
==> srv12: Booting VM...
==> srv12: Waiting for machine to boot. This may take a few minutes...
srv12: SSH address: 127.0.0.1:2202
srv12: SSH username: vagrant
srv12: SSH auth method: private key
srv12:
srv12: Vagrant insecure key detected. Vagrant will automatically replace
srv12: this with a newly generated keypair for better security.
srv12:
srv12: Inserting generated public key within guest...
srv12: Removing insecure key from the guest if it's present...
srv12: Key inserted! Disconnecting and reconnecting using new SSH key...
==> srv12: Machine booted and ready!
==> srv12: Checking for guest additions in VM...
srv12: The guest additions on this VM do not match the installed version of
srv12: VirtualBox! In most cases this is fine, but in rare cases it can
srv12: prevent things such as shared folders from working properly. If you see
srv12: shared folder errors, please make sure the guest additions within the
srv12: virtual machine match the version of VirtualBox you have installed on
srv12: your host and reload your VM.
srv12:
srv12: Guest Additions Version: 4.3.10
srv12: VirtualBox Version: 6.0
==> srv12: Setting hostname...
==> srv12: Configuring and enabling network interfaces...
==> srv12: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
srv12: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> srv12: Running provisioner: shell...
srv12: Running: inline script
==> vqfx2-pfe: Importing base box 'juniper/vqfx10k-pfe'...
==> vqfx2-pfe: Matching MAC address for NAT networking...
==> vqfx2-pfe: Checking if box 'juniper/vqfx10k-pfe' version '0.3.0' is up to date...
==> vqfx2-pfe: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_vqfx2-pfe_1562591703054_40865
==> vqfx2-pfe: Fixed port collision for 22 => 2222. Now on port 2203.
==> vqfx2-pfe: Clearing any previously set network interfaces...
==> vqfx2-pfe: Preparing network interfaces based on configuration...
vqfx2-pfe: Adapter 1: nat
vqfx2-pfe: Adapter 2: intnet
==> vqfx2-pfe: Forwarding ports...
vqfx2-pfe: 22 (guest) => 2203 (host) (adapter 1)
==> vqfx2-pfe: Booting VM...
==> vqfx2-pfe: Waiting for machine to boot. This may take a few minutes...
vqfx2-pfe: SSH address: 127.0.0.1:2203
vqfx2-pfe: SSH username: vagrant
vqfx2-pfe: SSH auth method: private key
==> vqfx2-pfe: Machine booted and ready!
==> vqfx2-pfe: Checking for guest additions in VM...
vqfx2-pfe: No guest additions were detected on the base box for this VM! Guest
vqfx2-pfe: additions are required for forwarded ports, shared folders, host only
vqfx2-pfe: networking, and more. If SSH fails on this machine, please install
vqfx2-pfe: the guest additions and repackage the box to continue.
vqfx2-pfe:
vqfx2-pfe: This is not an error message; everything may continue to work properly,
vqfx2-pfe: in which case you may ignore this message.
==> vqfx2-pfe: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
vqfx2-pfe: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> vqfx2: Importing base box 'juniper/vqfx10k-re'...
==> vqfx2: Matching MAC address for NAT networking...
==> vqfx2: Checking if box 'juniper/vqfx10k-re' version '0.3.0' is up to date...
==> vqfx2: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_vqfx2_1562591797990_9794
==> vqfx2: Fixed port collision for 22 => 2222. Now on port 2204.
==> vqfx2: Clearing any previously set network interfaces...
==> vqfx2: Preparing network interfaces based on configuration...
vqfx2: Adapter 1: nat
vqfx2: Adapter 2: intnet
vqfx2: Adapter 3: intnet
vqfx2: Adapter 4: intnet
vqfx2: Adapter 5: intnet
vqfx2: Adapter 6: intnet
vqfx2: Adapter 7: intnet
vqfx2: Adapter 8: intnet
==> vqfx2: Forwarding ports...
vqfx2: 22 (guest) => 2204 (host) (adapter 1)
==> vqfx2: Running 'pre-boot' VM customizations...
==> vqfx2: Booting VM...
==> vqfx2: Waiting for machine to boot. This may take a few minutes...
vqfx2: SSH address: 127.0.0.1:2204
vqfx2: SSH username: vagrant
vqfx2: SSH auth method: private key
==> vqfx2: Machine booted and ready!
==> vqfx2: Checking for guest additions in VM...
vqfx2: No guest additions were detected on the base box for this VM! Guest
vqfx2: additions are required for forwarded ports, shared folders, host only
vqfx2: networking, and more. If SSH fails on this machine, please install
vqfx2: the guest additions and repackage the box to continue.
vqfx2:
vqfx2: This is not an error message; everything may continue to work properly,
vqfx2: in which case you may ignore this message.
==> vqfx2: Setting hostname...
==> vqfx2: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
vqfx2: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
TASK [Build configuration] *****************************************************
[DEPRECATION WARNING]: Distribution Ubuntu 18.04 on host vqfx2 should use
/usr/bin/python3, but is using /usr/bin/python for backward compatibility with
prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See https://docs.ansible.com/ansible/
2.8/reference_appendices/interpreter_discovery.html for more information. This
feature will be removed in version 2.12. Deprecation warnings can be disabled
by setting deprecation_warnings=False in ansible.cfg.
changed: [vqfx2]
TASK [Deploy config to device ... please wait] *********************************
[WARNING]: The value 2204 (type int) in a string field was converted to
u'2204' (type string). If this does not look like what you expect, quote the
entire value to ensure it does not change.
changed: [vqfx2]
PLAY RECAP *********************************************************************
vqfx2 : ok=2 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
==> srv21: Box 'robwc/minitrusty64' could not be found. Attempting to find and install...
srv21: Box Provider: virtualbox
srv21: Box Version: >= 0
==> srv21: Loading metadata for box 'robwc/minitrusty64'
srv21: URL: https://vagrantcloud.com/robwc/minitrusty64
==> srv21: Adding box 'robwc/minitrusty64' (v0.1.0) for provider: virtualbox
==> srv21: Importing base box 'robwc/minitrusty64'...
==> srv21: Matching MAC address for NAT networking...
==> srv21: Checking if box 'robwc/minitrusty64' version '0.1.0' is up to date...
==> srv21: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_srv21_1562591948142_33833
==> srv21: Fixed port collision for 22 => 2222. Now on port 2205.
==> srv21: Clearing any previously set network interfaces...
==> srv21: Preparing network interfaces based on configuration...
srv21: Adapter 1: nat
srv21: Adapter 2: intnet
==> srv21: Forwarding ports...
srv21: 22 (guest) => 2205 (host) (adapter 1)
==> srv21: Running 'pre-boot' VM customizations...
==> srv21: Booting VM...
==> srv21: Waiting for machine to boot. This may take a few minutes...
srv21: SSH address: 127.0.0.1:2205
srv21: SSH username: vagrant
srv21: SSH auth method: private key
srv21:
srv21: Vagrant insecure key detected. Vagrant will automatically replace
srv21: this with a newly generated keypair for better security.
srv21:
srv21: Inserting generated public key within guest...
srv21: Removing insecure key from the guest if it's present...
srv21: Key inserted! Disconnecting and reconnecting using new SSH key...
==> srv21: Machine booted and ready!
==> srv21: Checking for guest additions in VM...
srv21: The guest additions on this VM do not match the installed version of
srv21: VirtualBox! In most cases this is fine, but in rare cases it can
srv21: prevent things such as shared folders from working properly. If you see
srv21: shared folder errors, please make sure the guest additions within the
srv21: virtual machine match the version of VirtualBox you have installed on
srv21: your host and reload your VM.
srv21:
srv21: Guest Additions Version: 4.3.10
srv21: VirtualBox Version: 6.0
==> srv21: Setting hostname...
==> srv21: Configuring and enabling network interfaces...
==> srv21: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
srv21: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> srv21: Running provisioner: shell...
srv21: Running: inline script
==> srv22: Box 'robwc/minitrusty64' could not be found. Attempting to find and install...
srv22: Box Provider: virtualbox
srv22: Box Version: >= 0
==> srv22: Loading metadata for box 'robwc/minitrusty64'
srv22: URL: https://vagrantcloud.com/robwc/minitrusty64
==> srv22: Adding box 'robwc/minitrusty64' (v0.1.0) for provider: virtualbox
==> srv22: Importing base box 'robwc/minitrusty64'...
==> srv22: Matching MAC address for NAT networking...
==> srv22: Checking if box 'robwc/minitrusty64' version '0.1.0' is up to date...
==> srv22: Setting the name of the VM: full-2qfx-4srv-evpnvxlan_srv22_1562592032028_59593
==> srv22: Fixed port collision for 22 => 2222. Now on port 2206.
==> srv22: Clearing any previously set network interfaces...
==> srv22: Preparing network interfaces based on configuration...
srv22: Adapter 1: nat
srv22: Adapter 2: intnet
==> srv22: Forwarding ports...
srv22: 22 (guest) => 2206 (host) (adapter 1)
==> srv22: Running 'pre-boot' VM customizations...
==> srv22: Booting VM...
==> srv22: Waiting for machine to boot. This may take a few minutes...
srv22: SSH address: 127.0.0.1:2206
srv22: SSH username: vagrant
srv22: SSH auth method: private key
srv22:
srv22: Vagrant insecure key detected. Vagrant will automatically replace
srv22: this with a newly generated keypair for better security.
srv22:
srv22: Inserting generated public key within guest...
srv22: Removing insecure key from the guest if it's present...
srv22: Key inserted! Disconnecting and reconnecting using new SSH key...
==> srv22: Machine booted and ready!
==> srv22: Checking for guest additions in VM...
srv22: The guest additions on this VM do not match the installed version of
srv22: VirtualBox! In most cases this is fine, but in rare cases it can
srv22: prevent things such as shared folders from working properly. If you see
srv22: shared folder errors, please make sure the guest additions within the
srv22: virtual machine match the version of VirtualBox you have installed on
srv22: your host and reload your VM.
srv22:
srv22: Guest Additions Version: 4.3.10
srv22: VirtualBox Version: 6.0
==> srv22: Setting hostname...
==> srv22: Configuring and enabling network interfaces...
==> srv22: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.8.1).
Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
srv22: Running ansible-playbook...
[WARNING] Ansible is being run in a world writable directory (/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan), ignoring it as an ansible.cfg source. For more information see https://docs.ansible.com/ansible/devel/reference_appendices/config.html#cfg-in-world-writable-dir
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to
allow bad characters in group names by default, this will change, but still be
user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in
ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use
-vvvv to see details
PLAY [Build and deploy configuration] ******************************************
skipping: no hosts matched
PLAY RECAP *********************************************************************
==> srv22: Running provisioner: shell...
srv22: Running: inline script
root@aburston-P50:/mnt/c/Users/aburston/vqfx10k-vagrant/full-2qfx-4srv-evpnvxlan#Completes successfully, however there seems to be a problem logging into the vqfx1/2 devices. This is probably unrelated to this bug.
Reported by @aburston:
It seems that when following the installation guide for Windows, this failure is taking place.
The logic in the Vagrantfile(s) is intended to direct the output to NUL on Windows, but the Windows detection does not seem to work right when the Windows Subsystem for Linux is in use. Should determine if we really need that.