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
expose option to force remove the OSD in osd removal template #1501
expose option to force remove the OSD in osd removal template #1501
Conversation
63d477e
to
a3fa73e
Compare
{ | ||
Name: "FORCE_OSD_REMOVAL", | ||
DisplayName: "FORCE_OSD_REMOVAL", | ||
Required: false, |
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.
I believe we also need to specify the default value as:
Value: "false",
Without that I assume the default is just empty, which will likely cause an error in Rook. But we need to test these template changes in an openshift cluster to confirm the default behavior.
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.
I believe we also need to specify the default value as:
Value: "false",
added
Without that I assume the default is just empty, which will likely cause an error in Rook. But we need to test these template changes in an openshift cluster to confirm the default behavior.
I ran oc process FAILED_OSD_IDS=0 ocs-osd-removal | oc create -f -
and in job pod the log I see
lag values: --force-osd-removal=false, --help=false, --log-level=DEBUG, --operator-image=, --osd-ids=0, --preserve-pvc=false, --service-account=
so it is adding false
by default to force-osd-removal
.
/cherry-pick release-4.10 |
@agarwal-mudit: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
adding option to expose `--force-osd-removal` `<true/false>`. It will help when Ceph indicates the OSD is not safe-to-destroy. Signed-off-by: subhamkrai <srai@redhat.com>
a3fa73e
to
9d1e544
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.
The changes look good. Can you comment on the testing you've been able to run? From an offline conversation I think it's good to go, but would be good to summarize it here.
So, when running the template without flag |
/lgtm |
/retest |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: agarwal-mudit, subhamkrai, travisn The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@subhamkrai: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@agarwal-mudit: new pull request created: #1518 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.9 |
@subhamkrai: new pull request created: #1778 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-4.8 |
@subhamkrai: #1501 failed to apply on top of branch "release-4.8":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'll create manual BP for 4.8, 4.7, 4.6 |
adding option to expose
--force-osd-removal
<true/false>
.It will help when Ceph indicates the OSD is not safe-to-destroy.
Signed-off-by: subhamkrai srai@redhat.com