Re: [Users] Installing ovirt-nightly problems
Jason Brooks wrote:
On 11/02/2012 05:24 AM, Joop wrote:
> Since I had some problems getting bonding working correctly in my
> ovirt-3.1 test installation I decide to start all over with a clean
> install and try the nightly, the webcast about bonding is using a
> nightly.
> That didn't go to well :-(
> What I did:
> - install Fedora-17 from live CD
> - yum upgrade --exclude=kernel*
> (stayed on 3.3.4-5)
The NFS issue that required a pre-3.5 kernel has been fixed -- you
should be able to use an up to date kernel now.
Yes I know but had gluster working
using 3.3.4-5 and didn't want to
change more things just in case I had problems.
> - yum localinstall
> http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
> - enabled nightly in ovirt.repo
> - yum install ovirt-engine
>
> Ended up with the following nightly rpms:
> ovirt-engine-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-backend-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-cli-3.2.0.5-1.20121025.git4189352.fc17.noarch
Users are having trouble with mis-matched ovirt-engine-cli and
ovirt-engine-sdk packages --> mixing 3.2 with 3.1. It interferes with
the all in one installer, and interferes with the iso uploader:
https://bugzilla.redhat.com/show_bug.cgi?id=869457
I read that on the list but I
had a problem with creating the database
long before I start using iso-uploader or sdk scripts. The create I have
solved using a workaround.
Will probably try tomorrow (saturday) whether I can get gluster working
using the installed nightly.
Joop