Red Hat Bugzilla – Bug 985168
nslookup issue with engine-setup
Last modified: 2013-07-24 08:21:05 EDT
Created attachment 774590 [details]
first part of engine-setup log output
This issue has been discussed on the net and I still don't see any solution. I'm with Fedora 19 and ovirt (from Fedora 19).
I've set in /etc/hosts the machine name as well as in /etc/sysconfig/network
# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
I can ping it, I can ssh to it (all from the same machine), but the engine-setup scripts uses nslookup which naturally fails.
Do I have to setup a DNS server? why is it ignoring the hosts file?
engine-setup log files enclosed.
Is 3.2 supported on Fedora 19?
the problem with the ovirt repo on Fedora 19 (if I add this repo) is that it will install the oVirt from Fedora 18, and there is already oVirt in Fedora 19 without this repo
More info: issue seems solved with nightly-build and with engine-setup-2 script instead of engine-setup
(In reply to Sandro Bonazzola from comment #1)
> Is 3.2 supported on Fedora 19?
I think we should aim 3.3 for fedora 19 at this point.
Could someone mention on the installation pages of oVirt to not run the release on F19? I spent 8 hours on this yesterday.
I've no rights for updating http://www.ovirt.org/Download , can you please add a note in that page to use nightly or beta repo on F19 because 3.2 stable is not supported there?
Closing this bug as nextrelease since this issue won't be fixed in 3.2 and is already fixed for 3.3.0.
"Fedora 19 is not supported for 3.2, please use 3.3 if you want to use Fedora 19 " added to ovirt.org download page