That patch fixed that issue, (re-tested with build from master this AM) and the upgrade proceeded.

However after the upgrade the engine.ear deployment to jboss is failing. (log files attached)
- DHC


On Sat, Jul 27, 2013 at 1:28 AM, Alon Bar-Lev <alonbl@redhat.com> wrote:


----- Original Message -----
> From: "Dead Horse" <deadhorseconsulting@gmail.com>
> To: "Alon Bar-Lev" <alonbl@redhat.com>
> Cc: "users" <users@ovirt.org>
> Sent: Saturday, July 27, 2013 2:05:08 AM
> Subject: Re: [Users] upgrade to latest master not working
>
> Yep there was a leftover:
> /usr/share/ovirt-engine/setup/plugins/ovirt-engine-setup/releasepreview
>
> I got past that now however it is now failing at the Environment
> customization stage.
>
> Here is the output of engine-upgrade. I have also attached the upgrade log.
>
> [ INFO  ] Stage: Initializing
> [ INFO  ] Stage: Environment setup
>           Log file: /tmp/ovirt-engine-setup-20130726175419.log
>           Version: otopi-3.3.020
>           Configuration files:
> ['/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
> [ INFO  ] Stage: Environment packages setup
> [ INFO  ] Stage: Programs detection
> [ INFO  ] Stage: Environment setup
> [ INFO  ] Stage: Environment customization
> [ ERROR ] Failed to execute stage 'Environment customization': Cannot
> connect to database: server does not support SSL, but SSL was required
> [ INFO  ] Stage: Clean up
>           Log file is located at /tmp/ovirt-engine-setup-20130726175419.log
> [ INFO  ] Stage: Pre-termination
> [ INFO  ] Stage: Termination
>
> - DHC

Correct, thanks!
I prepared a patch[1].

commit 18fe8cf53c519fdb8a4e831faf3b0a6c5a64167b
Author: Alon Bar-Lev <alonbl@redhat.com>
Date:   Sat Jul 27 09:25:27 2013 +0300

    packaging: setup: legacy: ssl flags should be boolean

    Change-Id: I9bc9f59a2a3ac18f613200bf2f9b70948b494b91
    Signed-off-by: Alon Bar-Lev <alonbl@redhat.com>
    Reported-By: Dead Horse <deadhorseconsulting@gmail.com>

[1] http://gerrit.ovirt.org/17359

>
>
>
> On Fri, Jul 26, 2013 at 3:38 PM, Alon Bar-Lev <alonbl@redhat.com> wrote:
>
> >
> > You probably have some leftovers at /usr/share/ovirt-engine/setup, search
> > for releasepreview
> >
> > ----- Original Message -----
> > > From: "Dead Horse" <deadhorseconsulting@gmail.com>
> > > To: "<users@ovirt.org>" <users@ovirt.org>
> > > Sent: Friday, July 26, 2013 11:34:09 PM
> > > Subject: [Users] upgrade to latest master not working
> > >
> > > Trying to upgrade engine built from
> > > commit: dbc3d31110ce372a1fa7e06f64c4a5c64544c679
> > >
> > > To latest engine built from latest master
> > >
> > > running engine-upgrade results in:
> > >
> > > ***L:ERROR Internal Error: No Module named releasepreview
> > >
> > > I know I must be missing something obvious?
> > >
> > > The surrounding versions of otopi, host-deploy, etc do yum upgrade
> > cleanly
> > > however.
> > >
> > > - DHC
> > >
> > > _______________________________________________
> > > Users mailing list
> > > Users@ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/users
> > >
> >
>