[jira] [Resolved] (CLOUDSTACK-1760) [Automation] Router test cases failed while checking dnsmasq service status

["Prasanna Santhanam (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Prasanna Santhanam resolved CLOUDSTACK-1760.
--------------------------------------------

    Resolution: Fixed
      Assignee: Prasanna Santhanam  (was: Girish Shilamkar)

Router tests have been passing for a while now:
http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/suite=test_routers/403/testReport/integration.smoke.test_routers/TestRouterServices/

                
> [Automation] Router test cases failed while checking dnsmasq service status
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1760
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1760
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Test Lab
>    Affects Versions: 4.1.0, 4.2.0
>         Environment: vm ware, kvm 
>            Reporter: Rayees Namathponnan
>            Assignee: Prasanna Santhanam
>             Fix For: 4.1.1
>
>
> Below test cases failed during BVT run in vmware
> test_routers.TestRouterServices.test_01_router_internal_basic test_routers.TestRouterServices.test_02_router_internal_adv
> test_routers.TestRouterServices.test_04_restart_network_wo_cleanup 
> test_routers.TestRouterServices.test_10_network_gc 
> Test cases failed with below error 
>     "Check dnsmasq service is running or not"
> AssertionError: Check dnsmasq service is running or not
> I didn't face any issue during manual testing, please see the result 
> root@r-322-VM:~# service dnsmasq status
> Checking DNS forwarder and DHCP server: dnsmasq(running).
> root@r-322-VM:~#

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira