Andrei Kvapil 964bd83cf5 fix(ci): stop check-rd-presets reporting present presets as missing
The membership check piped printf into `grep -Fqx` under `set -o pipefail`.
`grep -q` exits on its first match, which can close the pipe while printf is
still in write(2); printf then fails with EPIPE, pipefail makes the pipeline
non-zero, and the negation reads that as "not found". A preset was therefore
reported missing precisely because it matched first.

It is a scheduling race, so it fired under `make -j4` in CI and not on an idle
machine. The cost was not cosmetic: `Unit & controller tests` gates `finalize`,
which gates `e2e`, so a false failure here skipped e2e and turned the required
`E2E Tests` context red, blocking merges on unrelated pull requests.

Feed grep from a here-string instead. No pipeline, nothing for pipefail to
judge, no writer to receive EPIPE. This is the only script under hack/ that
combined pipefail with a `| grep -q`.

The tests pin the two outcomes the check owes, a complete enum passing and an
incomplete one failing with the missing value named, rather than trying to win
the race: a test that only reddens when the scheduler cooperates is the flaky
kind this repo does not add. The fixture is written with jq alone so it does
not depend on which yq dialect is installed, and it creates its temp dir in the
test body because hack/cozytest.sh knows @test and nothing else.

Refs #4193

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
2026-09-10 13:41:12 +02:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

Open Source Apache-2.0 License Support Active GitHub Release GitHub Commit OpenSSF Best Practices OpenSSF Scorecard

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.

Cozystack user interface

Use-Cases

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.

Languages
Go 46.8%
Shell 37.9%
TypeScript 7%
Go Template 5.5%
Makefile 1.5%
Other 1.1%