OLS-2504 - Adding adaptation to lcore tests - WIP#2713
OLS-2504 - Adding adaptation to lcore tests - WIP#2713JoaoFula wants to merge 6 commits intoopenshift:mainfrom
Conversation
7e230e6 to
fbc9a3d
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
cc83464 to
9624157
Compare
0e7bd31 to
0442f58
Compare
|
/retest |
8b7483a to
a22b712
Compare
|
TODO: |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
a22b712 to
94d46ff
Compare
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
1 similar comment
|
/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
…ool calling enabled
ee43854 to
bfe0272
Compare
|
/retest |
|
/test e2e-ols-cluster |
tests/e2e/utils/cluster.py
Outdated
| ) | ||
| 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") |
tests/e2e/utils/adapt_ols_config.py
Outdated
| # 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": |
There was a problem hiding this comment.
How reliable is this condition? Should it be if not lcore_enabled?
There was a problem hiding this comment.
might be reliable but makes no sense when we have lcore_enabled. Good catch
tests/e2e/utils/cluster.py
Outdated
| ) | ||
| 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") |
tests/e2e/utils/ols_installer.py
Outdated
|
|
||
| provider = os.getenv("PROVIDER", "openai") | ||
| creds = os.getenv("PROVIDER_KEY_PATH", "empty") | ||
| update_lcore_setting() |
There was a problem hiding this comment.
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?
tests/e2e/utils/adapt_ols_config.py
Outdated
| "deployment/lightspeed-operator-controller-manager", | ||
| "--replicas", | ||
| "0", | ||
| "1", |
There was a problem hiding this comment.
This should be 0 - this seems to be the cause of failures in the E2E.
|
@JoaoFula: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Description
Type of change
Related Tickets & Documents
Checklist before requesting a review
Testing