-
Notifications
You must be signed in to change notification settings - Fork 200
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(version): fix castemplate output runstask version suffix #1735
Merged
AmitKumarDas
merged 1 commit into
openebs-archive:master
from
shubham14bajpai:fix-version
Jul 21, 2020
Merged
fix(version): fix castemplate output runstask version suffix #1735
AmitKumarDas
merged 1 commit into
openebs-archive:master
from
shubham14bajpai:fix-version
Jul 21, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: shubham <shubham.bajpai@mayadata.io>
7 tasks
AmitKumarDas
approved these changes
Jul 21, 2020
mittachaitu
pushed a commit
to mittachaitu/maya
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](openebs-archive#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
7 tasks
kmova
pushed a commit
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
mittachaitu
pushed a commit
to mittachaitu/maya
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](openebs-archive#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
mittachaitu
pushed a commit
to mittachaitu/maya
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](openebs-archive#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
kmova
pushed a commit
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
kmova
pushed a commit
that referenced
this pull request
Aug 11, 2020
This PR fixes CStor volume provisioning issue. Currently REST request to create CStor volume will fail if request is made without creating PVC because of following bug: - When the REST API is called to create volume it will verify whether request payload has PVC name. If PVC name doesn't exist then it will skip execution of `cstor-volume-create-puttargetservice-default` runtask but with latest changes of PR [1735](#1735) above runtask is not skiped and leads to failure in creation of CStor volume. Signed-off-by: mittachaitu <sai.chaithanya@mayadata.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: shubham shubham.bajpai@mayadata.io
What this PR does?:
PR fixes the issue with output runtask version suffix ( RC1 --> rc1) . (Changes got missed to commit earlier due to some local rebase errors and got stashed locally)
more info #1733
Does this PR require any upgrade changes?:
If the changes in this PR are manually verified, list down the scenarios covered::
After building images with a custom tag 1.11.0-ee-rc2
Steps Performed
Any additional information for your reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>