LG Auto-Provisioning query
We have built a POC (non-Production) environment in which to validate and demonstrate the auto provision of Load Generators in AWS.
We have successfully connected the install of LRE 2020 to our AWS account and created a template which specifies that we want to use the Microfocus AMI for provisioning Load Generators.
We then linked this template to our test.
So when we start our performance test, am I correct in saying that the test should link to the template, and based on the template it creates Load Generators to be used for the test?
But we get an error when it looks for a Controller and the test fails.
This video from MicroFocus shows how the configuration is done. At 01:52 when the test is run you can see a Controller already exists therefore the test can use that one.
So do we need to have at least 1 'Controller' machine built prior to attempting Load Generator auto-provision?
First off, thanks for giving the AWS auto-provisioning a try. You definitely need to have a controller in place before kicking off a test. Make sure that a controller is identified, and also that the necessary ports are opened for the LG and Controller communication.
Thank you @cyrusm
We built another machine in AWS to act as our controller. Then we repeated the steps I mentioned in my opening post. We do not see the same error.
However, we the request now fails with a different error.
ERROR HP.PC.PCS.HostOperations.SetHostImpl - failed ChangeMachineIdentity [Context: f6b8662c-8345-44d1-adf2-3771240df606] [FullContext: BackendUrl:http://localhost:5876 UserName:lreadmin Domain:DEFAULT Project:LAB_PROJECT]
System.Net.WebException: The remote name could not be resolved: 'LRE_SERVER'
The name is correct as when we log into the LRE2020 we use the following URL to successfully open the LRE2020 application http://LRE_SERVER.lre
We also see "Failed to communicate with the remote WCF service" in the logs. I saw a tip on another thread about this.
The issue occurs because LRE Host cannot communicate with LRE backend service over port 5876 (default port)
Staying on LRE Server and LRE Host, try to access http://LREServer:5876 and make sure you can access it, if not make the port 5876 is open from LRE Host to LRE Server.
We do have that port open however so we are unsure what to try next,