Skip to content

[release-4.17] OCPBUGS-56901: Fix dynamic-system-reserved-calc.sh when only true parameter is used #5096

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 10, 2025
Merged

[release-4.17] OCPBUGS-56901: Fix dynamic-system-reserved-calc.sh when only true parameter is used #5096

merged 1 commit into from
Jun 10, 2025

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #4733

/assign BhargaviGudi

@oarribas
Fix dynamic_node_sizing when only true parameter is used
35fd49b 
When using the command with only `true` parameter, the call to function `dynamic_node_sizing` only has 1 parameter, and `dynamic_cpu_sizing $2` has no parameter.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request May 30, 2025
Merged
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-45621 has been cloned as Jira Issue OCPBUGS-56901. Will retitle bug to link to clone.
/retitle [release-4.17] OCPBUGS-56901: Fix dynamic-system-reserved-calc.sh when only true parameter is used

In response to this:

This is an automated cherry-pick of #4733

/assign BhargaviGudi

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 changed the title [release-4.17] OCPBUGS-45621: Fix dynamic-system-reserved-calc.sh when only true parameter is used [release-4.17] OCPBUGS-56901: Fix dynamic-system-reserved-calc.sh when only true parameter is used May 30, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate 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 a referenced Jira bug is invalid for the branch this PR is targeting. labels May 30, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-56901, which is invalid:

  • expected dependent Jira Issue OCPBUGS-45621 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead
  • expected dependent Jira Issue OCPBUGS-45621 to target a version in 4.18.0, 4.18.z, but it targets "4.19" 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.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #4733

/assign BhargaviGudi

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 requested review from djoshy and yuqi-zhang May 30, 2025 11:03
sairameshv
sairameshv approved these changes May 30, 2025
View reviewed changes
Copy link
Member

@sairameshv sairameshv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 30, 2025
@BhargaviGudi
Copy link

/retest-required

@BhargaviGudi
Copy link

/retest

@BhargaviGudi
Copy link

/cherry-pick-approved

@sergiordlr
Copy link
Contributor

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 4, 2025
@sairameshv
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sairameshv: This pull request references Jira Issue OCPBUGS-56901, which is invalid:

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:

/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.

@sairameshv
Copy link
Member

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@sairameshv: This pull request references Jira Issue OCPBUGS-56901, which is invalid:

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:

/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.

@sairameshv
Copy link
Member

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 5, 2025
@openshift-ci-robot
Copy link
Contributor

@sairameshv: This pull request references Jira Issue OCPBUGS-56901, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-45621 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-45621 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @lyman9966

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-ci openshift-ci bot requested a review from lyman9966 June 5, 2025 13:51
@sairameshv
Copy link
Member

@yuqi-zhang , Could you add the required labels for this change?

yuqi-zhang
yuqi-zhang approved these changes Jun 6, 2025
View reviewed changes
Copy link
Contributor

@yuqi-zhang yuqi-zhang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 6, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, sairameshv, yuqi-zhang

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 6, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f54ce41 and 2 for PR HEAD 35fd49b in total

3 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f54ce41 and 2 for PR HEAD 35fd49b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f54ce41 and 2 for PR HEAD 35fd49b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD f54ce41 and 2 for PR HEAD 35fd49b in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ca15369 and 1 for PR HEAD 35fd49b in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 9, 2025 •
edited
Loading

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-vsphere-ovn-upi-zones 35fd49b link false /test e2e-vsphere-ovn-upi-zones
ci/prow/e2e-gcp-op-techpreview 35fd49b link false /test e2e-gcp-op-techpreview
ci/prow/e2e-azure-ovn-upgrade-out-of-change 35fd49b link false /test e2e-azure-ovn-upgrade-out-of-change

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

@oarribas
Copy link
Contributor

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD ca15369 and 2 for PR HEAD 35fd49b in total

@openshift-merge-bot openshift-merge-bot bot merged commit 3027d07 into openshift:release-4.17 Jun 10, 2025
14 of 17 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56901: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-56901 has been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #4733

/assign BhargaviGudi

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.17.0-202506102034.p0.g3027d07.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.17.0-0.nightly-2025-06-11-184010

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

@sairameshv sairameshv sairameshv approved these changes

@yuqi-zhang yuqi-zhang yuqi-zhang approved these changes

@djoshy djoshy Awaiting requested review from djoshy

@lyman9966 lyman9966 Awaiting requested review from lyman9966

Assignees

@rbbratta rbbratta

@eurijon eurijon

@sairameshv sairameshv

@anuragthehatter anuragthehatter

@sergiordlr sergiordlr

@rlobillo rlobillo

@rioliu-rh rioliu-rh

@mhanss mhanss

@BhargaviGudi BhargaviGudi

@ptalgulk01 ptalgulk01

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a 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 Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.