cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
Date Fri, 12 Dec 2014 15:08:13 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244236#comment-14244236
] 

Rohit Yadav commented on CLOUDSTACK-8070:
-----------------------------------------

cc [~harikrishna.patnala] [~kishan] I think this may be applicable for upgrades to 4.5.0 as
well as the 442 to 450 sql simply update the router.ram.size value without using a clean decrypt
util like the fix for this issue in case of 4.3; if so, please pick the fix and apply for
4.5 branch as well.

> Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-8070
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8070
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.3.2
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Blocker
>             Fix For: 4.3.2
>
>
> The hidden field ram.router.maxsize was changed in 4.3.2 (to 256), this caused jasypt
to complain when mgmt server starts up. The fix would be encrypt the config values when upgrades
are done.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message