elastic / elastic/integrations
[Stack 8.19.17-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - memory) in oracle.memory
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
Description
- Stack version: 8.19.17-SNAPSHOT
- Package: oracle
- Failing test: system test: (elastic-agent logs - memory)
- DataStream: memory
- Owners:
- @elastic/obs-infraobs-integrations
Failure:
```
test case failed: one or more errors found while examining elastic-agent.logs3580259436: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-2c05f95f-db82-4bbc-86f6-876eb5dee367 (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/45081
Latest failed builds:
- https://buildkite.com/elastic/integrations/builds/45169
Contributor guide
Research direction
Start with the latest failed Buildkite build 45169 and its oracle.memory system-test logs, then inspect the elastic-agent logs check and SQL connection setup shown in the failure. Determine why the Oracle listener is unavailable and rerun the test; done means the memory data stream remains healthy without the ORA-12541 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