elastic / elastic/integrations
[Stack 8.19.20-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - tablespace) in oracle.tablespace
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 182
Description
- Stack version: 8.19.20-SNAPSHOT
- Package: oracle
- Failing test: system test: (elastic-agent logs - tablespace)
- DataStream: tablespace
- Owners:
- @elastic/obs-infraobs-integrations
Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs2019110160: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-f8414932-28dc-466d-8eee-8734008f6c15 (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/47075
Latest 5 failed builds:
- https://buildkite.com/elastic/integrations/builds/48319
- https://buildkite.com/elastic/integrations/builds/48398
- https://buildkite.com/elastic/integrations/builds/48455
- https://buildkite.com/elastic/integrations/builds/48532
- https://buildkite.com/elastic/integrations/builds/48614
Contributor guide
Research direction
Start by rerunning the oracle.tablespace system test or inspecting the latest failed Buildkite runs, especially the elastic-agent logs for the tablespace DataStream. Investigate the reported ORA-12541 “TNS:no listener” connection failure; done means the test passes reliably without this degraded sql.query metricset error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100