Aleksei Sviridkin
9e3f66f2b2
## What this PR does The node-join diagnostics already read the worker's CPU counters twice on failure, but they read the compute container's cgroup, and that cgroup holds every thread QEMU runs: the guest vCPUs, the emulator thread, the IO threads. A container spending most of its quota while the guest makes no progress has two incompatible readings and no container-level counter picks one. This adds the per-thread split. It execs into each Running worker's compute container and copies the QEMU process's `/proc/<pid>/task/<tid>/stat` lines into the artifact verbatim, with a legend. Nothing is computed in the collector. The legend is there because the field positions are a trap that gives a wrong answer instead of an error: a vCPU thread is named `CPU 0/KVM`, that space sits inside the comm parentheses, and awk over whitespace then reads the wrong column for exactly the threads the split is about. It runs in the sampling loop the other two subjects already share, so there is no second wait. Rates come from the two files and the stamps in them. Every way the read can fall short gets its own sentence in the artifact instead of an empty directory, and neither the legend nor the pairing instruction is attached to a read that did not finish. Coverage is `hack/run-kubernetes-thread-cpu_test.bats`, under `make unit-tests`. It drives those outcomes rather than grepping the source for them, and runs the probe against staged `/proc` trees. Context: cozystack/cozystack#3513. This is an instrument, not a fix, and it does not close that issue. ### Screenshots Not a UI change. ### Downstream repositories Walked against the diff. It touches `hack/e2e-chainsaw/_lib/run-kubernetes.sh`, the two kubernetes chainsaw suites, three `hack/*.bats` files and one paragraph in `docs/agents/e2e-testing.md`. Nothing under `packages/` moves, no ApplicationDefinition, schema, enum or default changes, no namespace or platform variant is renamed, no metric changes, and no label or annotation another component matches as a literal is touched. The two repositories that vendor out of `hack/` take `hack/package.mk` and `hack/update-crd.sh`, and neither is in this diff. - [x] No downstream repository is affected by this change - [ ] [cozystack/website](https://github.com/cozystack/website) - follow-up: - [ ] [cozystack/terraform-provider-cozystack](https://github.com/cozystack/terraform-provider-cozystack) - follow-up: - [ ] [cozystack/ansible-cozystack](https://github.com/cozystack/ansible-cozystack) - follow-up: - [ ] [cozystack/ccp](https://github.com/cozystack/ccp) - follow-up: - [ ] [cozystack/talm](https://github.com/cozystack/talm) - follow-up: - [ ] [cozystack/cozyhr](https://github.com/cozystack/cozyhr) - follow-up: - [ ] [cozystack/cozy-proxy](https://github.com/cozystack/cozy-proxy) - follow-up: - [ ] [cozystack/cozystack-telemetry-server](https://github.com/cozystack/cozystack-telemetry-server) - follow-up: - [ ] [cozystack/external-apps-example](https://github.com/cozystack/external-apps-example) - follow-up: - [ ] [cozystack/examples](https://github.com/cozystack/examples) - follow-up: ### Release note ```release-note test(e2e): on tenant node-join failure, capture how the compute container's CPU time splits across QEMU's vCPU, emulator and IO threads ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added per-thread CPU diagnostics for worker compute processes. - Reports sampling timestamps, outcomes, interpretation notes, and relevant missing or incomplete data. - Improved Pod and node discovery for diagnostic collection. - **Documentation** - Clarified diagnostic sampling intervals, timing, and collection budgets. - **Tests** - Added comprehensive coverage for per-thread CPU diagnostics, bounded sampling, failure handling, fallbacks, and budget enforcement. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.