Self Service Summary
If you face this message, either in the output of the command
kubectl exec deploy/dynatrace-operator -n dynatrace -- dynatrace-operator troubleshoot
or while describing the ActiveGate statefulset / OneAgent daemonset
Pulling ActiveGate (custom image) image <repository>/linux/activegate:latest failed: reading manifest latest in <repository>/linux/activegate: unknown: Unable to find latest installer for active gate - is there a build unit for S3Type docker_activegate_image_ubuntu?
Pulling OneAgent image <repository>/linux/oneagent:latest failed: reading manifest latest in <repository>/linux/oneagent: tag invalid: No bootstrapping-image found for version: 1.259.369.20230308-123910
| Issue |
Solution |
Tasks |
Alternative(s) |
| ActiveGate/Oneagent pod won't pull the image / is not starting anymore. |
Check in the Cluster management console the installer packages for ActiveGate. |
Make sure to have the correct version available (not excluded). The ActiveAGate/OneAgent version has to be -1 from the Managed cluster version. |
Raise a support ticket. |
This situation can occur if you're trying to do a managed cluster update, for example from 1.260 to 1.262 and it fails. During the upgrade process, you manually exclude ActiveGate/OneAgent installer with version 1.259.
So if the upgrade will fail, and you're still running as in the example managed cluster 1.260 and ActiveGate installer 1.259 has been excluded, you will see following message:
Pulling ActiveGate (custom image) image <repository>/linux/activegate:latest failed: reading manifest latest in <repository>/linux/activegate: unknown: Unable to find latest installer for active gate - is there a build unit for S3Type docker_activegate_image_ubuntu?
Pulling OneAgent image <repository>/linux/oneagent:latest failed: reading manifest latest in <repository>/linux/oneagent: tag invalid: No bootstrapping-image found for version: 1.259.369.20230308-123910
The solution for this is to go to Cluster Management console and make the ActiveGate/OneAgent installer available once again and then check the status of the ActiveGate/OneAgent pod.
If the issue persists though, please raise a support ticket and we'll assist you.
