Deployment failing at step1 - TASK [ping] fails

[sunnyghat]

Hello,

I am setting up ECS CE again after a hard drive failure, I have downloaded and installed CentOS 7.9 minimal, pulled the installation files, bootstrap worked file with my deploy.yml, but step1 is failing with the following:

`[root@ecsce ECS]# step1
ecs-install> Initializing data container, one moment ..DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7.
You are using pip version 19.0.3, however version 20.3.4 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
. OK
ecs-install> Applying and validating deploy.yml...

Do you accept the license? ["yes" or "no"]: yes
Great, thanks for helping us keep the lawyers happy!

PLAY [Installer | Setup access between ecs-install and install node] *****************************************************************************************

TASK [Gathering Facts] ***************************************************************************************************************************************
fatal: [10.100.1.85]: UNREACHABLE! => {"changed": false, "msg": "Authentication failure.", "unreachable": true}

PLAY RECAP ***************************************************************************************************************************************************
10.100.1.85 : ok=0 changed=0 unreachable=1 failed=0

Playbook run took 0 days, 0 hours, 0 minutes, 2 seconds
Operation failed.

PLAY [Common | Ping data nodes before doing anything else] ***************************************************************************************************

TASK [ping] **************************************************************************************************************************************************
fatal: [10.100.1.85]: UNREACHABLE! => {"changed": false, "msg": "Authentication failure.", "unreachable": true}

PLAY RECAP ***************************************************************************************************************************************************
10.100.1.85 : ok=0 changed=0 unreachable=1 failed=0

Playbook run took 0 days, 0 hours, 0 minutes, 2 seconds
Operation failed.
`

nslookup and ping for the hostname and IP address both are successfull including backwards.

Below is the contents of my deploy.yml:

`licensing:
license_accepted: false

autonames:
custom:

• ecsce

facts:
install_node: 10.100.1.85

management_clients:
- 0.0.0.0/0

ssh_defaults:
ssh_username: admin
ssh_password: ChangeMe
ansible_become_pass: ChangeMe
ssh_crypto: rsa

node_defaults:
dns_domain: ghataura.net
dns_servers:
- 10.100.1.1
ntp_servers:
- 10.100.1.1

entropy_source: /dev/urandom
autonaming: custom

storage_pool_defaults:
is_cold_storage_enabled: false
is_protected: false
description: Default storage pool description
ecs_block_devices:
- /dev/sdb

storage_pools:
- name: sp1
members:
- 10.100.1.85
options:
is_protected: false
is_cold_storage_enabled: false
description: My First SP
ecs_block_devices:
- /dev/sdb

virtual_data_center_defaults:
description: Default virtual data center description

virtual_data_centers:
- name: vdc1
members:
- sp1
options:
description: My First VDC

replication_group_defaults:
description: Default replication group description
enable_rebalancing: true
allow_all_namespaces: true
is_full_rep: false

replication_groups:
- name: rg1
members:
- vdc1
options:
description: My First RG
enable_rebalancing: true
allow_all_namespaces: true
is_full_rep: false

management_user_defaults:
is_system_admin: false
is_system_monitor: false

management_users:
- username: admin1
password: ChangeMe
options:
is_system_admin: true
- username: monitor1
password: ChangeMe
options:
is_system_monitor: true

namespace_defaults:
is_stale_allowed: false
is_compliance_enabled: false

namespaces:
- name: ns1
replication_group: rg1
administrators:
- root
options:
is_stale_allowed: false
is_compliance_enabled: false

object_user_defaults:
swift_groups_list:
- users
s3_expiry_time: 2592000

object_users:
- username: object_admin1
namespace: ns1
options:
swift_password: ChangeMe
swift_groups_list:
- admin
- users
s3_secret_key: ChangeMeChangeMeChangeMeChangeMeChangeMe
s3_expiry_time: 2592000
- username: object_user1
namespace: ns1
options:
swift_password: ChangeMe
s3_secret_key: ChangeMeChangeMeChangeMeChangeMeChangeMe

bucket_defaults:
namespace: ns1
replication_group: rg1
head_type: s3
filesystem_enabled: False
stale_allowed: False
encryption_enabled: False
owner: object_admin1

buckets:
- name: bucket1
options:
namespace: ns1
replication_group: rg1
owner: object_admin1
head_type: s3
filesystem_enabled: False
stale_allowed: False
encryption_enabled: False
`

Any assitance would be much appriciated.

[sunnyghat]

By the looks of it it would seemt thet the initial container is not starting:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
61a49c3c27b7 emccorp/ecs-install:latest "/bin/echo echo 'D..." About an hour ago Exited (0) About an hour ago ecs-install-data

I have also downgraded to CentOS 9.4 and get the same error, so I am woundering if its the docker image thats faulty..