Skip to content

wip: reset default pod affinity unless replica count is 2#1265

Open
flavianmissi wants to merge 2 commits intoopenshift:mainfrom
flavianmissi:fix-pod-affinity
Open

wip: reset default pod affinity unless replica count is 2#1265
flavianmissi wants to merge 2 commits intoopenshift:mainfrom
flavianmissi:fix-pod-affinity

Conversation

@flavianmissi
Copy link
Member

@flavianmissi flavianmissi commented Oct 28, 2025

this is an attempt to fix the TestScaleUp e2e failures.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 28, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flavianmissi

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2025
@flavianmissi
Copy link
Member Author

flavianmissi commented Oct 28, 2025

/test e2e-azure-operator
/test e2e-gcp-operator

@flavianmissi
wip: add a hash to deployment in attempt to generate a new version
f1e4d93 
TestScaleUp is still failing, and I suspect it might be due to an
improperly cleanup of the pod affinities.
Try adding a hash annotation to force update when we want to clear up
the pod affinities.
@flavianmissi
Copy link
Member Author

flavianmissi commented Oct 29, 2025

looks like TestScaleUp passed in e2e-aws-operator, let's run it on all the *-operator tests to be on the safe side.

/test e2e-aws-operator
/test e2e-azure-operator
/test e2e-gcp-operator

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 29, 2025

@flavianmissi: 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/hypershift-e2e-aks f1e4d93 link true /test hypershift-e2e-aks
ci/prow/e2e-gcp-operator f1e4d93 link false /test e2e-gcp-operator
ci/prow/e2e-aws-operator f1e4d93 link true /test e2e-aws-operator
ci/prow/e2e-azure-operator f1e4d93 link false /test e2e-azure-operator
ci/prow/unit f1e4d93 link true /test unit

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot
Copy link
Contributor

openshift-bot commented Jan 28, 2026

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 Jan 28, 2026
@openshift-bot
Copy link
Contributor

openshift-bot commented Feb 27, 2026

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

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

openshift-merge-robot commented Feb 27, 2026

PR needs rebase.

Details

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.

@openshift-ci openshift-ci bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ricardomaraschini ricardomaraschini Awaiting requested review from ricardomaraschini

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@flavianmissi @openshift-bot @openshift-merge-robot