[Users] Installing ovirt-nightly problems
Jason Brooks
jbrooks at redhat.com
Fri Nov 2 17:11:22 UTC 2012
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.
> - 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
> ovirt-engine-config-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-dbscripts-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-genericapi-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-notification-service-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-restapi-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-sdk-3.2.0.2-1.20121022.git8013c12.fc17.noarch
Here's that 3.2 sdk pkg.
> ovirt-engine-setup-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-tools-common-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-userportal-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-engine-webadmin-portal-3.1.0-3.20121031.gitdd0ad7f.fc17.noarch
> ovirt-image-uploader-3.1.0-1.fc17.noarch
> ovirt-iso-uploader-3.1.0-1.fc17.noarch
> ovirt-log-collector-3.1.0-1.fc17.noarch
> ovirt-release-fedora-4-2.noarch
>
> ran engine-setup and gave default answers where possible.
> Instalation stopped with a Creating Database... ERROR
> Attached are the logs and the real error is in the enginedb log:
> user name is: engine
> Creating uuid-ossp extension...
> psql:/tmp/tmp.8hb5EYqc0Y:1: ERROR: permission denied to create extension
> "uuid-ossp"
> HINT: Must be superuser to create this extension.
>
> It is right, user engine isn't a superuser and thus not allowed to create
> the extension.
> I modified the CREATE ROLE statement to include SUPERUSER role and
> restarted engine-setup, now it continues and runs til the end.
> Looking at the code I think that the second invocation of creating the
> uuid-ossp extension isn't needed but commenting that line gives an error
> too.
> Looking at ovirt-stable and comparing the scripts in
> /usr/share/ovirt-engine does show some changes but I don't know enough
> internals to see what changed that causes this.
>
>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
--
@jasonbrooks
More information about the Users
mailing list