Latest update:
I found the cause, but I'm not sure if it is a bug.
I add a value for trix_login_fqdn before I ran ansible-playbook controller.yml for the first time.
The following in all.yml gives me an error. Deleting it was not enough I had to start the install from scratch.
trix_external_fqdn: ondemand.baylor.edu
-----------------------------------------------------------------------
optional hostname/fqdn only needed when building a login image
based on the login-default.yml playbook.
trix_login_fqdn: ondemand.cluster.baylor.edu
I cloned the current archive into a new install, copied all.yml.example, and edited it.
Is this a problem with the all.yml in the distribution, or is it one of the changes that I made to all.yml?
TASK [trinity/yml-check : debug] ************************************************
ok: [trinitya] => {
"msg": "yaml version in all.yml 0 >= 150300"
}
TASK [trinity/yml-check : Verifying if group_vars/all.yml is compatible with current TrinityX release] ***
fatal: [trinitya]: FAILED! => {"changed": false, "msg": "Existing group_vars/all.yml is not compatible with the current TrinityX release. Please copy group_vars/all.yml.example to group_vars/all.yml and review the configuration first"}
PLAY RECAP **********************************************************************
trinitya : ok=5 changed=1 unreachable=0 failed=1 skipped=3 rescued=0 ignored=0
[root@trinitya site]# tail group_vars/all.yml
-----------------------------------------------------------------------
whether we need to configure our ldap, sssd and other things (true)
or we use an external manually configured authentication mechanism (false)
enable_authentication: true
-----------------------------------------------------------------------
DO NOT REMOVE: yml check: 150300
[root@trinitya site]# tail group_vars/all.yml.example
-----------------------------------------------------------------------
whether we need to configure our ldap, sssd and other things (true)
or we use an external manually configured authentication mechanism (false)
enable_authentication: true
-----------------------------------------------------------------------
DO NOT REMOVE: yml check: 150300
[root@trinitya site]#
Latest update:
I found the cause, but I'm not sure if it is a bug.
I add a value for trix_login_fqdn before I ran ansible-playbook controller.yml for the first time.
The following in all.yml gives me an error. Deleting it was not enough I had to start the install from scratch.
trix_external_fqdn: ondemand.baylor.edu
-----------------------------------------------------------------------
optional hostname/fqdn only needed when building a login image
based on the login-default.yml playbook.
trix_login_fqdn: ondemand.cluster.baylor.edu
I cloned the current archive into a new install, copied all.yml.example, and edited it.
Is this a problem with the all.yml in the distribution, or is it one of the changes that I made to all.yml?
TASK [trinity/yml-check : debug] ************************************************
ok: [trinitya] => {
"msg": "yaml version in all.yml 0 >= 150300"
}
TASK [trinity/yml-check : Verifying if group_vars/all.yml is compatible with current TrinityX release] ***
fatal: [trinitya]: FAILED! => {"changed": false, "msg": "Existing group_vars/all.yml is not compatible with the current TrinityX release. Please copy group_vars/all.yml.example to group_vars/all.yml and review the configuration first"}
PLAY RECAP **********************************************************************
trinitya : ok=5 changed=1 unreachable=0 failed=1 skipped=3 rescued=0 ignored=0
[root@trinitya site]# tail group_vars/all.yml
-----------------------------------------------------------------------
whether we need to configure our ldap, sssd and other things (true)
or we use an external manually configured authentication mechanism (false)
enable_authentication: true
-----------------------------------------------------------------------
DO NOT REMOVE: yml check: 150300
[root@trinitya site]# tail group_vars/all.yml.example
-----------------------------------------------------------------------
whether we need to configure our ldap, sssd and other things (true)
or we use an external manually configured authentication mechanism (false)
enable_authentication: true
-----------------------------------------------------------------------
DO NOT REMOVE: yml check: 150300
[root@trinitya site]#