-
Notifications
You must be signed in to change notification settings - Fork 105
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
OCPBUGS-34577: UPSTREAM: <carry>: Clean up Multi-AZ Cluster matching rule #2019
base: master
Are you sure you want to change the base?
Conversation
@jsafrane: This pull request references Jira Issue OCPBUGS-34577, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
@jsafrane: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
/jira refresh |
@jsafrane: This pull request references Jira Issue OCPBUGS-34577, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), 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 openshift-eng/jira-lifecycle-plugin repository. |
/retest |
3 similar comments
/retest |
/retest |
/retest |
1589016
to
0ea7420
Compare
@jsafrane: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
Clean up "Multi-AZ Cluster Volumes should schedule pods in the same zones as statically provisioned PVs" from Disabled:Broken, because the test is already skipped in Disabled:Unsupported section.
0ea7420
to
ebb0fed
Compare
@jsafrane: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jsafrane The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jsafrane: 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-sigs/prow repository. I understand the commands that are listed here. |
Clean up "Multi-AZ Cluster Volumes should schedule pods in the same zones as statically provisioned PVs" from Disabled:Broken, because the test is already skipped in Disabled:Unsupported section.
This does not really fix the linked bug, it just cleans up related OCP rules. The test still needs to be skipped.
cc @openshift/storage