canonical / canonical/operator
Tracing integration test failure
- Dominant language
- Python
- Stars
- 267
- Forks
- 136
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 28
Description
The tracing `test_deployment` integration test is consistently failing.
1. For some reason test_tracing is run under the secret tests. I assume that should not be the case.
2. The test fails when [integrating with tempo](https://github.com/canonical/operator/actions/runs/26018272398/job/76473267127) before getting to the actual tracing checks. The Juju log indicates minio or maybe k8s is not correctly configured.
Contributor guide
Research direction
Start by locating the tracing test_deployment and test_tracing integration tests and the workflow that runs secret tests. Reproduce the Tempo integration failure from the linked action run, then verify that test_tracing is in the intended test group and that the integration completes past the MinIO or Kubernetes setup before the tracing checks run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes, python
- Domain
- ci-cd, infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100