Skip to content

OLS-2504 - Adding adaptation to lcore tests - WIP#2713

Open
JoaoFula wants to merge 6 commits intoopenshift:mainfrom
JoaoFula:lcore-tests-adaptation
Open

OLS-2504 - Adding adaptation to lcore tests - WIP#2713
JoaoFula wants to merge 6 commits intoopenshift:mainfrom
JoaoFula:lcore-tests-adaptation

Conversation

@JoaoFula
Copy link
Contributor

Description

Type of change

  • Refactor
  • New feature
  • Bug fix
  • CVE fix
  • Optimization
  • Documentation Update
  • Configuration Update
  • Bump-up dependent library
  • Bump-up library or tool used for development (does not change the final image)
  • CI configuration change
  • Konflux configuration change

Related Tickets & Documents

  • Related Issue #
  • Closes #

Checklist before requesting a review

  • I have performed a self-review of my code.
  • PR has passed all pre-merge test jobs.
  • If it is a core feature, I have added thorough tests.

Testing

  • Please provide detailed steps to perform tests related to this code change.
  • How were the fix/results from this change verified? Please provide relevant screenshots or results.

@JoaoFula JoaoFula marked this pull request as draft January 23, 2026 10:32
@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 Jan 23, 2026
@openshift-ci openshift-ci bot requested review from onmete and xrajesh January 23, 2026 10:32
@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch from 7e230e6 to fbc9a3d Compare January 23, 2026 15:12
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 25, 2026
@openshift-ci
Copy link

openshift-ci bot commented Jan 27, 2026

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

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

@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch from cc83464 to 9624157 Compare January 27, 2026 11:10
@JoaoFula JoaoFula marked this pull request as ready for review January 27, 2026 11:10
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 27, 2026
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 27, 2026
@openshift-ci openshift-ci bot requested a review from raptorsun January 27, 2026 11:11
@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch 7 times, most recently from 0e7bd31 to 0442f58 Compare January 29, 2026 10:42
@JoaoFula
Copy link
Contributor Author

JoaoFula commented Feb 2, 2026

/retest

@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch from 8b7483a to a22b712 Compare February 3, 2026 07:37
@JoaoFula
Copy link
Contributor Author

JoaoFula commented Feb 3, 2026

TODO:
As a follow up, we should remove the update_ols_config() from ols_installer and adapt_ols_config and just have this run as a fixture or being called in the data_collection test. It will simplify the installer files.

@JoaoFula
Copy link
Contributor Author

JoaoFula commented Feb 3, 2026

/retest

2 similar comments
@JoaoFula
Copy link
Contributor Author

JoaoFula commented Feb 6, 2026

/retest

@JoaoFula
Copy link
Contributor Author

/retest

@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch from a22b712 to 94d46ff Compare February 18, 2026 09:05
@JoaoFula
Copy link
Contributor Author

/retest

3 similar comments
@JoaoFula
Copy link
Contributor Author

/retest

@JoaoFula
Copy link
Contributor Author

/retest

@JoaoFula
Copy link
Contributor Author

/retest

@JoaoFula
Copy link
Contributor Author

/retest

1 similar comment
@JoaoFula
Copy link
Contributor Author

/retest

deactivating more tests
Removing bundle sync configuration from console tests. Just run the tests in main.

Removing bundle sync configuration from console tests. Just run the tests in main.

Removing bundle sync configuration from console tests. Just run the tests in main.

Removing bundle sync configuration from console tests. Just run the tests in main.

Adding obs owners for access to cluster pool logs

Adding obs owners for access to cluster pool logs

Adding obs owners for access to cluster pool logs
Deactivating operator pod for data collection test
@JoaoFula JoaoFula force-pushed the lcore-tests-adaptation branch from ee43854 to bfe0272 Compare February 27, 2026 13:39
@JoaoFula
Copy link
Contributor Author

/retest

@onmete
Copy link
Contributor

onmete commented Mar 2, 2026

/test e2e-ols-cluster

)
if not r:
raise Exception("Timed out waiting for new OLS pod to be ready")
raise Exception("Timed out waiting for {name} pod to be ready")
Copy link
Contributor

Choose a reason for hiding this comment

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

Missing f

# Update configmap with e2e-specific settings - FAIL FAST if this breaks
print("Updating configmap with e2e test settings...")
update_ols_configmap()
if OLS_SERVICE_DEPLOYMENT == "lightspeed-app-server":
Copy link
Contributor

Choose a reason for hiding this comment

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

How reliable is this condition? Should it be if not lcore_enabled?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

might be reliable but makes no sense when we have lcore_enabled. Good catch

)
if not r:
raise Exception("Timed out waiting for new OLS pod to be ready")
raise Exception("Timed out waiting for {name} pod to be ready")
Copy link
Contributor

Choose a reason for hiding this comment

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

Missing f.


provider = os.getenv("PROVIDER", "openai")
creds = os.getenv("PROVIDER_KEY_PATH", "empty")
update_lcore_setting()
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want to always executed this?

if lcore_enabled:
    update_lcore_setting()

And the update_lcore_setting is doing another check like lcore_enabled from env vars. Can we reuse a single constant defining if lcore is on/off through all places?

"deployment/lightspeed-operator-controller-manager",
"--replicas",
"0",
"1",
Copy link
Contributor

Choose a reason for hiding this comment

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

This should be 0 - this seems to be the cause of failures in the E2E.

@openshift-ci
Copy link

openshift-ci bot commented Mar 2, 2026

@JoaoFula: 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/verify 27be98b link true /test verify
ci/prow/e2e-ols-cluster 27be98b link true /test e2e-ols-cluster

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.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants