Skip to content

Conversation

@leelavg
Copy link
Contributor

@leelavg leelavg commented Oct 9, 2025

this also depends on locking all the dependencies to an exact version which will be changed in d/s.

manual cherrypick of #383

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 Oct 9, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 9, 2025

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

  • expected the bug to target the "odf-4.19.6" version, but no target version was set

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.

Details

In response to this:

this also depends on locking all the dependencies to an exact version which will be changed in d/s.

manual cherrypick of #383

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 Oct 9, 2025
@leelavg
Copy link
Contributor Author

leelavg commented Oct 9, 2025

/hold

need to update build team as well to lock the deps at exact version.

this also depends on locking all the dependencies to an exact version
which will be changed in d/s.

Signed-off-by: Leela Venkaiah G <[email protected]>
@rewantsoni
Copy link
Member

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Jan 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, rewantsoni

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@leelavg
Copy link
Contributor Author

leelavg commented Jan 7, 2026

/unhold

informed d/s build team.

@leelavg
Copy link
Contributor Author

leelavg commented Jan 7, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Jan 7, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 7, 2026

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

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.19.10) matches configured target version for branch (odf-4.19.10)
  • bug is in the state POST, 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 ([email protected]), skipping review request.

Details

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 2b1541e into red-hat-storage:release-4.19 Jan 7, 2026
10 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 7, 2026

@leelavg: [Jira Issue DFBUGS-4297](https://issues.redhat.com//browse/DFBUGS-4297): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-4297](https://issues.redhat.com//browse/DFBUGS-4297) has been moved to the MODIFIED state.

Details

In response to this:

this also depends on locking all the dependencies to an exact version which will be changed in d/s.

manual cherrypick of #383

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants