SovereignCloudStack / SovereignCloudStack/cluster-stacks
SCS compliance tests are failling in e2e pipelines
Open
Nobody has claimed this yet.
bug
Container
- Dominant language
- Python
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
/kind bug
Currently the csc compliance tests in e2e pipeline fails, see this error message in the PR#134:
Testing standard Kubernetes node distribution and availability ...
Reference: https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Standards/scs-0214-v1-k8s-node-distribution.md ...
WARNING: There seems to be no distribution across multiple regions or labels aren't set correctly across nodes.
WARNING: There seems to be no distribution across multiple zones or labels aren't set correctly across nodes.
WARNING: There seems to be no distribution across multiple host-ids or labels aren't set correctly across nodes.
ERROR: The distribution of nodes described in the standard couldn't be detected.
... returned 1 errors, 0 aborts
Contributor guide
No contributing guide indexed for this repository
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
Start with the SCS compliance failure referenced in PR #134 and inspect the e2e pipeline configuration and test output. Trace how Kubernetes node regions, zones, and host IDs are supplied to the compliance test. Done means the e2e compliance tests detect the required node distribution without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- ci-cd, infrastructure, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100