Troubleshooting

Overview

This page will document frquently encountered issues by tenant’s and should be the first place you visit when you are seeing unexpected behavior. This page will be updated frequently so check back often.

If you cannot find a solution to your issue below, please open a Standard FCS Support Request.

1. Jenkins says I’m "missing the Overall/Read permission"
2. Jenkins reports “TooManyRequests: You have reached your pull rate limit”
3. My Jenkins build failed
4. My Jenkins image built but failed to deploy
5. I don’t see my application logs in Datadog

Jenkins says I’m "missing the Overall/Read permission"

This error means that you haven’t been added to the correct group that corresponds to your team in the FCS IDM. To rectify this issue, you must follow the steps under Account Creation on the Jenkins Access page.

Jenkins reports “TooManyRequests: You have reached your pull rate limit”

This is happening because the base image is likely being pulled from Docker Hub. MCaaS does not have a subscription to Docker Hub. To resolve this issue, you can push your Docker base image to our ECR and reference it in the Dockerfile to avoid pulling it from Docker Hub.

:warning: Announcement
May 2023 - MCaaS is aware of an increase of build failures with this error as the root issue. MCaaS is currently working on implementing a pull-through-cache which will reduce the calls to docker hub and thus reduce the likelihood of encountering these rate limit errors. Until this is implemented, please retry your builds later, or implement a base image hosted in ECR as outlined above.

My Jenkins build failed

Navigate to the specific build that failed in Jenkins. Check the Console Output for any errors. If it seems to be an application error, build the application locally using Docker and try to resolve there.

Possible errors:

1. The repository with name "" does not exist
   • This means that a corresponding repository for your application has not been created in ECR. Request ECR
2. Could not find artifact "" in local-maven-repo
   • Check the source of your Maven dependencies to verify that the correct version of the jar exists.

My Jenkins image built but failed to deploy

This suggests an issue with the Flux process.

1. Check our FAQ answer to Why didn’t Flux pick up my new image?
2. Check the Flux Datadog logs
   • Filter the Kubernetes Namespace option by tenant-flux-ns

I don’t see my application logs in Datadog

Datadog needs to be configured in your application’s HelmRelease to capture application logging. See our Datadog Setup page for more details.

Warning

Datadog configuration differs between application runtimes. Please pay attention to the instrumentation documentation when configuring for your application.