Skip to content

Conversation

umangachapagain
Copy link
Contributor

@umangachapagain umangachapagain commented Apr 1, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. label Apr 1, 2025
Copy link
Contributor

openshift-ci bot commented Apr 1, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umangachapagain

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-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Apr 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 1, 2025

@umangachapagain: This pull request references [Jira Issue DFBUGS-2036](https://issues.redhat.com//browse/DFBUGS-2036), which is invalid:

  • expected the bug to target either version "odf-4.18.2." or "openshift-odf-4.18.2.", but it targets "odf-4.18.3" 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:

Depends on #301 and #303

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 openshift-ci bot added the approved label Apr 1, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 9, 2025

@umangachapagain: This pull request references [Jira Issue DFBUGS-2036](https://issues.redhat.com//browse/DFBUGS-2036), which is invalid:

  • expected the bug to target either version "odf-4.18.2." or "openshift-odf-4.18.2.", but it targets "odf-4.18.3" 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:

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.

@umangachapagain umangachapagain force-pushed the release-4.18-fix-storageid-exchange branch from 2e61ca5 to eab0821 Compare April 9, 2025 06:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid jira ticket of any type
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants