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

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
>