[Engine-devel] cannot login after re-deploying development environment

Alon Bar-Lev alonbl at redhat.com
Tue Aug 6 18:05:52 UTC 2013



----- Original Message -----
> From: "Einav Cohen" <ecohen at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "engine-devel" <engine-devel at ovirt.org>
> Sent: Tuesday, August 6, 2013 9:00:37 PM
> Subject: Re: [Engine-devel] cannot login after re-deploying	development	environment
> 
> > ----- Original Message -----
> > From: "Alon Bar-Lev" <alonbl at redhat.com>
> > Sent: Tuesday, August 6, 2013 1:46:09 PM
> > 
> > 
> > 
> > ----- Original Message -----
> > > From: "Einav Cohen" <ecohen at redhat.com>
> > > To: "engine-devel" <engine-devel at ovirt.org>
> > > Sent: Tuesday, August 6, 2013 8:31:07 PM
> > > Subject: [Engine-devel] cannot login after re-deploying development
> > > 	environment
> > > 
> > > Hi,
> > > 
> > > The following scenario already happened to me several times:
> > > 
> > > I created a brand new 'engine' data-base, created / deployed
> > > development environment [everything works correctly].
> > > 
> > > After ^^^, I re-create/deploy development environment, this
> > > time without creating a brand new 'engine' data-base (i.e. I
> > > utilized the existing one). Everything seems to be working
> > > correctly, only I cannot login into the web-admin (I fail on
> > > USER_FAILED_TO_AUTHENTICATE CanDoAction).
> > > 
> > > The only workaround I found is to use a brand-new data-base.
> > > 
> > > Any ideas?
> > 
> > If you remove $HOME/ovirt-engine you remove the pki keys.
> > If you do not drop/create the database then the engine-setup is perform
> > upgrade not fresh install.
> > This cause the password to be undecryptable by the new key.
> > Using engine-config -s AdminPassword=interactive will store encrypted
> > password using the new key.
> > If you want fresh install, please also drop/create database.
> 
> Thanks, Alon; so assuming that I want to utilize my existing database
> (after working hard filling it with Hosts, Storage Domains, VMs, etc...),
> but to re-deploy the environment (since I just fetched latest code from
> ovirt master, for example, and I want to run it) - I assume that I should
> NOT remove "$HOME/ovirt-engine" (or "PREFIX"); is it safe to simply
> run:
>  "make clean install-dev PREFIX=[old-PREFIX]"

Right, if there is no significant change this will work, if there are database changes, you should run engine-setup again to perform upgrade.

However, you do able to remove the entire environment without cleaning database, just run engine-setup and then reset password using:

"${HOME}"/ovirt-engine/bin/engine-config -s AdminPassword=interactive

And you will be able to login, but lose encrypted storage secrets.

> or is there something that needs to be removed / some cleanup that should
> be performed in order to make sure that there are no leftovers from
> previous deployments?

As files are only added, there might be side effects.
If, for example, dbscripts were modified, you may have duplicates etc..
In this case you can remove $HOME/ovirt-engine/share/ovirt-engine/dbscripts before install-dev.
There can be other side effects if packaging files are added.

> > 
> > > 
> > > [attached: engine.log, engine-setup output, engine-setup.log]
> > > 
> > > Thanks in advance.
> > > Einav
> > > 
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > > 
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > 
> > 
> > 
> 



More information about the Engine-devel mailing list