[Users] Problem setting up new engine with 3.3 on Fedora 19

[Alon Bar-Lev]

----- Original Message -----
> From: "Bob Doolittle" <bob at doolittle.us.com>
> To: users at ovirt.org
> Sent: Sunday, November 3, 2013 10:17:36 PM
> Subject: [Users] Problem setting up new engine with 3.3 on Fedora 19
> 
> Hi,
> 
> I am doing a fresh engine-setup, with all the defaults, using oVirt 3.3
> on Fedora 19 (all updates).
> 
> When I connect to it, it shows my default Datacenter as "Uninitialized"
> and shows no Storage (it should show ISODOMAIN). I can see that my
> ISODOMAIN appears to be created and NFS exported, and I can mount it
> [*]. It's not actually mounted anywhere, however, which seems suspicious.
> 
> In the Storage tab, if I go to create a New Domain, it shows "Data
> Center Default (NFS) !", and if I mouse-over the exclamation point it
> says "Data Center is uninitialized, in order to initialize add a data
> domain". But I can't actually create a new domain, because the "Use
> Host" pull-down is empty.
> 
> Should I not see my local host in that pulldown menu? How am I supposed
> to add local storage?
> I can't find any errors in the log that logs that look relevant. I checked:
> 
> engine-config.log (no errors)
> 
> setup/ovirt-engine-setup-*.log (no errors)
> 
> engine.log has no errors that look relevant, but it does have a lot of
> odd java exceptions, which can be viewed here:
> http://pastebin.com/TYxi3p36
> 
> Any suggestions?
> 
> -Bob
> 
> * There's a bug in F19 that interferes with engine-setup
> (https://bugzilla.redhat.com/show_bug.cgi?id=970595). Systemd does not
> start the NFS service at boot and you have to do a weird kludge to
> actually get it to start at bootup (described in the bug report). I've
> applied the workaround so that's not my issue but it's worth mentioning
> here.

Thanks for the reference, sandro, we may want to depend on this newer package.

> Unfortunately engine-setup doesn't detect that the service is down
> when you attempt to configure an NFS storage domain. That sounds like an
> engine-setup bug to me - it should check and warn the user, which would
> go a fair ways towards mitigating the issue in F19,

I am not sure I follow, we cannot be a database for every known [and future known] bug out there.

We do restart nfs post setup[1], please send your complete setup log.

> and may be more
> important for other platforms which may make different assumptions about
> the default behavior of the NFS service (Fedora assumes it should be
> running, it's just a bug there, but other platforms may arguably assume
> it should not be running by default).

We are not making that assumption as far as I understand.

Regards,
Alon Bar-Lev.

[1] http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=packaging/setup/plugins/ovirt-engine-setup/system/nfs.py;h=ea72ffaeee93cd35d950e282cd58c743aa37ae66;hb=refs/heads/ovirt-engine-3.3.1#l198