Skip to content
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

'ocp' and 'ocpm' prefixes are hardcoded in 'scripts/deployOpenShift.sh' #8

Open
alexbez opened this issue Oct 4, 2017 · 2 comments

Comments

@alexbez
Copy link

alexbez commented Oct 4, 2017

If a users chooses any other prefix than 'ocp' in 'azuredeploy.parameters.json', the deployOpenShift.sh script fails, as it expects to find a hardcoded 'ocp' and 'ocpm' prefixes while constructing '/etc/ansible/hosts' file. Then if the prefix set in 'openshiftClusterPrefix' in 'azuredeploy.parameters.json' file is different, then hosts file would contain wrong entries and when installer tries to set networking parameters that operation fails.

Suggestion: replace hardcoded 'ocp', 'ocpm' (and, probably, some others like 'ocpi' or 'ocpn' or 'ocpb') by parameters taken from 'openshiftClusterPrefix' in 'azuredeploy.parameters.json.

@mglantz
Copy link
Owner

mglantz commented Oct 9, 2017

Yepp, I'm aware of this. It's due to spagetti hostname magic in the deployOpenShift.sh script. Will fix when I get some time.

@mglantz
Copy link
Owner

mglantz commented Oct 11, 2017

In the new version of the deployment script cluster prefix is not possible change, until I get this fixed..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants