Skip to content

Conversation

@elmiko
Copy link

@elmiko elmiko commented Mar 19, 2025

while doing some fixing for OCPBUGS-11115, i noticed a condition whereby HCP would not properly detect failed machines. this change makes the logic more aware to differences between MAPI and CAPI.

@elmiko
Copy link
Author

elmiko commented Mar 19, 2025

/hold

this needs to wait for #347

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 19, 2025
@openshift-ci openshift-ci bot requested review from JoelSpeed and frobware March 19, 2025 22:49
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 28, 2025
This change allows the failed machine logic to be aware of the API
differences between MAPI and CAPI status fields related to failures and
errors. This change is being added to ensure that the autoscaler will
properly detect failed machines regardless of whether it is running on
OCP or HCP.
@elmiko elmiko force-pushed the fixups-for-failed-machine-hcp branch from c3ba40e to ec6d1fd Compare June 18, 2025 19:27
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 18, 2025
@elmiko
Copy link
Author

elmiko commented Jun 18, 2025

i've rebased this, but i wonder if we shouldn't wait for the rebase on upstream so that we can drop one of the commits.

edit: nvm about waiting, we already brought in the upstream patch.

@openshift-ci
Copy link

openshift-ci bot commented Jun 18, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign enxebre 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

@openshift-ci
Copy link

openshift-ci bot commented Jun 18, 2025

@elmiko: 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-azure-periodic-pre c3ba40e link false /test e2e-azure-periodic-pre
ci/prow/okd-scos-images c3ba40e link true /test okd-scos-images
ci/prow/security ec6d1fd link true /test security
ci/prow/golint ec6d1fd link true /test golint

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.

@elmiko
Copy link
Author

elmiko commented Aug 26, 2025

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 26, 2025
@elmiko
Copy link
Author

elmiko commented Aug 26, 2025

i have a feeling this will need a cleanup, but we should consider adding this for improved hypershift performance.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 25, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Nov 25, 2025
@openshift-merge-robot
Copy link

PR needs rebase.

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.

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

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants