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.

Sign up for GitHub

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

Jump to bottom

Artifact is wrongly reported in storage after a restart #936

Closed
stefanprodan opened this issue Oct 17, 2022 · 0 comments · Fixed by #974
Closed

Artifact is wrongly reported in storage after a restart #936

stefanprodan opened this issue Oct 17, 2022 · 0 comments · Fixed by #974
Assignees
@darkowlzz
Labels
bug Something isn't working
Milestone
Helm GA

Comments

@stefanprodan
Copy link
Member

stefanprodan commented Oct 17, 2022 •
edited
Loading

The status of all sources are reporting as ArtifactInStorage=True even if the storage is empty because the controller pod was deleted. This is due to the fact that we don't write to the status once we observe a drift, making the consumers (Kustomize and Helm controller) miss behave. Ref: #935
@stefanprodan stefanprodan added the bug Something isn't working label Oct 17, 2022
@stefanprodan stefanprodan added this to the GA milestone Oct 17, 2022
@darkowlzz darkowlzz mentioned this issue Dec 5, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@darkowlzz darkowlzz

Labels
bug Something isn't working
Projects
Maintainers' Focus
Status: Done
Milestone
Helm GA
Development

Successfully merging a pull request may close this issue.

Introduce Progressive status fluxcd/source-controller
2 participants
@darkowlzz @stefanprodan