-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛 no longer fail when removing a volume from a node that does no longer exist #7036
🐛 no longer fail when removing a volume from a node that does no longer exist #7036
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7036 +/- ##
===========================================
- Coverage 87.08% 70.04% -17.05%
===========================================
Files 1597 665 -932
Lines 62455 32320 -30135
Branches 2050 262 -1788
===========================================
- Hits 54389 22637 -31752
- Misses 7729 9623 +1894
+ Partials 337 60 -277
Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this not be a warning??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Q: @GitHK So sometimes when I run manually director-v2 CLI to stop the hanging sidecars and it fails that the node ID is not in the DB anymore, this will fix it? |
@matusdrobuliak66 that is a different issue and unrelated to this one |
…ue-removing-volume
…K/osparc-simcore-forked into pr-osparc-fix-issue-removing-volume
…ue-removing-volume
…K/osparc-simcore-forked into pr-osparc-fix-issue-removing-volume
|
What do these changes do?
As part of the service shutdown proceed,
director-v2
will try to remove the used volumes of the service from the node via the agent. If the node is missing for whatever reason, the below error would be raised.This fix allows the director-v2 to no longer fail when the node with the required running agent instance is missing.
Related issue/s
How to test
Dev-ops checklist