-
Notifications
You must be signed in to change notification settings - Fork 148
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
Add a global FreezeFS setting and a volume FreezeFS field #2744
Conversation
This pull request is now in conflict. Could you fix it @ejweber? 🙏 |
This pull request is now in conflict. Could you fix it @ejweber? 🙏 |
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.
Looks reasonable to me, although I would probably not catch omissions.
I ran out of time to retest this now that the dependencies are resolved and coming from the lower-level merged PRs, but I don't anticipate any change in functionality. It is ready for review (and I will retest the full stack before merge). |
Longhorn 2187 Signed-off-by: Eric Weber <eric.weber@suse.com>
b5e5b7f
to
f3c4451
Compare
I retested the full stack and everything is looking good. Please review when you can. |
Longhorn 2187 Signed-off-by: Eric Weber <eric.weber@suse.com>
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.
LGTM
Which issue(s) this PR fixes:
longhorn/longhorn#2187
What this PR does / why we need it:
freezeFS == true
orfreezeFS == false
in the proxy snapshot request to the engine.Depends on:
Need to resolve imports before merging.