elastic / elastic/integrations

[LogsDB] [Stack 8.19.18-SNAPSHOT] [oracle] Failing test daily: system test: (elastic-agent logs - performance) in oracle.performance

Open
#19,848 0 comments 0 reactions 0 assignees View on GitHub
automation flaky-test Integration:oracle Team:Obs-InfraObs
Dominant language
Handlebars
Stars
333
Forks
647
Avg merge
3d 4h
Merged PRs (30d)
209

Description

- Stack version: 8.19.18-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.logs3582367509: [0] found error "Unit state changed sql/metrics-default-sql/metrics-oracle-3b18977d-90a8-4e3e-a97a-5c65d47868f5 (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/45219

Latest 5 failed builds:
- https://buildkite.com/elastic/integrations/builds/45764
- https://buildkite.com/elastic/integrations/builds/45840
- https://buildkite.com/elastic/integrations/builds/45910
- https://buildkite.com/elastic/integrations/builds/45971
- https://buildkite.com/elastic/integrations/builds/46035

Contributor guide

Open the contributing guide

Research direction

Start with the failing `elastic-agent logs - performance` system test for the `oracle` package and inspect the linked Buildkite failures, focusing on the `ORA-12541: TNS:no listener` connection error. Determine the relevant test setup and connection path; done means the performance data stream test runs without this connection error.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.