elastic / elastic/integrations
[Stack 8.19.22-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - performance) in oracle.performance
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 225
Description
- Stack version: 8.19.22-SNAPSHOT
- Package: oracle
- Failing test: system test: (elastic-agent logs - performance)
- DataStream: performance
- Owners:
- @elastic/obs-infraobs-integrations
Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs988807896: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-f807608d-e8a9-4fb7-b7da-c4fa97779c38 (HEALTHY->DEGRADED): Error fetching data for metricset sql.query: cannot open connection: testing connection: user=\"sys\" standalone params={authMode:2 connectionClass: connectionClassLength:0 purity:0 newPassword: newPasswordLength:0 appContext: numAppContext:0 externalAuth:0 externalHandle: pool: tag: tagLength:0 matchAnyTag:0 outTag: outTagLength:0 outTagFound:0 shardingKeyColumns: numShardingKeyColumns:0 superShardingKeyColumns: numSuperShardingKeyColumns:0 outNewSession:0}: ORA-12541: TNS:no listener"
```
First build failed: https://buildkite.com/elastic/integrations/builds/49549
Contributor guide
Research direction
Start by examining the failing system test, “elastic-agent logs - performance,” in the oracle package and the first failed Buildkite run 49549. Trace the reported ORA-12541 connection failure and verify the test’s Oracle listener setup; done means the performance data stream test completes without the degraded metricset error.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100