You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.
Describe the bug
OpenShift Container Platform Deployment using Ansible can never work.
To Reproduce
Steps to reproduce the behavior:
Deploy the platform according to the documentation
Results in error: The error was: 'master_publicip_fqdn' is undefined
Expected behavior
A deployed cluster using Ansible
Additional context
The problem here is that in the playbook a new play is started on the Bastion host, while all variables were set on localhost. Hence the deployment fails as the Bastion is not aware of all the facts that were set on localhost. This should be easy to fix by referencing all facts that were set in de play before as follows:
{{ hostvars['localhost']['fact'] }}
It looks like this playbook has not been tested, as it could have never worked.
The text was updated successfully, but these errors were encountered:
After solving this part of the playbook, it turns out that this playbook stops after deploying the infra: The installation of the Openshift container platform is never initiated. I guess that this still is Work in Progress, and it would be kind to add this to the documentation.
Sorry for the delay. I have been working on making a major update to the templates and scripts. I have already incorporated the fix from @geda10 into the latest version of the templates and have opened a PR with a major revision. Once this gets reviewed and we merge, all should be good.
Describe the bug
OpenShift Container Platform Deployment using Ansible can never work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A deployed cluster using Ansible
Additional context
The problem here is that in the playbook a new play is started on the Bastion host, while all variables were set on localhost. Hence the deployment fails as the Bastion is not aware of all the facts that were set on localhost. This should be easy to fix by referencing all facts that were set in de play before as follows:
{{ hostvars['localhost']['fact'] }}
It looks like this playbook has not been tested, as it could have never worked.
The text was updated successfully, but these errors were encountered: