Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ImageUpdateAutomation not providing helpful error message #548

Open
RogerSik opened this issue Jun 28, 2023 · 3 comments
Open

ImageUpdateAutomation not providing helpful error message #548

RogerSik opened this issue Jun 28, 2023 · 3 comments

Comments

@RogerSik
Copy link

Using version v2.0.0-rc.5 and trying to use the Flux auto update but it's not working there are no helpful error messages.

$ kubectl  describe ImageUpdateAutomation
Events:
  Type     Reason  Age                    From                         Message
  ----     ------  ----                   ----                         -------
  Warning  error   9m23s (x18 over 125m)  image-automation-controller  unknown error: remote:
$

Looking into image-automation-controller for more information

$ kubectl logs -f deployment/image-automation-controller
{"level":"error","ts":"2023-06-28T08:32:17.954Z","msg":"Reconciler error","controller":"imageupdateautomation","controllerGroup":"image.toolkit.fluxcd.io","controllerKind":"ImageUpdateAutomation","ImageUpdateAutomation":{"name":"app","namespace":"xxx"},"namespace":"xxx","name":"app","reconcileID":"b3cc389f-70fb-4720-8c08-da948193e4a4","error":"unknown error: remote: "}
$

flux itself is working fine (applying yaml files and succesfully writing commits when updating flux).

@RogerSik
Copy link
Author

There was an MR for better error messages #115 which was also merged.

@aryan9600
Copy link
Member

this error is usually observed when you're using a GitLab deploy key with no write access, see: #491. could you confirm that is the case here as well?

@RogerSik
Copy link
Author

Has written access. The flux update where the files get written / updated and send a commit was also working. Even if this would be the case: a more helpful error message would be helpful. 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants