[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14246453#comment-14246453 ]
ASF subversion and git services commented on CLOUDSTACK-8070: ------------------------------------------------------------- Commit 1a66b3b5c6b88e9180377e1b5e1206fe2f892c46 in cloudstack's branch refs/heads/hotfix/scp-exception from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1a66b3b ] CLOUDSTACK-8070: Upgrade router.ram.size using encryption util Upgrade fails if value is set using plain text encoding, the value needs to be encrypted (if a key was provided during db was setup). Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> (cherry picked from commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d) Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> > 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.5.0, 4.4.3, 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)