Skip to content
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

DFBUGS-957: [release-4.18-compatibility] Fix pool name check for blockpools #1834

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1830

/assign SanjalKatiyar

Signed-off-by: vbadrina <vbadrina@redhat.com>
@vbnrh
Copy link
Member

vbnrh commented Jan 23, 2025

/retitle DFBUGS-957: [release-4.18-compatibility] Fix pool name check for blockpools

@openshift-ci openshift-ci bot changed the title [release-4.18-compatibility] Fix pool name check for blockpools DFBUGS-957: [release-4.18-compatibility] Fix pool name check for blockpools Jan 23, 2025
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Jan 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 23, 2025

@openshift-cherrypick-robot: This pull request references [Jira Issue DFBUGS-957](https://issues.redhat.com//browse/DFBUGS-957), which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.18) matches configured target version for branch (odf-4.18)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (ikave@redhat.com), skipping review request.

In response to this:

This is an automated cherry-pick of #1830

/assign SanjalKatiyar

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.

@SanjalKatiyar
Copy link
Collaborator

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jan 23, 2025
Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, SanjalKatiyar

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 237d689 into red-hat-storage:release-4.18-compatibility Jan 23, 2025
7 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 23, 2025

@openshift-cherrypick-robot: An error was encountered updating to the MODIFIED state for bug DFBUGS-957 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. Error marking step #34606878 finished: root cause: Tried to update an entity that does not exist.: request failed. Please analyze the request body for more details. Status code: 400:

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #1830

/assign SanjalKatiyar

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type lgtm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants