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

ASF subversion and git services commented on CLOUDSTACK-6777:
-------------------------------------------------------------

Commit 2a28a3c5a4dc006cf8f158dfefa67a331f504c4a in cloudstack's branch 
refs/heads/4.4-forward from [~harikrishna.patnala]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2a28a3c ]

Fixed Regression issues mentioned in following test failures

integration.smoke.test_iso - CLOUDSTACK-6774, CLOUDSTACK-6769
integration.smoke.test_non_contigiousvlan - CLOUDSTACK-6776
integration.smoke.test_primary_storage - CLOUDSTACK-6770
integration.smoke.test_secondary_storage – CLOUDSTACK-6777, CLOUDSTACK-6773
integration.smoke.test_scale_vm - CLOUDSTACK-6768

Signed-off-by: Abhinandan Prateek <aprat...@apache.org>


> [Automation]: Test case failure in test_secondary_storage.py
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6777
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6777
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Automation, KVM
>    Affects Versions: 4.4.0
>            Reporter: Harikrishna Patnala
>             Fix For: 4.4.0
>
>         Attachments: KVM_test_02_sys_template_ready_REPORT.rtf, vmops.log
>
>
> There is test case failure in test_secondary_storage.py
> 1) 
> integration.smoke.test_secondary_storage.TestSecStorageServices.test_02_sys_template_ready
> Error Message
> Builtin template is not ready No route to host in zone 
> 9459d36e-a477-4a60-890b-2bc48edf1410
> -------------------- >> begin captured stdout << ---------------------
> === TestName: test_02_sys_template_ready | Status : FAILED ===
> Attached Test reports and Management server logs



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to