openshift
[release-4.15] OCPBUGS-37397: RWOP accessMode is not available on OpenShift console UI
This is an automated cherry-pick of #13829
/assign cyril-ui-developer
@openshift-cherrypick-robot: Jira Issue OCPBUGS-29777 has been cloned as Jira Issue OCPBUGS-37397. Will retitle bug to link to clone. /retitle [release-4.15] OCPBUGS-37397: RWOP accessMode is not available on OpenShift console UI
In response to this:
This is an automated cherry-pick of #13829
/assign cyril-ui-developer
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.
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-37397, which is invalid:
- expected dependent Jira Issue OCPBUGS-29777 to target a version in 4.16.0, 4.16.z, but it targets "4.17.0" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
This is an automated cherry-pick of #13829
/assign cyril-ui-developer
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.
@cyril-ui-developer: Can not set label backport-risk-assessed: Must be member in one of these teams: []
In response to this:
/label backport-risk-assessed
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@jhadvig: This pull request references Jira Issue OCPBUGS-37397, which is invalid:
- expected dependent Jira Issue OCPBUGS-29777 to target a version in 4.16.0, 4.16.z, but it targets "4.17.0" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@cyril-ui-developer: This pull request references Jira Issue OCPBUGS-37397, which is invalid:
- expected dependent Jira Issue OCPBUGS-29777 to target a version in 4.16.0, 4.16.z, but it targets "4.17.0" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@jhadvig: This pull request references Jira Issue OCPBUGS-37397, which is invalid:
- expected dependent Jira Issue OCPBUGS-29777 to target a version in 4.16.0, 4.16.z, but it targets "4.17.0" instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
/jira refresh
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.
@cyril-ui-developer: This pull request references Jira Issue OCPBUGS-37397, which is valid. The bug has been moved to the POST state.
7 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.15.z) matches configured target version for branch (4.15.z)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
- release note type set to "Release Note Not Required"
- dependent bug Jira Issue OCPBUGS-29777 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
- dependent Jira Issue OCPBUGS-29777 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
- bug has dependents
Requesting review from QA contact: /cc @yapei
In response to this:
/jira refresh
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.
@cyril-ui-developer: GitHub didn't allow me to assign the following users: yapei.
Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. For more information please see the contributor guide
In response to this:
/assign @jhadvig
QA Approver: /assign @yapei
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.