Closed fromanu closed 4 years ago
This happens for the following reason: wicked calculates a configuration "hash" over the static configuration; this hashing mechanism also included the .git
folder, which in turns contains two files index
and HEAD
which are always written with dynamic content when a git clone
is done.
You can call this a regression bug; this happened when changing the hashing calculation for wicked 1.0.0-rc.1 to use a node internal hashing instead of relying on shasum
inside the API container.
Some edge cases are unfortunately still not working.
It works.
More edge cases not working: If there is a configuration upgrade step between versions, competing wicked versions will continuously restart each other, as the configuration has is calculated on the upgraded configuration, not on the original content from e.g. the git repository. The configuration has to be calculated before the configuration is upgraded.
When having 2 k8s clusters with 2 instances of wicked deployed inside, which are using the same configuration and are sharing the same Postgres database (Azure Database for PostgreSQL), the 2 wicked instances are killing each other. The following messages appear in the logs of the api pods from the 2 clusters and they are continuously failing and restarting: