Bug 1012831 - Failed to decrypt value for property LocalAdminPassword in engine.log
Summary: Failed to decrypt value for property LocalAdminPassword in engine.log
Keywords:
Status: CLOSED DUPLICATE of bug 994454
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yair Zaslavsky
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 08:45 UTC by Artyom
Modified: 2016-02-10 19:29 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-29 10:51:32 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Engine log (230.25 KB, text/x-log)
2013-09-27 08:45 UTC, Artyom 		no flags Details
View All

Description Artyom 2013-09-27 08:45:50 UTC 
Created attachment 803825 [details]
Engine log

Description of problem:
Many errors of type "Failed to decrypt value for property LocalAdminPassword will be used encrypted value: javax.crypto.BadPaddingException: doFinal() failed"

Version-Release number of selected component (if applicable):
is16
ovirt-hosted-engine-setup-1.0.0-0.4.beta.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. install ovirt-hosted-engine-setup
2. finish hosted-engine --deploy process
3. Enter to engine vm and check engine.log

Actual results:
Many errors of type "Failed to decrypt value for property LocalAdminPassword will be used encrypted value: javax.crypto.BadPaddingException: doFinal() failed"

Expected results:
No error in engine.log

Additional info:
Comment 1 Alon Bar-Lev 2013-09-27 09:21:41 UTC 
two of these encryption exception are typical at startup.

but yair, it is time to understand why the default 123456 is being decrypted at startup.
Comment 2 Yair Zaslavsky 2013-09-29 10:51:32 UTC 

*** This bug has been marked as a duplicate of bug 994454 ***
Note You need to log in before you can comment on or make changes to this bug.