Skip to content
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

No "Database type" options in UI #430

Open
estromenko opened this issue Jun 19, 2024 · 3 comments
Open

No "Database type" options in UI #430

estromenko opened this issue Jun 19, 2024 · 3 comments

Comments

@estromenko
Copy link

After fresh installation in a local k3s cluster there are no options in "Database type" field, so the next steps are not available. All pods in everest-system, everest-monitoring, everest-olm and my target namespace are running. There are no errors in browser console.

image

@solovevayaroslavna
Copy link
Contributor

solovevayaroslavna commented Jul 1, 2024

Hello @estromenko! Thanks for mention of this issue!

I ran into the same problem in everest. In my case, the status of DBEngine data didn't come from BE to FE, which is why the ui showed exactly this picture.
The reason for this in my case turned out to be a forgotten wireguard connection that I had not disconnected in the background, which affected the work of the everest operator. The error wasn't visible in the console of my operating system where i worked with everest-cli, but I was able to find an entry about it in the tilt interface, with which I raised the local cluster at this path - http://localhost:port/r/everest-operator/overview.

@recharte
Copy link
Collaborator

recharte commented Jul 1, 2024

@estromenko is your k8s cluster running behind a proxy blocking internet access?
The Everest operator requires access to Percona's Version Service (https://check.percona.com/) to figure out the available DB engine versions. If the operator can't reach the version service the UI will not know which engines (and versions) are available.

@estromenko
Copy link
Author

Hello everyone! Thanks a lot for the advises!
There were some issues with DNS resolution in my cluster. I noticed i/o timeout errors in coredns pod, so that's why everest couldn't reach https://check.percona.com address. I did 2 actions and I am not really sure which one solved the issue (might be both).

Steps to fix the issue:

  1. Configure or reset iptables rules (for instance sudo iptables --flush).
  2. Change nameserver in /etc/resolv.conf file and reinstall cluster. For example, I changed nameserver from 192.168.0.1 to 127.0.0.53 (might be bad advice because systemd-resolved resets this file, but it's out of the current topic).

What do you think about adding some UI error message in this case? It would help a lot in troubleshooting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants