Skip to content

Conversation

@DavidHurta
Copy link
Contributor

No description provided.

Utilize a new structure, which holds the relevant information
regarding the desired CVO configuration and its status to encapsulate
this information to a simple data structure.
Using the field we can avoid changing the actual logging during testing
by assigning a different function to the field if necessary.

We can now also verify that the handler field is being executed.
The information regarding enabled feature gates is now available
sooner in the code. Utilize this information to conditionally initialize
the configuration controller at a one specific place. If no configuration
controller is needed, this information is clearly stated by
the noninitialized configuration field.

The subsequent code can then easily check for existence of the configuration
using a nil.
An error in the start logic will now result in the immediate shutdown of the CVO,
rather than in the CVO catching the failed controller and continuing to work
by ignoring the failed start.
Due to recent changes, the two test functions can now be safely merged together.

The second function verified the overall synchronization of the configuration,
which is now also being exercised in the first function.

The tests cases were migrated over to the first function or were already present.
@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 Sep 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidHurta

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 Sep 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 24, 2025

@DavidHurta: 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/okd-scos-e2e-aws-ovn 439176c link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-techpreview 439176c link true /test e2e-aws-ovn-techpreview
ci/prow/e2e-agnostic-ovn 439176c link true /test e2e-agnostic-ovn

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.

@DavidHurta
Copy link
Contributor Author

Blocked by #1232

@petr-muller
Copy link
Member

/cc

@openshift-ci openshift-ci bot requested a review from petr-muller September 26, 2025 09:18
@petr-muller
Copy link
Member

/uncc

@openshift-ci openshift-ci bot removed the request for review from petr-muller September 30, 2025 13:31
@openshift-bot
Copy link
Contributor

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 Dec 30, 2025
@coderabbitai
Copy link

coderabbitai bot commented Dec 30, 2025

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)
  • do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

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

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/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants