locked
Test agent cannot connect to Test controller on Windows Azure RRS feed

  • Question

  • I wanted to create a Test rig on cloud. I have created a windows azure hosted service that installsTest Controller and configures it with on premise DB. I have created another hosted service that installs Test Agent. I have enabled Virtual network in the Azure service by providing Activation token taken from azure portal. I also created a Azure Connect Group in which I added my local endpoint(On Premise DB) and windows azure roles( Test Controller rand Test Agent). When I deploy this on azure I am facing problem of Test Agent connectivity with Test Controller.

    Test Controller can ping to my on premise DB machine and vice versa. But my test controller machine cannot ping test agent machine or vice versa on cloud.

    I have ensured following things on test Controller

    • User testagent is part of group TeamTestAgentService
    • User testagent is also administrator on TestController hosted service.
    • Firewall exceptions have been added

     If I try to ping two azure machines I cannot do that. By default azure has ping disabled so I added following firewall rule

     netsh advfirewall firewall add rule name="ICMPv6" dir=in action=allow enable=yes protocol=icmpv6

     but it still does not work. I think if these two machines will be able to ping each other the problem of test agent connectivity to test controller on cloud will be solved.

    Thursday, February 16, 2012 1:31 PM

Answers

  • Reply from http://social.msdn.microsoft.com/profile/rlfh/

    It won’t work as you have it now. The controller and agents have to be in different roles, but also the controller you need to install Azure Connect as an endpoint– not enabled as a role. So, you want to configure the Controller manually, then it should show up so you can add it to the Connect From list. Leave the agents as they are(azure connect as a role) and then it should work. The Roles in the Connect TO: part won’t be allowed to intercommunicate, though an endpoint can – since they have the option you selected to allow this.

    My problem was solved when I manually installed Azure Connect endpoint from azure portal on the controller machine instead of enabling it as a Role in Virtual network.



    • Marked as answer by Ozair Saleem Monday, February 20, 2012 8:01 AM
    • Edited by Ozair Saleem Monday, February 20, 2012 8:02 AM
    Monday, February 20, 2012 8:01 AM

All replies

  • Take a look at http://social.technet.microsoft.com/wiki/contents/articles/6073.windows-azure-performance-testing-using-the-power-of-cloud.aspx

    It has some batch files which you can run on the agents.

    Thnaks,

    Anuj


    http://www.anujchaudhary.com

    Thursday, February 16, 2012 8:16 PM
  • Hi Ozair,

    Any update? Could you get useful information from Anuj's reply?

    Would you mind letting us know the result of the suggestion?

    Best Regards,



    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us

    Monday, February 20, 2012 6:58 AM
    Moderator
  • Reply from http://social.msdn.microsoft.com/profile/rlfh/

    It won’t work as you have it now. The controller and agents have to be in different roles, but also the controller you need to install Azure Connect as an endpoint– not enabled as a role. So, you want to configure the Controller manually, then it should show up so you can add it to the Connect From list. Leave the agents as they are(azure connect as a role) and then it should work. The Roles in the Connect TO: part won’t be allowed to intercommunicate, though an endpoint can – since they have the option you selected to allow this.

    My problem was solved when I manually installed Azure Connect endpoint from azure portal on the controller machine instead of enabling it as a Role in Virtual network.



    • Marked as answer by Ozair Saleem Monday, February 20, 2012 8:01 AM
    • Edited by Ozair Saleem Monday, February 20, 2012 8:02 AM
    Monday, February 20, 2012 8:01 AM
  • Hi Ozair,

    Thank you for sharing your solutions and experience here. It will be very beneficial for other community members who have similar questions.

    Have a nice day,



    Jack Zhai [MSFT]
    MSDN Community Support | Feedback to us

    Monday, February 20, 2012 10:25 AM
    Moderator
  • Hi Ozair,

    I am trying to do the same thing i.e. configuring test agent and test controller on Azure. When I try to install local endpoint on worker role VM(having test controller), system blocks the file download. I enabled file download in IE security setting but it still did not work. Is there anything else that one has to do to install local endpoint on the system where controller is running.

    -regards,

    Gaurav

    Tuesday, February 21, 2012 6:17 AM
  • What you can do is download "wacendpointpackage.exe" on your local machine by clicking "Install local endpoint" on azure portal. Then remotey access Worker role VM and paste the setup there(Windows 2008 allows sharing clipboard in remote session). This means you can copy any thing from your local machine to azure worker vm.

    After you have done that intall endpoint in command prompt like.

    wacendpointpackage.exe  /i /s /m en-us /token Your-Token-from-azure-portal

    I hope your probelm will be solved by doing this.

    Tuesday, February 21, 2012 10:35 AM
  • Yes Ozair, your solution worked perfectly fine. Thanks a lot.

    Another related query - I have my VSTS client on-premise connecting to test controller and test agents on Azure. It seems with this kind of deployment I have to use the Visual Studio Load Test Virtual Users Pack. Is there no other way to execute load test without the virtual users pack?

    I have a customer demo and I want to showcase the ease with which test agents running on Azure can be scaled up/down so I do not want to do local execution.

    Please share your thoughts on this.

    -regards,

    Gaurav

    Friday, February 24, 2012 2:35 AM
  • Visual Studio Load Test Virtual Users Pack are must when you do any Load Test Execution on Test Controller and Test agents(local or on Cloud). There is no other solution for this.


    Ozair Saleem

    Friday, February 24, 2012 9:42 AM