| ... | ... | @@ -2,6 +2,10 @@ |
|
|
|
|
|
|
|
The following is the list of known issues in current and previous versions of Stork. You can also see all Stork issues under [this link](https://gitlab.isc.org/isc-projects/stork/issues?label_name[]=bug).
|
|
|
|
|
|
|
|
## Stork 1.16.0
|
|
|
|
|
|
|
|
If neither `--server-url` flag nor the `STORK_AGENT_SERVER_URL` environment variable is specified, the agent certificates and tokens are not validated. In this case, the Stork agent may run without some required certificates or with invalid ones. It may produce cryptic errors on every connection attempt [#1352].
|
|
|
|
|
|
|
|
## Stork 1.15.0
|
|
|
|
|
|
|
|
- A problem running demo and system tests were observed when running on Docker 25.x. The early investigation suggests it is a Docker issue. The matter is being investigated. One possible workaround is to downgrade Docker to version 23.x, which was proven to work [#1192].
|
| ... | ... | @@ -58,6 +62,7 @@ In reality, it only has the documentation build fix on top. |
|
|
|
|
|
|
|
- If upgrading from previous releases, see known issues for 0.8.0 below.
|
|
|
|
|
|
|
|
|
|
|
|
## Stork 0.8.0
|
|
|
|
|
|
|
|
- There are appearing problems with starting Stork demo using `rake docker_up` command on Ubuntu 20.04. This is due to a kernel bug and a workaround in Go runtime. GitLab https://gitlab.isc.org/isc-projects/stork/-/issues/306
|
| ... | ... | |
