Skip to content

Commit

Permalink
Add troubleshooting docs for libvirt console issue.
Browse files Browse the repository at this point in the history
  • Loading branch information
praveenkumar committed Mar 6, 2019
1 parent 2a667dc commit cc4a3fd
Showing 1 changed file with 26 additions and 0 deletions.
26 changes: 26 additions & 0 deletions docs/dev/libvirt-howto.md
Original file line number Diff line number Diff line change
Expand Up @@ -286,6 +286,32 @@ kubectl get --all-namespaces pods
## Troubleshooting
If following the above steps hasn't quite worked, please review this section for well known issues.

### console doesn't come up
In case of libvirt there is no wildcard dns resolution and console is depend on the route which is created by auth operator.
To make it work we need to use the multi-stage installation and edit the `domain` for ingress.

Following steps are required to have console operator up and working.
```console
// Add another domain entry in the openshift.conf which used by dnsmasq
// Here `tt.testing` is the domain which I choose when running the installer.
$ cat /etc/NetworkManager/dnsmasq.d/openshift.conf
server=/tt.testing/192.168.126.1
address=/.apps.tt.testing/192.168.126.51

// Make sure you restart the NetworkManager after change in the openshift.conf
$ sudo systemctl restart NetworkManager

// Create the manifests
$ openshift-install create manifests --dir myTestDir

// Edit the cluster-ingress-02-config.yml file
$ cat myTestDir/manifests/cluster-ingress-02-config.yml | grep domain
domain: apps.tt.testing

// Start the installer to create the cluster
$ openshift-install create cluster
```

### Install throws an `Unable to resolve address 'localhost'` error

If you're seeing an error similar to
Expand Down

0 comments on commit cc4a3fd

Please sign in to comment.