layer5io / layer5io/learn-layer5
Test failure: Conflict with artifacts from prior test run
Open
Nobody has claimed this yet.
area/tests
kind/bug
- Dominant language
- Go
- Stars
- 72
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Description
SMI Conformance was run for one service mesh. The test failed to complete, so the meshery namespace was manually deleted. Some deploy artifacts were orphaned. When the test was invoked for a different service mesh, a collision occurred.
Logs
Error installing smi tool: rendered manifests contain a resource that already exists. Unable to continue with install:
ClusterRoleBinding "smi-conformance" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm";
annotation validation error: missing key "meta.helm.sh/release-name": must be set to "smi-conformance";
annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "meshery"
Environment:
- Version: v0.5.0-beta-4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing SMI Conformance for one service mesh, deleting the meshery namespace after failure, and running it for a different mesh while reviewing the Helm installation logs. Done means a subsequent run completes without a collision with the existing smi-conformance ClusterRoleBinding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100