all.yml file doesn't have etcd num nodes

[rlopez133]

The file: https://github.com/openshift/openshift-ansible-contrib/blob/master/playbooks/provisioning/openstack/sample-inventory/group_vars/all.yml makes no mention of number of etcd nodes, however, if you use the existing https://github.com/openshift/openshift-ansible-contrib/blob/master/playbooks/provisioning/openstack/sample-inventory/hosts file example, it expects an etcd system with etcd.openshift.example.com.

The workaround was to put etcd servers within the masters. However, the all.yaml file should have some sort of variable to list out # of etc nodes and/or if it finds 0 to place etcd by default within master nodes

@tomassedovic

[bogdando]

also note that the heat stack outputs contain empty lists for etcd related info

[mbruzek]

I ran into a similar problem with the installer. Here was the output from the playbook:

TASK [Evaluate groups - Fail if no etcd hosts group is defined] ****************                         
Tuesday 19 September 2017  16:18:26 +0000 (0:00:00.021)       0:00:00.325 *****                          
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg": "Running etcd as an embedded service is no longer supported. If this is a new install please define an 'etcd' group with either one or three hosts. These hosts may be the same hosts as your masters. If this is an upgrade you may set openshift_master_unsupported_embedded_etcd=true until a migration playbook becomes available.\n"} 

Is it possible the openshift-ansible project made a change that is not yet reflected in the contrib repository?

What can be done to work around this issue?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale