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

ASF GitHub Bot commented on CLOUDSTACK-10319:
---------------------------------------------

blueorangutan commented on issue #2480: CLOUDSTACK-10319: Prefer TLSv1.2, 
deprecate TLSv1.0,1.1
URL: https://github.com/apache/cloudstack/pull/2480#issuecomment-371596013
 
 
   <b>Trillian test result (tid-2342)</b>
   Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
   Total time taken: 22351 seconds
   Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2480-t2342-kvm-centos7.zip
   Intermitten failure detected: /marvin/tests/smoke/test_host_maintenance.py
   Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
   Smoke tests completed. 66 look OK, 1 have error(s)
   Only failed tests results shown below:
   
   
   Test | Result | Time (s) | Test File
   --- | --- | --- | ---
   test_hostha_enable_ha_when_host_in_maintenance | `Error` | 3.74 | 
test_hostha_kvm.py
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Prefer TLSv1.2 and deprecate TLS 1.0/1.1
> ----------------------------------------
>
>                 Key: CLOUDSTACK-10319
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10319
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Major
>             Fix For: 4.12.0.0, 4.11.1.0
>
>
> TLS 1.0 and 1.1 are both recommended to not be used. The aim would be to make 
> cloudstack prefer tls 1.2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to