Troubleshooting

You have to configure your provider to get the token. See Configure dynamic infrastructure providers.

Possible errors during connection phase:

• Failed to start infrastructure: Authentication failed.
  The API Token used in Infrastructure Provider settings is wrong. For more information, see this section.

• Failed to start infrastructure: Host not found.
  The API URL used in Infrastructure Provider settings is wrong. For more information, see this section.

• Too many attempts have been done, please try again.

NeoLoad communicates with the Provider but is not able to start Controller and Load Generators properly. You have to investigate on the Provider side. (ex: Kubernetes debug).
Possible errors while connected to the cluster:

• Image cannot be pulled by the cluster.

• Cluster is not able to place NeoLoad pods because of quotas or limit issues.

• Pods are taking too much time to start.

• Pods are running but are not able to connect to NeoLoad Web.

• Not enough resources available with the same version.
  Make sure your Controller and load generators image share the same version. If this error persists, you will need to ensure your project has been designed with the same version as your Controller and load generators as well. If needed, you can upgrade your project to a newer version by opening it in your latest NeoLoad client.

You cannot use pods with less than 1Go memory or less than 1CPU. Neotys applies a minimum of viability for the Controller to 2000MB, 1.5CPU and for the Load Generators to 1500MB, 1CPU.

You can use Kubernetes / OpenShift quotas on the namespace / project used by NeoLoad Web.

You can refer to the “How to configure it?” section. When you configure and set the Provider, use the Kubernetes value.