7.2. Troubleshooting Red Hat Ansible Lightspeed on-premise deployment errors


This section provides information about errors when configuring the Red Hat Ansible Lightspeed on-premise deployment and their workarounds.

7.2.1. Cannot log out of the Ansible Lightspeed portal

After you log out from the Ansible Lightspeed portal, you are redirected to the automation controller API page instead of Ansible Lightspeed.

This error indicates that the logout redirect URI was not configured while setting up your Red Hat Ansible Lightspeed on-premise deployment. You must configure the logout redirect URI by adding the LOGOUT_ALLOWED_HOSTS entry to the YAML file.

7.2.2. Cannot connect to the Ansible Lightspeed service from the Ansible VS Code extension

The following scenarios are possible:

  • The log-in attempt fails with the following error message:

    Enable lightspeed services from settings to use the feature.

    This error indicates that Ansible Lightspeed is not enabled in the Ansible VS Code extension. To resolve this error, perform the following tasks:

    1. Open the VS Code application.
    2. From the Activity bar, click the Extensions icon.
    3. From the Installed Extensions list, select Ansible.
    4. From the Ansible extension page, click the Settings icon ( Settings icon ) and select Extension Settings.
    5. Select Ansible Lightspeed settings and then select the Enable Ansible Lightspeed checkbox.
  • You are redirected to an incorrect Ansible Lightspeed instance on clicking the Connect button.

    This error indicates an incorrect route URL was used while configuring the Ansible Lightspeed service in Ansible VS Code extension. Ensure that you have configured the correct value in the route URL without any suffix. For more information, see Configuring Ansible VS Code extension for Red Hat Ansible Lightspeed on-premise deployment.

  • Cannot request code recommendations

    The following error message is displayed:

    An error occurred attempting to complete your request. Please try again later.

    This error indicates that the Ansible Lightspeed service is not running or is running with issues. Please check the Lightspeed service logs (the pod with suffix -api) for more details and error codes.

  • Cannot request code recommendations

    The following error message is displayed:

    The IBM watsonx Code Assistant is unavailable. Please try again later.

    or:

    IBM watsonx Code Assistant Model ID is invalid. Please contact your administrator.

    This error indicates that the model secret contains incorrect values. To resolve this error, ensure that you have not accidentally added any whitespace characters (extra line, space, and so on) to the username, model_url, and model_api_key parameters in the model connection secret. For more information, see Creating connection secrets.

7.2.3. Cannot connect to the Ansible Lightspeed service due to SSL connection error

If you are using self-signed certificates on the model server, you might encounter SSL certification verification errors, causing the connection between Ansible Lightspeed service and the model server to fail. The following error message is displayed:

Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED]
certificate verify failed: self signed certificate in certificate chain (_ssl.c:1006)'))

To resolve this error, use one of the following workarounds based on your Ansible Automation Platform version:

  • For Red Hat Ansible Automation Platform 2.5 and later:

Specify the optional key/value pair as model_verify_ssl=true in the model secret to connect to an IBM watsonx Code Assistant model. For details about the procedure, see Creating connection secrets.

  • For Red Hat Ansible Automation Platform 2.4:

You can disable the SSL protection between the model server and the Ansible Lightspeed service. For example, you can disable the SSL protection when you are on a testing environment. To disable the SSL protection, you must add the following extra setting in the Red Hat Ansible Lightspeed Custom Resource Definition (CRD) YAML file under the spec: section:

extra_settings:
    - setting: ANSIBLE_AI_MODEL_MESH_API_VERIFY_SSL
      value: false
重要

Reenabling the SSL protection You must re-enable the SSL protection when deploying on a production environment. To re-enable the SSL protection, simply remove the extra setting from the YAML file.

To reenable the SSL protection, perform the following tasks: . Go to the Red Hat OpenShift Container Platform. . Select Operators Installed Operators. . From the Projects list, select the namespace that you created when you installed the Red Hat Ansible Automation Platform operator. . Locate and select the Ansible Automation Platform operator. . Locate and select the Ansible Automation Platform custom resource, and then click the required app. . Select the YAML tab. The editor switches to a YAML editor view. . Scroll and find the spec: section, and add the following parameter under the spec: section:

extra_settings:
    - setting: ANSIBLE_AI_MODEL_MESH_API_VERIFY_SSL
      value: false
  1. Click Save.
  2. Restart the automation controller pods to apply the revised YAML:

    1. From the Red Hat OpenShift Container Platform, select Workloads Pods.
    2. Locate and select the Ansible Lightspeed pod that you updated.
    3. Click the Edit icon beside the pod and select Delete Pod.

      The select pod gets deleted and a new pod gets created.

Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Legal Notice

Theme

© 2026 Red Hat
トップに戻る