-
Notifications
You must be signed in to change notification settings - Fork 34
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
Allow expansion of volumes with snapshots, or restored volumes #816
Conversation
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
0220e89
to
e0176f5
Compare
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.
Something like this:
'Allow expansion for volumes with snapshots, or restored volumes'
…tored volumes Till now we had a limitation that IO used to fail on an expanded volume if it had a snapshot before expansion. The issue is fixed in data-plane and hence this limitation is now being removed. Signed-off-by: Diwakar Sharma <diwakar.sharma@datacore.com>
Signed-off-by: Diwakar Sharma <diwakar.sharma@datacore.com>
e0176f5
to
67813b2
Compare
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
You forgot to change the PR title as well |
Done now (y). Had changed commit title though. |
Build succeeded: |
You had to cancel bors... got merged with wrong title... |
Ah, bummer. Not a big deal I guess? the PR title just gets embedded in the description of merge commit. And it's not wrong per se, just needed rewording. |
Yeah no biggie |
No description provided.