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

Add preflight check for apps-crc.testing DNS resolution #335

Closed
cfergeau opened this issue Jul 22, 2019 · 4 comments
Closed

Add preflight check for apps-crc.testing DNS resolution #335

cfergeau opened this issue Jul 22, 2019 · 4 comments
Labels
status/stale Issue went stale; did not receive attention or no reply from the OP

Comments

@cfergeau
Copy link
Contributor

I recently helped someone debug their crc install. The issue was a /etc/NetworkManager/dnsmasq.d/openshift.conf file taking precedence over the crc.conf file that crc installs. This was causing *..apps-crc.testing to resolve to 192.168.126.11 instead of the expected 192.168.130.11. We should have a check resolving foo.apps-crc.testing and erroring out if it does not resolve to 192.168.130.11. I'm not sure we can automatically fix this though.

@cfergeau
Copy link
Contributor Author

This might become obsolete with #248

@gbraad
Copy link
Contributor

gbraad commented Jul 24, 2019

We still have to check for the existence of the file during the setup command to clean the state... and this can be a general command to make sure we are in a consistent state.

the deletion of this file might be included for a short time

@stale
Copy link

stale bot commented Feb 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Feb 11, 2020
@stale stale bot closed this as completed Feb 25, 2020
@cfergeau
Copy link
Contributor Author

This was addressed in 6673ade except on macos. See also #1013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/stale Issue went stale; did not receive attention or no reply from the OP
Projects
None yet
Development

No branches or pull requests

2 participants