Fix SWCK oapserverconfig e2e version mismatch#177
Merged
Conversation
…eout The SWCK operator matches OAPServerConfig to OAPServer by spec.version. The OAPServer uses version "latest" but the oapserverconfig-demo.yaml has version "9.5.0", so the operator never applies the config and the OAP pod is never restarted, causing the test to timeout.
The latest OAP requires a top-level 'layer: GENERAL' in LAL rules. Without it, the rule is ignored and log_count metrics are never produced, causing the log_count_info verification to fail with all-zero values.
Switch from SWCK v0.9.0 to commit e98e180 which includes the layer: GENERAL fix in the LAL rule, removing the local sed workaround.
kezhenxu94
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
OAPServerConfigtoOAPServerbyspec.version. The OAPServer uses versionlatestbut the upstreamoapserverconfig-demo.yamlhasversion: 9.5.0, so the operator never applies the config and the OAP pod is never restarted, causing the test to timeout.sed 's/version: 9.5.0/version: latest/'to align the OAPServerConfig version with the OAPServer.Test plan
Run SWCK oap-ui-agent-oapserverconfig Testpasses