[Ovirt-devel] ovirt-server-installer problems

[Perry Myers]

I've applied the patches from Joey onto next:
[PATCH server] RESEND - required changes to move from ovirt-recipe to 
ovirt-server-installer
[PATCH appliance] RESEND - required changes to move from ovirt-recipe to 
ovirt-server-installer
[PATCH release] RESEND - required changes to move from ovirt-recipe to 
ovirt-server-installer
[PATCH server installer] freeipa_prompt cleanup, selinuxenabled prompt 
refactor, nameserver now lists 127.0.0.1 entry
[PATCH server] dns forward/reverse lookup update / dnsdomainname is 
default for dhcp domain

In conjunction with the temp qpid hack that I just posted:
[PATCH appliance] Temporary hack so qpidd will start up properly

This patch series should remove the need for ovirt-recipe repo and RPM and 
replaces appliance creation with use of ovirt-server-installer.

Ran into a few problems with the appliance after applying these patches. 
First thing is that during ace processing the ovirt-rails-mongrel service 
is started, but later in init the normal ovirt-rails-mongrel service tries 
to start again and that causes errors on the console.  Though I think they 
are harmless.

No obvious errors in ace.log, but when you try to bring up Firefox to log 
into the UI it doesn't accept the standard ovirtadmin/ovirt authentication.

Ah, that's because with the new installer the password changed to 
'password'.  Ok that's not a problem, but we should make people aware of 
the change.

Also, on reboot after first install, ace fails to refresh the appliance. 
Log says:
> Fri Jan 30 03:41:41 +0000 2009 //postgres::bundled/Single_exec[create_ovirt_development_db]/returns (err): change from notrun to 0 failed: /usr/bin/createdb ovirt_development returned 1 instead of 0 at /usr/share/ace/modules/ovirt/manifests/postgres.pp:57

Looks like on reboots the ace service is trying to update when it is not 
necessary to update.  i.e. no new packages were installed, so why is is 
trying to update the installation?  And if there were new packages 
installed, looks like the update would fail anyhow because the it's trying 
to create the ovirt db and since it already exists that fails.

Another problem is that the /etc/dnsmasq.conf file needs to have:
#conf-dir=/etc/dnsmasq.d
uncommented otherwise it won't pick up any files in that directory to process.

Also noticed that /etc/dnsmasq.d/ovirt-dhcp.conf on appliance contained:
> interface=eth1
> dhcp-range=192.168.50.3,192.168.50.10
> domain=priv.ovirt.org
> dhcp-option=option:router,192.168.50.1
> dhcp-option=option:ntp-server,192.168.222.211
> dhcp-option=12
> no-resolv
> local=/priv.ovirt.org/
> server=

This is wrong for a few reasons....  ntp-server should be 192.168.50.2, 
dhcp-range shouldn't be so restrictive.  Open up at least to .50 so a few 
more hosts can be booted.  And there is no eth1 interface on the 
appliance.  Everything is on eth0

Next problem....

/var/lib/tftpboot is empty which means the cobbler-import script was never 
run.  That script needs to be run on the appliance to create the ovirt 
node pxe boot images and install them for tftp.  It also creates the 
Fedora cobbler distro so you can install Fedora from the appliance.

That's as far as I got in testing, but it looks like there are a few 
things that need to be cleaned up in the ovirt-server-installer before the 
next round....

Perry

-- 
|=-        Red Hat, Engineering, Emerging Technologies, Boston        -=|
|=-                     Email: pmyers at redhat.com                      -=|
|=-         Office: +1 412 474 3552   Mobile: +1 703 362 9622         -=|
|=- GnuPG: E65E4F3D 88F9 F1C9 C2F3 1303 01FE 817C C5D2 8B91 E65E 4F3D -=|