RabbitMQ: RabbitMQ on Kubernetes, Helm Fails to Fetch Images
Article ID: 381251
Updated On:
Products
Issue/Introduction
Typically the issue happens when user follows below documents: Install VMware Tanzu RabbitMQ for Kubernetes using Helm and helm would fail to fetch the image.
The sample error message which is generated when helm tries to wrap a local image + chart bundle. This process would fetch the images from the registry defined in the Chart.yaml:
Environment
RabbitMQ on Kubernetes 4.0.2
Cause
It is due to mis-configuration of path to the rmq-audit-logger image.
Resolution
Before applying the Resolution, please go through the Troubleshooting to identify if users are impacted by this issue described in this article.
Troubleshooting:
1. Please make sure you have helm registry login to all of the required Broadcom Registry successfully.
Not only the the helm registry, also the general broadcom registry that mentioned in the error message you see.
Please note that in the container world, wrong environment value settings(such as EXPORT valuename=value in Linux environment, set valuename=value in Windows) would return similar error messages MANIFEST UNKNOWN as well. Therefore, please always try to make sure the things are correct before trying anything else.
2. Then open the Chart.yaml file and identify if the path to the rmq-audit-logger is incorrect.
Correct one is: rabbitmq.packages.broadcom.com/audit-logger:0.4.3-amd64
Resolution:
Option 1: If users are sure that the Audit Logger is not being used in the cluster (Note: it is not being used by default.), you can remove the references to it from Chart.yaml file, and try again. In the file, the references would look like below, delete these 2 lines would do.
Option 2: Modify the path to correct one.
Long Term Fix:
Feedback
