Bug 1038645 - engine-setup seems to finish but unable to log in on 3.3.1-x on RHEL 6.5
Summary: engine-setup seems to finish but unable to log in on 3.3.1-x on RHEL 6.5
Keywords:
Status: CLOSED DUPLICATE of bug 1023538
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-installer
Version: 3.3
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Yedidyah Bar David
QA Contact:
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-05 14:56 UTC by dijuremo
Modified: 2013-12-16 21:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-16 21:14:42 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
engine log file (12.60 KB, text/plain)
2013-12-05 14:56 UTC, dijuremo
no flags Details

Description dijuremo 2013-12-05 14:56:15 UTC
Created attachment 833194 [details]
engine log file

Description of problem:

Password is not correctly set with engine-setup after upgrading to 3.3.1 on RHEL 6.5

The password is accepted during setup, but then you can not login with the admin account. Also, you are unable to reset the password:

[root@phys-vmm ~]# engine-config -g AdminPassword
AdminPassword: Failed to decrypt the current value.
Failed to decrypt the current value.
[root@phys-vmm ~]# engine-config -s AdminPassword=interactive
Please enter a password:
Please reenter password:
Failed to encrypt the current value.
Error setting AdminPassword's value. Failed to encrypt the current value.

Version-Release number of selected component (if applicable):
3.3.1-1.el6
3.3.1-2.el6

How reproducible:
Always


Steps to Reproduce:
1. Update to ovirt 3.3.1-1 or 3.3.1-2 rpms
2. If you already had ovirt configure, run engine-cleanup
3. Now run engine-setup and got through all steps

Actual results:
Configuration seems to succeed, but there are problems trying to decrypt the password set during setup, so it is no longer possible to log in. Trying to reset the password results in similar errors in the logs. (See attachment for full details).

Error seems like:

2013-12-02 13:18:36,741 INFO  [org.ovirt.engine.core.utils.LocalConfig] (MSC service thread 1-2) Value of property "SENSITIVE_KEYS" is ",ENGINE_DB_PASSWORD,ENGINE_PKI_TRUST_STORE_PASSWORD,ENGINE_PKI_ENGINE_STORE_PASSWORD".
2013-12-02 13:18:37,283 INFO  [org.ovirt.engine.core.bll.Backend] (MSC service thread 1-4) Start initializing Backend
2013-12-02 13:18:38,435 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (MSC service thread 1-4) Failed to decrypt value for property LocalAdminPassword will be used encrypted value: java.lang.RuntimeException: Failed to locate key '1'


Expected results:
Should be able to configure the engine and set the password


Additional info:
Downgrading to 3.3.0-1.el6 and running engine-setup allows you to configure the engine and password properly

Comment 1 Yedidyah Bar David 2013-12-16 08:03:25 UTC
Hello,

Can you please send the output of 'java -version'? If it's IBM's jdk, can you change it to OpenJDK by running 'update-alternatives --config', then choosing openjdk (assuming it's installed), then try again?

Thanks and best regards,
-- 
Didi

Comment 2 Yedidyah Bar David 2013-12-16 11:08:39 UTC
(In reply to Yedidyah Bar David from comment #1)
> Hello,
> 
> Can you please send the output of 'java -version'? If it's IBM's jdk, can
> you change it to OpenJDK by running 'update-alternatives --config', then
> choosing openjdk (assuming it's installed), then try again?
> 

Sorry, I do not think it's related, as 3.3.1 already had code to require and use openjdk.

Can you please send the list of installed packages ('rpm -qa')?

Thanks,
-- 
Didi

Comment 3 dijuremo 2013-12-16 20:01:53 UTC
Hi,

The 3.3.1 rpms do not seem to require openjdk. I did have the IBM java 

[root@phys-vmm ~]# java -version
java version "1.7.0"
Java(TM) SE Runtime Environment (build pxa6470sr6-20131015_01(SR6))
IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References 20131013_170512 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR6_20131013_1510_B170512
JIT  - r11.b05_20131003_47443
GC   - R26_Java726_SR6_20131013_1510_B170512_CMPRSS
J9CL - 20131013_170512)
JCL - 20131011_01 based on Oracle 7u45-b18

I am currently on the old version, do you want me to go ahead and re-test with openjdk for you?

Comment 4 Yedidyah Bar David 2013-12-16 20:43:48 UTC
(In reply to dijuremo from comment #3)
> Hi,
> 
> The 3.3.1 rpms do not seem to require openjdk. I did have the IBM java 

Are you certain about that? I think it does require it, but does not forbid
having other versions, and even having another one as default. What is the output of this:

yum provides java

> 
> [root@phys-vmm ~]# java -version
> java version "1.7.0"
> Java(TM) SE Runtime Environment (build pxa6470sr6-20131015_01(SR6))
> IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References
> 20131013_170512 (JIT enabled, AOT enabled)
> J9VM - R26_Java726_SR6_20131013_1510_B170512
> JIT  - r11.b05_20131003_47443
> GC   - R26_Java726_SR6_20131013_1510_B170512_CMPRSS
> J9CL - 20131013_170512)
> JCL - 20131011_01 based on Oracle 7u45-b18

This means that ibm is your default, which you can change using update-alternatives.

> 
> I am currently on the old version, do you want me to go ahead and re-test
> with openjdk for you?

Please do.

However, as I said, we have a script which should select the right java version for the engine:

/usr/share/ovirt-engine/bin/java-home

What does it output?

And what is the output of:

$(/usr/share/ovirt-engine/bin/java-home)/bin/java -version

Just today, without relation to your bug, a fix was posted to this script to exit if a good version is not found, http://gerrit.ovirt.org/22416 , but I am not sure it's relevant to your bug.

Thanks for the report and all the tests!

Regards,
-- 
Didi

Comment 5 dijuremo 2013-12-16 21:08:49 UTC
> > The 3.3.1 rpms do not seem to require openjdk. I did have the IBM java 
> 
> Are you certain about that? I think it does require it, but does not forbid
> having other versions, and even having another one as default. What is the
> output of this:
> 
> yum provides java

You are correct, I did a yum install openjdk, which in turn updated (not installed) the older version I had in the machine. I have switched over to openjdk now using:

update-alternatives --config java

[root@phys-vmm ~]# java -version
java version "1.7.0_45"
OpenJDK Runtime Environment (rhel-2.4.3.4.el6_5-x86_64 u45-b15)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

Now I have the correct one.

> 
> > 
> > [root@phys-vmm ~]# java -version
> > java version "1.7.0"
> > Java(TM) SE Runtime Environment (build pxa6470sr6-20131015_01(SR6))
> > IBM J9 VM (build 2.6, JRE 1.7.0 Linux amd64-64 Compressed References
> > 20131013_170512 (JIT enabled, AOT enabled)
> > J9VM - R26_Java726_SR6_20131013_1510_B170512
> > JIT  - r11.b05_20131003_47443
> > GC   - R26_Java726_SR6_20131013_1510_B170512_CMPRSS
> > J9CL - 20131013_170512)
> > JCL - 20131011_01 based on Oracle 7u45-b18
> 
> This means that ibm is your default, which you can change using
> update-alternatives.
> 
> > 
> > I am currently on the old version, do you want me to go ahead and re-test
> > with openjdk for you?
> 
> Please do.
> 
> However, as I said, we have a script which should select the right java
> version for the engine:
> 
> /usr/share/ovirt-engine/bin/java-home
> 
> What does it output?
> 
> And what is the output of:
> 
> $(/usr/share/ovirt-engine/bin/java-home)/bin/java -version

[root@phys-vmm ~]# /usr/share/ovirt-engine/bin/java-home
/usr/lib/jvm/jre
[root@phys-vmm ~]# $(/usr/share/ovirt-engine/bin/java-home)/bin/java -version
java version "1.7.0_45"
OpenJDK Runtime Environment (rhel-2.4.3.4.el6_5-x86_64 u45-b15)
OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode)

> 
> Just today, without relation to your bug, a fix was posted to this script to
> exit if a good version is not found, http://gerrit.ovirt.org/22416 , but I
> am not sure it's relevant to your bug.
> 
> Thanks for the report and all the tests!
> 

Now I was able to successfully run and configure Ovirt with engine-setup and the password works properly on the web interface!

Comment 6 Alon Bar-Lev 2013-12-16 21:14:42 UTC
Thanks!

*** This bug has been marked as a duplicate of bug 1023538 ***


Note You need to log in before you can comment on or make changes to this bug.