-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
openshift-install failed to install on vsphere and API is not up #4381
Comments
Please check that the bootstrap machine is running and accessible. The bootstrap machine should be the first one to take control of the API VIP. Also, there appears to be a problem communicating with the vCenter at the end.
|
The bootstrap is up, but it comes up with this error:
https://192.168.10.15/sdk should not be accessible according to vmware. |
I think that you are misreading that article. That article is stating that sdk URL is not serving a web page, so it is not "accessible" from a web browser. It should be accessible generally, however. |
but if I visit this URL "https://192.168.10.15/sdk/vimService.wsdl" according to the article, it works just fine as below
|
The following is a snippet from "vendor/github.com/vmware/govmomi/vim25/soap/client.go"
|
Please use https://github.com/openshift/okd for OKD installer issues Dupe of okd-project/okd#394 /close |
@vrutkovs: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Version
Platform:
vsphere
IPI
What happened?
I am running the latest version of installer on vsphere. I can see that the VMs are created for master, worker etc, but the API is not responding. 192.168.10.31 and 192.168.10.32 are 2 unused internal IP in the LAN. the 2 IPs are updated in the DNS with reverse lookup also
192.168.10.31 <-> api.dev.mycompany.com
192.168.10.32 <-> *.apps.dev.mycompany.com
The text was updated successfully, but these errors were encountered: