-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdated configs #1
Comments
Hi there, thanks for the feedbacks. This repo was created for personal use at first in order to study openshift before. Pull requests are always welcome although i havent maintain it for a while. i also hope this repo can help people to verify advanced openshift install on their local machine, always. |
I have one question that since what version of openshift-ansible, this |
It's a good question. I didn't checked it exactly. I used your default config, and it didn't worked with your default version (3.9). After I made the node relabelling with the cli tool, the nodes became alive and my pods started to run. |
Hi @chriske this issue has finally been fixed after a bunch of local deploying tests over and over again in these 8 days! Besides, this repo now supports OKD 3.10 deployment and set this version as default one right now. Kindly check them out and give it a try. Feel free to re-open this issue if you've got any other questions. |
Hey!
First of all - thanks for your work!
Currently the config is outdated, because Ansible 2.7 is came out, and it is not able to install OpenShift Origin at this moment. (need to force the Ansible version before 2.7)
The second thing is, after I used Ansible 2.6.5, your node labels are not correct in the ansible hosts file.
Here are the new labels, and the exact same problem: openshift/openshift-ansible#8327
And in the ansible hosts file the subdomain name was incorrect also.
Will you fix those issues? Or do you maintain this repository? Because I'm almost already done with the fixes, and if you want them, I can create a pull request.
Thanks!
The text was updated successfully, but these errors were encountered: