Skip to content

Conversation

@siegfriedweber
Copy link
Member

Description

Fix the error "failed to write content: File exists (os error 17)" after a Node restart.

Fixes #262

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes
# Author
- [x] Changes are OpenShift compatible
- [x] Helm chart can be installed and deployed operator works
- [x] Integration tests passed (for non trivial changes)
- [x] Changes need to be "offline" compatible
# Reviewer
- [ ] Code contains useful comments
- [ ] Code contains useful logging statements
- [ ] (Integration-)Test cases added
- [ ] Documentation added or updated. Follows the [style guide](https://docs.stackable.tech/home/nightly/contributor/docs/style-guide).
- [ ] Changelog updated
- [ ] Cargo.toml only contains references to git tags (not specific commits or branches)
# Acceptance
- [ ] Feature Tracker has been updated
- [ ] Proper release label has been added
- [ ] [Roadmap](https://github.com/orgs/stackabletech/projects/25/views/1) has been updated

@siegfriedweber siegfriedweber requested a review from nightkr March 7, 2025 13:15
@siegfriedweber siegfriedweber self-assigned this Mar 7, 2025
@siegfriedweber siegfriedweber moved this to Development: Waiting for Review in Stackable Engineering Mar 7, 2025
@siegfriedweber siegfriedweber force-pushed the fix/node-restart-error branch from 0191d93 to 2747cde Compare March 7, 2025 13:16
@siegfriedweber siegfriedweber requested a review from nightkr March 7, 2025 17:11
@siegfriedweber siegfriedweber moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Mar 7, 2025
@nightkr nightkr changed the title fix: Fix an error after a Node restart fix: Fix republishing volumesafter a Node restart Mar 10, 2025
@nightkr nightkr changed the title fix: Fix republishing volumesafter a Node restart fix: Fix republishing volumes after a Node restart Mar 10, 2025
@siegfriedweber siegfriedweber added this pull request to the merge queue Mar 10, 2025
@siegfriedweber siegfriedweber moved this from Development: In Review to Development: Done in Stackable Engineering Mar 10, 2025
Merged via the queue into main with commit 922273d Mar 10, 2025
16 of 17 checks passed
@siegfriedweber siegfriedweber deleted the fix/node-restart-error branch March 10, 2025 09:40
@lfrancke
Copy link
Member

lfrancke commented Mar 20, 2025

Can you please add a release note snippet in the form "Previously, 'this went wrong'. With this release, 'this was fixed in the following way'."

@lfrancke lfrancke moved this from Development: Done to Acceptance: In Progress in Stackable Engineering Mar 20, 2025
@siegfriedweber
Copy link
Member Author

Can you please add a release note snippet in the form "Previously, 'this went wrong'. With this release, 'this was fixed in the following way'."

Already done in #262, see https://docs.stackable.tech/home/stable/release-notes/#_bug_fixes.

@lfrancke lfrancke moved this from Acceptance: In Progress to Done in Stackable Engineering Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Pods with listener volumes can not be restarted after their node is restarted

4 participants