elastic / elastic/integrations

[Stack 8.19.22-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - tablespace) in oracle.tablespace

Open
#21,210 0 comments 0 reactions 0 assignees View on GitHub
automation flaky-test
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

- Stack version: 8.19.22-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.logs3437261993: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-516c544b-912f-4079-9c26-13753d430bfa (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

Open the contributing guide

Research direction

Start with the Oracle tablespace system test for the elastic-agent logs data stream and review the failure from build 49549. Investigate the ORA-12541 no-listener error during the sql.query metricset connection, then rerun the test and confirm the tablespace data stream no longer reports a degraded unit.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.