Red Hat SummitChapter 4. Ansible plug-ins subscription warning messages
The Ansible plug-ins display a subscription warning banner in the user interface in the following scenarios:
4.1. Unable to connect to Ansible Automation Platform
The following warning indicates that the automation controller details are not configured, or the controller instance API is unreachable to query the subscription status.
Unable to connect to Ansible Automation Platform Verify that Ansible Automation Platform is reachable and correctly configured in the Ansible plug-ins. To get help, please refer to the Ansible plug-ins installation guide.
Remediation steps
-
Verify that Ansible Automation Platform is reachable and correctly configured in the
rhaapsection of the ConfigMap. -
Ensure the
checkSSLkey is correctly set for your environment. - After correcting the configuration details, restart the Red Hat Developer Hub pod to initiate a subscription query.
4.2. Unable to authenticate to Ansible Automation Platform
The following warning indicates that the Ansible plug-ins were not able to authenticate with Ansible Automation Platform to query the subscription status.
Unable to authenticate to Ansible Automation Platform Verify that the authentication details for Ansible Automation Platform are correctly configured in the Ansible plug-ins. For help, please refer to the Ansible plug-ins installation guide.
Remediation steps
- Verify that the automation controller Personal Access Token (PAT) configured in the Ansible plug-ins is correct. For more information, refer to the Adding tokens section of TitleCentralAuth.
- After correcting the authentication details, restart the Red Hat Developer Hub pod to initiate a subscription query.
4.3. Invalid Ansible Automation Platform configuration
The following warning indicates that the Ansible Automation Platform configuration section is invalid or incomplete.
Invalid resource for Ansible Automation Platform Verify that the resource url for Ansible Automation Platform are correctly configured in the Ansible plug-ins. For help, please refer to the Ansible plug-ins installation guide.
Remediation steps
-
Verify that the
rhaapsection of the Ansible plug-ins ConfigMap is correctly configured and contains all the necessary entries. For more information, refer to Configuring Ansible Automation Platform details. - After correcting the configuration, restart the Red Hat Developer Hub pod to initiate a subscription query.
4.4. Ansible Automation Platform subscription is out of compliance
The following warning indicates that the Ansible plug-ins successfully retrieved the Ansible Automation Platform subscription status. However, the subscription is out of compliance.
Subscription non-compliant The connected Ansible Automation Platform subscription is out of compliance. Contact your Red Hat account team to obtain a new subscription entitlement. Learn more about account compliance.
Remediation steps
- Contact your Red Hat account team to obtain a new subscription entitlement.
- Learn more about account compliance.
- When the subscription is in compliance, restart the Red Hat Developer Hub pod to initiate a new subscription query.
4.5. Invalid Ansible Automation Platform subscription
The following warning indicates that the Ansible plug-ins successfully retrieved the Ansible Automation Platform subscription status. However, the subscription type is invalid for Ansible Automation Platform.
Invalid subscription The connected Ansible Automation Platform subscription is invalid. Contact your Red Hat account team, or start an Ansible Automation Platform trial.
Remediation steps
- Contact your Red Hat account team to obtain a new subscription entitlement or start an Ansible Automation Platform trial.
- When you have updated the subscription, restart the Red Hat Developer Hub pod to initiate a new subscription query.
