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

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

rhtyd commented on issue #2211: CLOUDSTACK-10013: Migrate systemvmtemplate to 
Debian9
URL: https://github.com/apache/cloudstack/pull/2211#issuecomment-353763673
 
 
   Thanks @borisstoyanov :) 
   Based on the last smoketests run we've 0 errors for KVM (centos7)  and 
VMware (5.5u3 with svs and 6.5u1 with dvs). The ssvm test case failed for 
XenServer 65sp1 due to slow starts and cloud/java process was not running 
however after sometime it started. When the agent keystore is setup for 
cpvm/ssvm it restarts the `cloud` process so if the ssh happens around this 
time, the process may appear dead as the `ssvm-check.sh` does not systemctl 
status but uses `ps -eaf | grep java`. Ignoring this case, all tests have 
passed on XenServer 65sp1 too.
   
   I'll merge the PR now and post-merge I'll kick smoke and component tests. 
Some component tests have been fixed in #2344 and will work with @borisstoyanov 
and others to further stabilize tests and master.

----------------------------------------------------------------
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:
[email protected]


> Migrate to Debian9 systemvmtemplate
> -----------------------------------
>
>                 Key: CLOUDSTACK-10013
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10013
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: Future, 4.11.0.0
>
>
> Migrate to debian9 based systemvmtemplate



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to