Bug 991350 - [RHEVM][backend] error message on egine start/restart -> Failed to decrypt value for property AttestationTruststorePass will be used encrypted value: javax.crypto.BadPaddingException: Data must start with zero
Summary: [RHEVM][backend] error message on egine start/restart -> Failed to decrypt va...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: x86_64
OS: Linux
high
low
Target Milestone: ---
: 3.3.0
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-02 08:15 UTC by Martin Pavlik
Modified: 2016-02-10 20:13 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-05 13:13:34 UTC
oVirt Team: SLA
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
log_collector (6.06 MB, application/x-xz)
2013-08-02 08:15 UTC, Martin Pavlik 		no flags Details
View All

Description Martin Pavlik 2013-08-02 08:15:33 UTC 
Created attachment 781878 [details]
log_collector

Description of problem:
following error message appears in log on each start/restart of ovirt engine service

2013-08-02 10:03:27,898 ERROR [org.ovirt.engine.core.dal.dbbroker.generic.DBConfigUtils] (ServerService Thread Pool -- 37) Failed to decrypt value for property AttestationTruststorePass will be used encrypted value: javax.crypto.BadPaddingException: Data must start with zero


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.13.master.el6ev 

How reproducible:
100%

Steps to Reproduce:
1. service ovirt-engine restart
2. check /var/log/ovirt-engine/engine.log
3.

Actual results:
error message appears -> engine starts fine

Expected results:
engine starts w/o error message

Additional info:
Comment 1 Doron Fediuck 2013-08-05 13:13:34 UTC 
This is not a bug.
DBConfigUtils was designed to fallback to using the current value if decryption fails. So it will issue an error and use the existing value.
Note You need to log in before you can comment on or make changes to this bug.