minishift: Locally installed dnsmasq server causes DNS lookups to fail for instances using the xhyve driver
dwojciec-osx:bin dwojciec$ minishift start
-- Checking if requested hypervisor 'xhyve' is supported on this platform ... OK
-- Checking if xhyve driver is installed ...
Driver is available at /usr/local/bin/docker-machine-driver-xhyve
Checking for setuid bit ... OK
-- Checking the ISO URL ...
Checking if /Users/dwojciec/.minishift/cache/iso/minishift-rhel7.iso exists ... OK
-- Starting local OpenShift cluster using 'xhyve' hypervisor ...
-- Starting Minishift VM ............... OK
-- Registering machine using subscription-manager
Registration in progress . FAIL [2s]
Error to register VM: ssh command error:
command : sudo -E subscription-manager register --auto-attach --username XXXXX --password 'XXXXX'
err : exit status 70
output : Registering to: subscription.rhsm.redhat.com:443/subscription
Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
I tried to start it using this command to have more information
minishift start -v 5 --show-libmachine-logs
but not real additional information.
Except the version of subscription-manager
sudo -E subscription-manager version
SSH cmd err, output: <nil>: server type: This system is currently not registered.
subscription management server: Unknown
subscription management rules: Unknown
subscription-manager: 1.19.23-1.el7_4
python-rhsm: 1.19.10-1.el7_4
by using minishift ssh I checked the /var/log/rhsm/rhsm.log
see here https://gist.github.com/dwojciec/c05459256b0016214883ea52ae62cf21
any helps are welcome
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 26 (15 by maintainers)
I solved it now. dnsmasq ran on my MAC OSX I have just
sudo launchctl stop homebrew.mxcl.dnsmasqand now it’s working
Thanks again for all your help.
@sensadrome The error about seeing a password should be filed against CDK, http://issues.jboss.org/ This is likely do to the way libmachine handles the ssh command (as it fails, it dumps it). Seems we didn’t find all the cases…
I am also seeing this error - and can confirm that either stopping the local dnsmasq server or making it listen on all interfaces (
listen-address=0.0.0.0) will alleviate the issue (presumably the latter is not desired since it will break any internal dns?).It should also be noted that the error is reported in the console and spits out the RHN password which is, presumably, not desirable.