falco
falco copied to clipboard
falcosecurity
CI issue: data race in publishing jobs for `-dev` packages
Describe the bug
When multiple PRs got merged at the same time, then the CircleCI may run multiple workflows in parallel.
In such a situation, a data race occurs while publishing -dev packages to https://download.falco.org/?prefix=packages/
Since the publishing operation also updates RPM and DEB repository metadata, the process may result in corrupted repositories.
This problem happened with #1871 and #1872
However, once another PR gets merged, repository metadata is computed again and the problem disappears.
Only -dev packages are affected. Stable packages are not affected because we just tag a release at a time.
How to reproduce it
No way to reproduce it locally.
Expected behaviour
Additional context
I have opened this PR mostly for the record. Likely, we won't fix it. Final users are not affected by this problem in any way.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
@leogr: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/remove-lifecycle stale
/help
Just FYI @FedeDP @jasondellaluce
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
/remove-lifecycle rotten
This can still happen.
cc @FedeDP @Andreagit97 pls take this into account if you have in mind to renovate a bit our CI :smile_cat:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
/remove-lifecycle stale
I think the issue might be fixed when porting Ci to GHA and enforcing a correct concurrency in the master workflow.
