[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244237#comment-14244237 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 5519095a2970103ac3acbd948ae1908aa2612c41 in cloudstack's branch refs/heads/4.3 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5519095 ] CLOUDSTACK-8070: during 4.3.1 to 4.3.2 upgrade encrypt config that are hidden In case there is an encryption key/password is provided the value, specifically for router.ram.size will be encrypted otherwise it will remain plain text. Signed-off-by: Rohit Yadav > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244252#comment-14244252 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 94cad49e07d45c7e252fbe9f35e4fab8e543c259 in cloudstack's branch refs/heads/4.4 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=94cad49 ] CLOUDSTACK-8070: during 4.4.2 to 4.4.3 upgrade encrypt config that are hidden In case there is an encryption key/password is provided the value, specifically for router.ram.size will be encrypted otherwise it will remain plain text. Signed-off-by: Rohit Yadav > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244412#comment-14244412 ] Harikrishna Patnala commented on CLOUDSTACK-8070: - Yes Rohit, you are right this needs to fix in master as well. Will do it asap > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244591#comment-14244591 ] Rohit Yadav commented on CLOUDSTACK-8070: - Cool, just wanted to confirm. I already have a fix in one of my branches, will push it right away. > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244598#comment-14244598 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d in cloudstack's branch refs/heads/4.5 from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6321a29 ] 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 > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244599#comment-14244599 ] ASF subversion and git services commented on CLOUDSTACK-8070: - Commit 1a66b3b5c6b88e9180377e1b5e1206fe2f892c46 in cloudstack's branch refs/heads/master 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 (cherry picked from commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d) Signed-off-by: Rohit Yadav > 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)
[jira] [Commented] (CLOUDSTACK-8070) Upgrade to 4.3.2 from 4.3.1 fails due to encryption error
[ 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 (cherry picked from commit 6321a29e4336de9ffe96e27968f896ec5a8bf37d) Signed-off-by: Rohit Yadav > 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)
