From: "Simone Tiraboschi" <stirabos(a)redhat.com>
To: "Shmuel Melamud" <smelamud(a)redhat.com>
Cc: "Yedidyah Bar David" <ybardavi(a)redhat.com>, devel(a)ovirt.org
Sent: Thursday, May 7, 2015 10:50:32 AM
Subject: Re: [ovirt-devel] Error in engine-setup in ovirt 3.5
----- Original Message -----
> From: "Shmuel Melamud" <smelamud(a)redhat.com>
> To: devel(a)ovirt.org, "Yedidyah Bar David" <ybardavi(a)redhat.com>
> Sent: Thursday, May 7, 2015 10:26:39 AM
> Subject: [ovirt-devel] Error in engine-setup in ovirt 3.5
> Can you help me with this? I'm trying to install oVirt 3.5.3. I've built
> Engine in a separate directory, created a separate DB and now running
> /home/smelamud/engine-root/3.5/bin/engine-setup. After answering all
> questions I get:
> --== OVIRT ENGINE CONFIGURATION ==--
> Skipping storing options as database already prepared
> --== PKI CONFIGURATION ==--
> Organization name for certificate [tlv.redhat.com
> --== APACHE CONFIGURATION ==--
> --== SYSTEM CONFIGURATION ==--
> --== MISC CONFIGURATION ==--
> --== END OF CONFIGURATION ==--
> [ INFO ] Stage: Setup validation
> [WARNING] Less than 16384MB of memory is available
> [ INFO ] Cleaning stale zombie tasks and commands
> [ ERROR ] Failed to execute stage 'Setup validation': LooseVersion instance
> has no attribute 'version'
> [ INFO ] Stage: Clean up
> Log file is located at
> [ INFO ] Generating answer file
> [ INFO ] Stage: Pre-termination
> [ INFO ] Stage: Termination
> [ ERROR ] Execution of setup failed
> Looks like some bug in engine-setup.
Ok, got it.
on engine-setup we need to discriminate if we are upgrading or if we are
deploying for the first time: generally we do it identifying it you have an
existing DB instance from a previous setup and you have it cause you
So engine-setup assumes that is an upgrade but something is missing (in this
precise case, info about the previously uninstalled release from postinstall
file) and so it fails.
If you need I can help to forcefully complete that setup but is not really a
supported configuration on user side.
to your answerfile should be enough to workaround on that.
> Log file is attached.
> Devel mailing list
Devel mailing list