-
Notifications
You must be signed in to change notification settings - Fork 77
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
01e1771
commit 2e25a37
Showing
1 changed file
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,41 @@ | ||
# Troubleshooting | ||
|
||
###1. Tilt stops working as not able to connect to kind cluster | ||
|
||
``` | ||
% kind get clusters | ||
enabling experimental podman provider | ||
ERROR: failed to list clusters: command "podman ps -a --filter label=io.x-k8s.kind.cluster --format '{{index .Labels "io.x-k8s.kind.cluster"}}'" failed with error: exit status 125 | ||
Command Output: Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM | ||
Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:61514: connect: connection refused | ||
``` | ||
|
||
1. Stop and start the Podman either via cli or from Podman Desktop. | ||
2. Run all the stopped containers like capi-test-control-plane, capi-test-worker, kind-registry. | ||
3. Try re-running `tilt up` from `cluster-api` directory. | ||
|
||
|
||
###2. SSH into data/control plane node configured with DHCP network | ||
1. Since the VM backing the node is configured with DHCP network which is private we can't directly SSH into it. | ||
2. Create a public VM in the same workspace and attach the DHCP network to it. | ||
|
||
1. Create public network in PowerVS workspace if it does not exist using ibmcloud cli | ||
```shell | ||
$ibmcloud pi subnet create publicnet1 --net-type public | ||
``` | ||
2. List the available images to create VM | ||
```shell | ||
$ibmcloud pi image lc | ||
``` | ||
3. Create the VM with public and DHCP subnet. | ||
```shell | ||
$ibmcloud pi instance create publicVM --image testrhel88 --subnets DHCPSERVERcapi-powervs-keerthana-new_Private,publicnet1 | ||
``` | ||
4. Get the public IP of created VM | ||
```shell | ||
$ibmcloud pi ins get publicVM | ||
``` | ||
4. SSH into the DHCP VM using public VM as a jump host. | ||
``` | ||
ssh -J root@<public_ip> root@<dhcp_ip> | ||
``` |