Skip to content

DFBUGS-5818: [release-4.20] controllers: create cronjob with tolerations set on client-op sub#522

Open
openshift-cherrypick-robot wants to merge 1 commit intored-hat-storage:release-4.20from
openshift-cherrypick-robot:cherry-pick-519-to-release-4.20
Open

DFBUGS-5818: [release-4.20] controllers: create cronjob with tolerations set on client-op sub#522
openshift-cherrypick-robot wants to merge 1 commit intored-hat-storage:release-4.20from
openshift-cherrypick-robot:cherry-pick-519-to-release-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #519

/assign leelavg

when tolerations are set on the client-op subscription olm automatically
transfers that to deployment, thereby to the pod and we need to use
the same tolerations for cronjob as well.

Signed-off-by: Leela Venkaiah G <lgangava@ibm.com>
@openshift-ci
Copy link

openshift-ci bot commented Mar 2, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please ask for approval from leelavg. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 leelavg changed the title [release-4.20] controllers: create cronjob with tolerations set on client-op sub DFBUGS-5818 [release-4.20] controllers: create cronjob with tolerations set on client-op sub Mar 2, 2026
@leelavg leelavg changed the title DFBUGS-5818 [release-4.20] controllers: create cronjob with tolerations set on client-op sub DFBUGS-5818: [release-4.20] controllers: create cronjob with tolerations set on client-op sub Mar 2, 2026
@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 Mar 2, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 2, 2026

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

  • expected the bug to target the "odf-4.20.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 is an automated cherry-pick of #519

/assign leelavg

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.

@leelavg
Copy link
Contributor

leelavg commented Mar 4, 2026

/hold

@leelavg
Copy link
Contributor

leelavg commented Mar 5, 2026

need #526 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting 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 size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants