[release-4.19] OCPBUGS-56193: UPSTREAM: 131236: RWX tests should create RWX volumes #2301
Conversation
The test that checks that a volume can be accessed from multiple nodes should create ReadWriteMany volume and not ReadWriteOnce.
openshift-ci-robot
added
the
backports/validated-commits
|
@openshift-cherrypick-robot: the contents of this pull request could be automatically validated. The following commits are valid:
Comment |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-54318 has been cloned as Jira Issue OCPBUGS-56193. Will retitle bug to link to clone. 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. |
openshift-ci
bot
changed the title
|
@openshift-cherrypick-robot: An error was encountered searching for bug OCPBUGS-56193 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
No response returned: Get "https://issues.redhat.com/rest/api/2/issue/OCPBUGS-56193": GET https://issues.redhat.com/rest/api/2/issue/OCPBUGS-56193 giving up after 5 attempt(s)
Please contact an administrator to resolve this issue, then request a bug refresh with 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 |
|
@openshift-cherrypick-robot: 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-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
/jira refresh |
openshift-ci-robot
added
jira/severity-moderate
|
@jsafrane: This pull request references Jira Issue OCPBUGS-56193, 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. |
|
/jira refresh |
|
@jsafrane: This pull request references Jira Issue OCPBUGS-56193, which is invalid:
Comment 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. |
|
/jira refresh |
|
@jsafrane: An error was encountered updating to the POST state for bug OCPBUGS-56193 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details. Full error message.
No response returned: Get "https://issues.redhat.com/rest/api/2/issue/16977076/transitions?expand=transitions.fields": GET https://issues.redhat.com/rest/api/2/issue/16977076/transitions?expand=transitions.fields giving up after 5 attempt(s)
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@jsafrane: This pull request references Jira Issue OCPBUGS-56193, which is valid. The bug has been moved to the POST state. 7 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. |
openshift-ci
bot
added
the
backport-risk-assessed
openshift-ci
bot
assigned gangwgr, kasturinarra, wangke19, xingxingxia, zhouying7780 and bertinatto
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto, jsafrane, openshift-cherrypick-robot 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 |
openshift-ci
bot
added
the
approved
|
/label cherry-pick-approved |
openshift-ci
bot
added
the
cherry-pick-approved
|
/label cherry-pick-approved |
openshift-merge-bot
bot
merged commit 9fe7dfd
into
openshift:release-4.19
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-56193: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-56193 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-pod |
|
[ART PR BUILD NOTIFIER] Distgit: kube-proxy |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-hyperkube |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-kube-apiserver-artifacts |
|
Fix included in accepted release 4.19.0-0.nightly-2025-05-15-183918 |
This is an automated cherry-pick of #2279
/assign jsafrane