search

ocp-power-automation / openshift-install-power

UPI Install helper to deploy OpenShift 4 on IBM Power Systems Virtual Server using Terraform IaC
Apache License 2.0
17 stars 24 forks source link

[BUG] Accessing cluster using local `oc` doesn't work as documented #112

Closed dpkshetty closed 3 years ago

dpkshetty commented 3 years ago

Describe the bug After succesfull completion of the openshift-install-powervs create script, we get the final msg, part of which says... To access the cluster on local system when using 'oc' run: export KUBECONFIG=/home/dpkshetty/ocp_on_psvs/ocp-install-dir/automation/kubeconfig But that didn't work for me!

To Reproduce

dpkshetty@DESKTOP-L94HV3O:~$ export KUBECONFIG=/home/dpkshetty/ocp_on_psvs/ocp-install-dir/automation/kubeconfig
dpkshetty@DESKTOP-L94HV3O:~$ less $KUBECONFIG
dpkshetty@DESKTOP-L94HV3O:~$ oc get nodes
The connection to the server api.deepakcs-ocp-psvs-637a.ocp.deepakcs:6443 was refused - did you specify the right host or port?
dpkshetty@DESKTOP-L94HV3O:~$ ping api.deepakcs-ocp-psvs-637a.ocp.deepakcs
PING api.deepakcs-ocp-psvs-637a.ocp.deepakcs (52.117.41.83) 56(84) bytes of data.
64 bytes from api.deepakcs-ocp-psvs-637a.ocp.deepakcs (52.117.41.83): icmp_seq=1 ttl=48 time=285 ms
64 bytes from api.deepakcs-ocp-psvs-637a.ocp.deepakcs (52.117.41.83): icmp_seq=2 ttl=48 time=303 ms
^C
--- api.deepakcs-ocp-psvs-637a.ocp.deepakcs ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 284.732/294.057/303.382/9.325 ms
dpkshetty@DESKTOP-L94HV3O:~$

Expected behavior oc from my local terminal should work as documented

Console Output See above

Desktop (please complete the following information):

Additional context None

dpkshetty commented 3 years ago

Additionally, people coming to OCP on PowerVS from OCP on IBM Cloud experience, would expect the oc login to work using the GUI/console oauth/token method. I am referring to the below steps....

The above too didn't work for me. In general for any OCP cluster, the above method should work and is expected to work

bpradipt commented 3 years ago

@dpkshetty which DC this cluster is running? Please check this - https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-network-security

dpkshetty commented 3 years ago

@bpradipt thanks for the link... I see this in there... The port 6443 is also open for miscellaneous purposes. This port will not be open for the WDC04 and DAL13 data centers.

Unfortunatly my PowerVS service is running in Dallas. So looks like then there is no way unless opting for DirectLink connect.. which needs additional charges

Maybe then we should mention the above somewhere and/or have a quick reference troubleshooting section in the README for readers to get enlightened on the above ?

Also the final output msg mentioning the KUBECONFIG step should be edited to include more details , esp the network-security link ?

bpradipt commented 3 years ago

Yes, good suggestion. We can clearly mention in the o/p that CLI login (6443) will not work for WDC04 and DAL13 DC.

dpkshetty commented 3 years ago

Yes, good suggestion. We can clearly mention in the o/p that CLI login (6443) will not work for WDC04 and DAL13 DC.

... and for more details, refer to the network link you had provided above