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
Platform detection/validation #2347
Comments
One could try to resolve this by creating a config file with platform info, eg.:
passing it to
|
I think solving this will solve many other issues with config file loading for different platforms. It can detect and overwrite the default ones. |
there is function : node.get_provider() which return the actual Provider name that can be use instead of getting t from config file. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. |
This issue has been automatically closed due to inactivity. Please re-open if this still requires investigation. |
When I execute tests on a cluster installed outside of ocs-ci, so that I have a standard cluster dir (from openshift-installer) only, like this:
I see that ocs-ci assumes that the platform is AWS IPI:
Even though the platform is Azure, which could be seen in
metadata.json
file created by openshift-installer in the cluster dir:While we can't be sure about IPI vs UPI status (and other deployment options), we could at least detect that the assumptions we have (coming from the default config) doesn't hold, and raise a warning (along with a suggestion what to do) stopping the test.
This could help people who are trying to run tests on clusters deployed outside of our CI, but tries to share results with us.
The text was updated successfully, but these errors were encountered: