[atomic] ose-ansible & openshift : ansible can't ssh locally

Hi,

I played the scenario showed hereafter based on OpenShift doc [1] to install OSE in a Centos Atomic vm but ansible reports that it can't ssh to 192.168.99.50

Centos Atomic QCow Image used: http://cloud.centos.org/centos/7/atomic/images/CentOS-Atomic-Host-7-GenericCloud.qcow2

The image has been used to create/start a vm in Virtualbox. Then I copy my inventory file to the vm and install "ose-ansible"

scp /Users/dabou/Code/rhoar/cloud-native/infra/virtualbox/inventory root 192 168 99 50:/root/inventory

ssh root 192 168 99 50 "atomic install --system --storage=ostree --set INVENTORY_FILE=/root/inventory registry.access.redhat.com/openshift3/ose-ansible"

I ssh to the vm and then consult the result of the job

systemctl start ose-ansible

systemctl status ose-ansible

As you can see ansible can't ssh locally

2018-03-15 19:31:00,538 p=1 u=root | ok: [localhost] => (item=192.168.99.50)

2018-03-15 19:31:00,550 p=1 u=root | PLAY [Ensure that all non-node hosts are accessible] ***************************

2018-03-15 19:31:00,555 p=1 u=root | TASK [Gathering Facts] *********************************************************

2018-03-15 19:31:01,507 p=1 u=root | fatal: [192.168.99.50]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '192.168.99.50' (ECDSA) to the list of known hosts.\r\nPermission denied (publickey,gssapi-keyex,gssapi-with-mic).\r\n", "unreachable": true}

The ip interface is working

docker0: connected to docker0

"docker0"

bridge, 02:42:E8:E7:32:0A, sw, mtu 1500

inet4 172.17.0.1/16

enp0s3: connected to System enp0s3

"Intel 82540EM Gigabit Ethernet Controller (PRO/1000 MT Desktop Adapter)"

ethernet (e1000), 08:00:27:DF:CC:E8, hw, mtu 1500

inet4 192.168.99.50/24

inet6 fe80::a00:27ff:fedf:cce8/64

enp0s8: connected to System enp0s8

"Intel 82540EM Gigabit Ethernet Controller (PRO/1000 MT Desktop Adapter)"