Hide Forgot
Created attachment 1143351 [details] answer file created after running the engine-setup is attached (don't have the setup.log file). Please ignore the .backup extension. Description of problem: After build+install of ovirt-engine on a clean environment, running the engine-setup tool doesn't ask you to set the password of the admin user (the user for the admin portal). Version-Release number of selected component (if applicable): none How reproducible: see below Steps to Reproduce: 1. run build and install of ovirt-engine from the master repository on a clean environment (i.e. no previous installation existed for the ovirt-engine). 2. run the bin/engine-setup and choose installation for a development environment. 3. the engine-setup won't ask you for the admin user password (for the admin portal). 4. Checking the the answer file after the installation completed, showed that the property OVESETUP_CONFIG/adminPassword was set to "none:None". Actual results: Not sure which password is set for the admin user. Expected results: The the engine-setup should ask you to set the admin user password. Additional info: answer file created after running the engine-setup is attached (don't have the setup.log file). Please ignore the .backup extension.
Unless this is easily reproducible (didn't try yet), I don't think we can do much without the setup log. Based on the attached answer file, specifically 'OVESETUP_CONFIG/engineDbBackupDir=str:/home/sgratch/ovirt-engine/var/lib/ovirt-engine/backups', I am guessing this is dev env, changing subject accordingly.
This bug occurred while running the engine-setup for a dev environment on my laptop (as mentioned in "Steps to Reproduce" - section 2). It reproduced on my environment twice. Each time I removed the engine installation folders to have a clean env, run the build and then the engine-setup for dev. The problem was solved only after I run the bin/engine-cleanup utility and manually removed the answer file (the one attached to this bug) and only then run the engine-setup which asked for the admin password.
(In reply to Sharon Gratch from comment #2) > It reproduced on my environment twice. Please attach setup logs. > The problem was solved only after I run the bin/engine-cleanup utility and > manually removed the answer file (the one attached to this bug) and only > then run the engine-setup which asked for the admin password. Where did you remove it from? How was it created in the first place? How do you run setup?
(In reply to Yedidyah Bar David from comment #3) > (In reply to Sharon Gratch from comment #2) > > It reproduced on my environment twice. > > Please attach setup logs. I don't have the setup logs. > > > The problem was solved only after I run the bin/engine-cleanup utility and > > manually removed the answer file (the one attached to this bug) and only > > then run the engine-setup which asked for the admin password. > > Where did you remove it from? > How was it created in the first place? > How do you run setup? The scenario in details: 1. run the bin/engine-setup on my laptop where no previous engine installation existed (setup for dev, done after I build the engine from master..). 2. no admin password was asked to set during that setup. 3. I removed the engine installation and repeat steps 1-2 again and the problem was reproduced. 4. I run bin/engine-cleanup, removed the answer file under the var/lib/ovirt-engine/setup/answers folder (attached) and only then run the bin/engine-setup. 5. this time I was asked to set the user admin password.
(In reply to Sharon Gratch from comment #4) > (In reply to Yedidyah Bar David from comment #3) > > (In reply to Sharon Gratch from comment #2) > > > It reproduced on my environment twice. > > > > Please attach setup logs. > > I don't have the setup logs. But you said you reproduced this twice. We can't do much without setup logs. You should be able to find them under var/log/ovirt-engine/setup .
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
As written above, I didn't have setup logs (don't remember why). Only answer file, which is already attached.
Very well. Please reopen if you manage to reproduce, and attach setup logs. Thanks.
Now happened also to me, so I think it's a reproduction: 1. install dev env to PREFIX 2. create empty db/user/etc 3. engine-setup in PREFIX, use this db/user 4. rm -rf PREFIX 5. install again dev env to PREFIX 6. engine-setup in PREFIX, use same db/user engine-setup does not prompt for admin password, as the database is not empty, and the password is supposedly already set there. see also bug 1259782.