-
Notifications
You must be signed in to change notification settings - Fork 36
Fix race condition in stacker's squashfuse mount path. #431
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
Fix race condition in stacker's squashfuse mount path. #431
Conversation
71d38db
to
c12d328
Compare
Codecov Report
@@ Coverage Diff @@
## main #431 +/- ##
==========================================
- Coverage 12.12% 12.08% -0.05%
==========================================
Files 44 44
Lines 5433 5451 +18
==========================================
Hits 659 659
- Misses 4657 4675 +18
Partials 117 117
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Why was test ' @github-actions ci / build / golang 1.20.x privilege unpriv (pull_request' skipped? |
part of the build (test) timed out https://github.com/project-stacker/stacker/actions/runs/4318221259/jobs/7554679260 |
1cbf125
to
2998625
Compare
squashfuse from Ubuntu 22.04 is linked to fuse2 and has some bugs compared to one that is linked against fuse3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025706 Signed-off-by: Scott Moser <smoser@brickies.net>
This protection was present in one of the callers of squashFuse, but not in another. The change here just to put them inside squashFuse. Fixes project-stacker#428. Signed-off-by: Scott Moser <smoser@brickies.net>
2998625
to
c546498
Compare
This is to work around a bug in stacker. project-stacker/stacker#431 Until that is fixed, we are getting errors during build where the 'run' section tries to use 'pkgtool' before that layer has been populated.
This is to work around a bug in stacker. project-stacker/stacker#431 Until that is fixed, we are getting errors during build where the 'run' section tries to use 'pkgtool' before that layer has been populated.
This protection was present in one of the callers of squashFuse, but not in another. The change here just to put them inside squashFuse.
Fixes #428.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.