Bug 2101343: UPSTREAM: 2101343: fix: changed the csistoragecapacity check namespace #52
Conversation
The CSIStorageCapacity v1 check was attampting to create an invalid object in the default namespace. This would fail if the pod did not have permissions to the namespace. This will now use the namespace specified in the NAMESPACE env variable. Signed-off-by: N Balachandran <nibalach@redhat.com>
openshift-ci
bot
added
the
approved
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jsafrane, tsmetana 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 |
|
/retest |
jsafrane
changed the title
openshift-ci
bot
added
bugzilla/severity-high
|
@jsafrane: This pull request references Bugzilla bug 2101343, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (wduan@redhat.com), skipping review request. 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. |
|
/retest |
1 similar comment
|
/retest |
|
it seems we won't get 1.24 kubelet soon and I want to fix it in 4.11 ASAP |
|
/override ci/prow/e2e-aws-csi |
|
@jsafrane: Overrode contexts on behalf of jsafrane: ci/prow/e2e-aws-csi, ci/prow/e2e-gcp-csi 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.11 |
|
@jsafrane: once the present PR merges, I will cherry-pick it on top of release-4.11 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. |
|
@jsafrane: Overrode contexts on behalf of jsafrane: ci/prow/e2e-aws-csi 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. |
|
@jsafrane: all tests passed! 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. |
|
@jsafrane: All pull requests linked via external trackers have merged: Bugzilla bug 2101343 has been moved to the MODIFIED state. 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. |
|
@jsafrane: new pull request created: #53 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 of kubernetes-csi#753 to 4.12.
The CSIStorageCapacity v1 check was attampting to create an invalid
object in the default namespace. This would fail if the pod did not
have permissions to the namespace. This will now use the namespace
specified in the NAMESPACE env variable.
cc @openshift/storage