elastic / elastic/integrations
[LogsDB] [Stack 8.19.17-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - performance) in oracle.performance
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 182
Description
- Stack version: 8.19.17-SNAPSHOT
- LogsDB: enabled
- 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.logs4114068168: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-81b9358b-60c3-467d-8ac4-3307e30929fa (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/45080
Latest failed builds:
- https://buildkite.com/elastic/integrations/builds/45168
Contributor guide
Research direction
Start with the `system test: (elastic-agent logs - performance)` case in `oracle.performance` and inspect the failed Buildkite builds 45080 and 45168. Trace the `sql.query` connection failure and determine why the Oracle listener is unavailable; done means the performance test completes without the ORA-12541 error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100