Inspect the install-dynamic-plugins init container logs to confirm that plug-ins installed from your configured delivery method.
- In a browser, log in to your OpenShift instance.
- In the Developer perspective, open the Topology view for the namespace where you deployed the chart.
- Select the deployment named
<release-name>-rhaap-portal.
- Open the deployment pod logs.
- In the pod details page, select the Logs tab.
- From Init containers, select
install-dynamic-plugins.
Expected log output for OCI delivery (recommended)
When pluginMode is oci, successful installation resembles the following output:
======= Installing dynamic plugin oci://registry.redhat.io/ansible-automation-platform/automation-portal:<plugin-version>!ansible-backstage-plugin-catalog-backend-module-rhaap
...
-> Successfully installed dynamic plugin oci://registry.redhat.io/ansible-automation-platform/automation-portal:<plugin-version>!ansible-backstage-plugin-catalog-backend-module-rhaap
Replace <plugin-version> with the value from your imageTagInfo setting. If you use a mirror registry, the registry host in the log reflects your imageRegistry or ociPluginImage configuration.
Expected log output for HTTP plug-in registry (deprecated)
When pluginMode is tarball, successful installation resembles the following output:
======= Installing dynamic plugin http://plugin-registry:8080/ansible-backstage-plugin-catalog-backend-module-rhaap-dynamic-x.y.z.tgz
...
-> Successfully installed dynamic plugin http://plugin-registry:8080/ansible-backstage-plugin-catalog-backend-module-rhaap-dynamic-x.y.z.tgz
The tarball file name includes the plug-in version from your bundle.
- On the Environment tab, verify that environment variables from your Helm chart appear as expected.