[GitHub] cloudstack issue #1660: CLOUDSTACK-9470: [BLOCKER] Bug in SshHelper affectin...
Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1660 @rhtyd @jburwell Just re-ran Marvin tests. All passes including test_network_acl which fails without this fix. [root@ussarlabcsmgt41 ~]# cat /tmp//MarvinLogs/test_volumes_939G6N/results.txt |grep -v '^ok' test DeployVM in anti-affinity groups for project ... === TestName: test_DeployVmAntiAffinityGroup_in_project | Status : SUCCESS === test DeployVM in anti-affinity groups ... === TestName: test_DeployVmAntiAffinityGroup | Status : SUCCESS === Test Deploy Virtual Machine ... SKIP: Skipping test because suitable hypervisor/host notpresent Test Deploy Virtual Machine from ISO ... === TestName: test_deploy_vm_from_iso | Status : SUCCESS === Test deploy virtual machine with root resize ... === TestName: test_00_deploy_vm_root_resize | Status : SUCCESS === Test proper failure to deploy virtual machine with rootdisksize of 0 ... === TestName: test_01_deploy_vm_root_resize | Status : SUCCESS === Test proper failure to deploy virtual machine with rootdisksize less than template size ... === TestName: test_02_deploy_vm_root_resize | Status : SUCCESS === Test to deploy vm with a first fit offering ... === TestName: test_deployvm_firstfit | Status : SUCCESS === Test deploy VMs using user concentrated planner ... === TestName: test_deployvm_userconcentrated | Status : SUCCESS === Test deploy VMs using user dispersion planner ... === TestName: test_deployvm_userdispersing | Status : SUCCESS === Test userdata as GET, size > 2k ... === TestName: test_deployvm_userdata | Status : SUCCESS === Test userdata as POST, size > 2k ... === TestName: test_deployvm_userdata_post | Status : SUCCESS === Test to create disk offering ... === TestName: test_01_create_disk_offering | Status : SUCCESS === Test to create a sparse type disk offering ... === TestName: test_02_create_sparse_type_disk_offering | Status : SUCCESS === Test to create a sparse type disk offering ... === TestName: test_04_create_fat_type_disk_offering | Status : SUCCESS === Test to update existing disk offering ... === TestName: test_02_edit_disk_offering | Status : SUCCESS === Test to delete disk offering ... === TestName: test_03_delete_disk_offering | Status : SUCCESS === Test to ensure 4 default roles cannot be deleted ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Test to check role, role permissions and account life cycles ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Test for role-rule enforcement in case of multiple mgmt servers ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Test to ensure role in use cannot be deleted ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests normal lifecycle operations for roles ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests role update ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests that default four roles exist ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests role update ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests role update when role is in use by an account ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests concurrent order updation of role permission ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests creation of role permission ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests deletion of role permission ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests listing of default role's permission ... SKIP: Dynamic Role-Based API checker not enabled, skipping test Tests order updation of role permission ... SKIP: Dynamic Role-Based API checker not enabled, skipping test test update configuration setting at zone level scope ... === TestName: test_UpdateConfigParamWithScope | Status : SUCCESS === Test guest vlan range dedication ... === TestName: test_dedicateGuestVlanRange | Status : SUCCESS === Test create public & private ISO ... === TestName: test_01_create_iso | Status : SUCCESS === Test Edit ISO ... === TestName: test_02_edit_iso | Status : SUCCESS === Test delete ISO ... === TestName: test_03_delete_iso | Status : SUCCESS === Test for extract ISO ... === TestName: test_04_extract_Iso | Status : SUCCESS === Update & Test for ISO permissions ... === TestName: test_05_iso_permissions | Status : SUCCESS === Test for copy ISO from one zone to another ... SKIP: Not enough zones available to perform copy template Test delete ISO ... === TestName: test_07_list_default_iso | Status : SUCCESS === Test listing Volumes using 'ids' parameter ... === TestName: test_01_list_volumes | Status : SUCCESS === Test listing Templ
Re: api uploadsslcert encoding issue
Awesome. GJ. Thanks for reporting back. :) On Sep 5, 2016 1:04 PM, "Patrick W." wrote: Figured it out! some special characters within the certificate body itself were not correctly encoded. In the end, all special characters, as well as all line breaks should be encoded to reflect the exact certificate output and format. Will look at improving the doc available out there as this isn't crystal clear. From: Patrick W. Sent: Monday, September 5, 2016 4:50 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue I'm using 4.5.2 Yes you are right, I saw this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-6864 but it was resolved in 4.4 Moreover I've tried the double encoding trick. From: Will Stevens Sent: Monday, September 5, 2016 4:42 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue What acs version are you using? I believe there was a problem with double encoding in some older releases. Maybe someone else can weigh in who knows for sure. On Sep 5, 2016 10:27 AM, "Patrick W." wrote: > Has someone managed to upload a certificate, its chain and its key in a > single call, using the uploadsslcert API command? > > I've done attempts with cloudmonkey, in python, etc. tried all possible > formatting and encoding combinations but I always get errors > > - Expected X509 certificate. Failed due to String index out of range: > - Error parsing certificate data Invalid certificate format. Expected X509 > certificate > - Error parsing certificate data Invalid Certificate format. Failed due to > problem parsing cert: java.security.cert.CertificateException: > java.io.IOException: corrupted stream - out of bounds length found > > Has anybody succeeded with this? if yes, I'd be interested to reuse the > exact same approach. > > thanks! >
Re: api uploadsslcert encoding issue
Figured it out! some special characters within the certificate body itself were not correctly encoded. In the end, all special characters, as well as all line breaks should be encoded to reflect the exact certificate output and format. Will look at improving the doc available out there as this isn't crystal clear. From: Patrick W. Sent: Monday, September 5, 2016 4:50 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue I'm using 4.5.2 Yes you are right, I saw this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-6864 but it was resolved in 4.4 Moreover I've tried the double encoding trick. From: Will Stevens Sent: Monday, September 5, 2016 4:42 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue What acs version are you using? I believe there was a problem with double encoding in some older releases. Maybe someone else can weigh in who knows for sure. On Sep 5, 2016 10:27 AM, "Patrick W." wrote: > Has someone managed to upload a certificate, its chain and its key in a > single call, using the uploadsslcert API command? > > I've done attempts with cloudmonkey, in python, etc. tried all possible > formatting and encoding combinations but I always get errors > > - Expected X509 certificate. Failed due to String index out of range: > - Error parsing certificate data Invalid certificate format. Expected X509 > certificate > - Error parsing certificate data Invalid Certificate format. Failed due to > problem parsing cert: java.security.cert.CertificateException: > java.io.IOException: corrupted stream - out of bounds length found > > Has anybody succeeded with this? if yes, I'd be interested to reuse the > exact same approach. > > thanks! >
Re: api uploadsslcert encoding issue
I'm using 4.5.2 Yes you are right, I saw this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-6864 but it was resolved in 4.4 Moreover I've tried the double encoding trick. From: Will Stevens Sent: Monday, September 5, 2016 4:42 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue What acs version are you using? I believe there was a problem with double encoding in some older releases. Maybe someone else can weigh in who knows for sure. On Sep 5, 2016 10:27 AM, "Patrick W." wrote: > Has someone managed to upload a certificate, its chain and its key in a > single call, using the uploadsslcert API command? > > I've done attempts with cloudmonkey, in python, etc. tried all possible > formatting and encoding combinations but I always get errors > > - Expected X509 certificate. Failed due to String index out of range: > - Error parsing certificate data Invalid certificate format. Expected X509 > certificate > - Error parsing certificate data Invalid Certificate format. Failed due to > problem parsing cert: java.security.cert.CertificateException: > java.io.IOException: corrupted stream - out of bounds length found > > Has anybody succeeded with this? if yes, I'd be interested to reuse the > exact same approach. > > thanks! >
Re: api uploadsslcert encoding issue
What acs version are you using? I believe there was a problem with double encoding in some older releases. Maybe someone else can weigh in who knows for sure. On Sep 5, 2016 10:27 AM, "Patrick W." wrote: > Has someone managed to upload a certificate, its chain and its key in a > single call, using the uploadsslcert API command? > > I've done attempts with cloudmonkey, in python, etc. tried all possible > formatting and encoding combinations but I always get errors > > - Expected X509 certificate. Failed due to String index out of range: > - Error parsing certificate data Invalid certificate format. Expected X509 > certificate > - Error parsing certificate data Invalid Certificate format. Failed due to > problem parsing cert: java.security.cert.CertificateException: > java.io.IOException: corrupted stream - out of bounds length found > > Has anybody succeeded with this? if yes, I'd be interested to reuse the > exact same approach. > > thanks! >
api uploadsslcert encoding issue
Has someone managed to upload a certificate, its chain and its key in a single call, using the uploadsslcert API command? I've done attempts with cloudmonkey, in python, etc. tried all possible formatting and encoding combinations but I always get errors - Expected X509 certificate. Failed due to String index out of range: - Error parsing certificate data Invalid certificate format. Expected X509 certificate - Error parsing certificate data Invalid Certificate format. Failed due to problem parsing cert: java.security.cert.CertificateException: java.io.IOException: corrupted stream - out of bounds length found Has anybody succeeded with this? if yes, I'd be interested to reuse the exact same approach. thanks!
