Skip to content

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #2385

/assign malayparida2000

In 4.16 when we implemented this change we had assumed the base
to be 6 OSDs, but since than we have added a lot more pods to the
ODF deployment.
The ODF docs also mention the resource requirement to be based on 3 OSDs

Signed-off-by: Malay Kumar Parida <[email protected]>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

[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 assign gowthamshanmugam for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@malayparida2000
Copy link
Contributor

malayparida2000 commented Nov 21, 2025

/retitle DFBUGS-4713: [release-4.20] Change the resource requirement base calculation from 6 to 3 OSDs

@openshift-ci openshift-ci bot changed the title [release-4.20] Change the resource requirement base calculation from 6 to 3 OSDs DFBUGS-4713: [release-4.20] Change the resource requirement base calculation from 6 to 3 OSDs Nov 21, 2025
@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 Nov 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 21, 2025

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

  • expected the bug to target the "odf-4.20" 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.

In response to this:

This is an automated cherry-pick of #2385

/assign malayparida2000

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

@malayparida2000 we need a PR for release-4.y-compatibility branch as well.

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

Labels

jira/invalid-bug Indicates that the referenced jira bug is invalid 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.

4 participants