Vagrant - playbook fails at TASK [download : download_file | Copy file back to ansible host file cache]

[der-ali]

Environment:
Vagrant Version: 2.0.3
vagrant config:

$instance_name_prefix = "kub"
$vm_cpus = 1
$num_instances = 4
$os = "centos"
$subnet = "10.0.20"
$network_plugin = "flannel"
$inventory = "inventory/my_lab"
$etcd_instances=1
$kube_master_instances=1

• OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"):
  Ubuntu 18.04.4 LTS
• Version of Ansible (ansible --version):
  ansible 2.9.6
• Version of Python (python --version):
  Python 3.7.5

Kubespray version (commit) (git rev-parse --short HEAD):
Master branch 6e29a47

Network plugin used:
flannel

Output of ansible run:

TASK [download : download_file | Copy file back to ansible host file cache] ****
fatal: [kub-1]: FAILED! => {"changed": false, "cmd": "/usr/bin/rsync --delay-updates -F --compress --archive --rsh=/usr/bin/ssh -S none -i /home/ali/.vagrant.d/insecure_private_key -o Port=2222 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null --rsync-path=sudo rsync --out-format=<<CHANGED>>%i %n%L vagrant@127.0.0.1:/home/ali/kubespray_cache/kubeadm-v1.17.5-amd64 /home/ali/kubespray_cache/kubeadm-v1.17.5-amd64", "msg": "Warning: Permanently added '[127.0.0.1]:2222' (ED25519) to the list of known hosts.\r\nReceived disconnect from 127.0.0.1 port 2222:2: Too many authentication failures\r\nDisconnected from 127.0.0.1 port 2222\r\nrsync: connection unexpectedly closed (0 bytes received so far) [Receiver]\nrsync error: unexplained error (code 255) at io.c(235) [Receiver=3.1.2]\n", "rc": 255}

I tried adding ansible_ssh_extra_args="-o IdentitiesOnly=yes" to the ansible inventory file but after rerunning the playbook i was failing at

TASK [kubernetes/preinstall : check if /etc/dhcp/dhclient.conf exists]
task path: /home/ali/Work/Arconsis/Exp/kubespray/roles/kubernetes/preinstall/tasks/0040-set_facts.yml:92
The full traceback is:
WARNING: The below traceback may *not* be related to the actual failure.
  File "/tmp/ansible_stat_payload_dAQdVo/ansible_stat_payload.zip/ansible/modules/files/stat.py", line 464, in main
fatal: [kub-1]: FAILED! => {
    "changed": false,
    "invocation": {
        "module_args": {
            "checksum_algorithm": "sha1",
            "follow": false,
            "get_attributes": true,
            "get_checksum": true,
            "get_md5": false,
            "get_mime": true,
            "path": "/etc/dhcp/dhclient.conf"
        }
    },
    "msg": "Permission denied"
}
<127.0.0.1> (1, b'\n{"msg": "Permission denied", "failed": true, "exception": "WARNING: The below traceback may *not* be related to the actual failure.\\n  File \\"/tmp/ansible_stat_payload_AM27TS/ansible_stat_payload.zip/ansible/modules/files/stat.py\\", line 464, in main\\n", "invocation": {"module_args": {"checksum_algorithm": "sha1", "get_checksum": true, "follow": false, "path": "/etc/dhcp/dhclient.conf", "get_md5": false, "get_mime": true, "get_attributes": true}}}\n', b'')
<127.0.0.1> Failed to connect to the host via ssh:

it is failing on the same task also on branch tag v2.12.5

[der-ali]

adding $HOME/.vagrant.d/insecure_private_key to the ssh-agent seems to solve the issue regarding Too many authentication failures

[Miouge1]

Last CI job for Vagrant is green, so I don't think it's something coming from Vagrantfile.

CI is using Vagrant v2.2.7, so I recommend to update to vagrant version

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.