Myasnikov Daniil c7dca5f1da test(e2e): record the upgrade lane's known failure instead of staying red
The lane is advisory, and an advisory check that is red for a reason
everyone already knows trains reviewers to ignore it — then it stops
working on the day it finds something new. It currently has exactly one
such reason: tenant-test/vm-instance-test does not return to Ready across
an upgrade (#3984), while the same workload passes on a fresh install in
the very same run.

Give the lane a ledger rather than a longer timeout or a suite exclusion.
hack/e2e-wait-hr-ready.sh learns an optional EXPECTED_NOT_READY_FILE, and
only hack/e2e-upgrade-apply.bats sets it; unset, the script behaves as it
always did, down to making no second listing call on the happy path, so
the install gate is untouched.

The entries have to expire on their own or the file becomes the thing it
was meant to prevent, a stale explanation outliving its defect. Three
rules do that, all failures rather than warnings:

  - a not-Ready release that is NOT listed still fails the gate;
  - a listed release that is Ready again fails until its line is deleted;
  - a line naming no release in the cluster fails too.

So the fastest way to remove a line is to fix the defect, and the file
cannot be wrong about the present without saying so. A named file that
cannot be read is also a failure: treating it as "nothing expected" would
turn a typo into a gate that quietly accepts more than it claims.

hack/wait-hr-ready_test.bats drives the real script through a kubectl stub
over all of it. It is deliberately not named hack/e2e-*.bats: the unit
target is $(filter-out hack/e2e-%.bats,...), so a file named after the
script it tests would be excluded from the suite and never run.

Verified non-vacuous by mutation — disabling each of the three rules in
turn turns exactly one case red, and the missing-file refusal likewise.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-08-28 15:36:37 +05: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.7%
Shell 37.8%
TypeScript 7.1%
Go Template 5.5%
Makefile 1.5%
Other 1.2%