You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently we use anchors on the cos collection.yaml file to avoid repeating some of the stuff, including version numbers for all the different cos-whatever artifacts.
This keeps the versions in sync, especially between the cos system and cos recovery, as they should always match,
Autobumper is adding version numbers to those entries and may desync them, so you end up with a recovery with a version and a system with another.
The contents are the same, so its not a big problem but it could lead to confusion, after a cos-reset of one of your nodes in a cluster it suddenly reports a different version number for example.
To Reproduce
have a recovery with a different version number than your cos system, run cos-reset, check version number
Expected behavior
Recovery and system to have the same version.
cos-toolkit version:
master
CPU architecture, OS, and Version:
N/A
Describe the bug
Currently we use anchors on the cos collection.yaml file to avoid repeating some of the stuff, including version numbers for all the different cos-whatever artifacts.
This keeps the versions in sync, especially between the cos system and cos recovery, as they should always match,
Autobumper is adding version numbers to those entries and may desync them, so you end up with a recovery with a version and a system with another.
The contents are the same, so its not a big problem but it could lead to confusion, after a cos-reset of one of your nodes in a cluster it suddenly reports a different version number for example.
To Reproduce
have a recovery with a different version number than your cos system, run cos-reset, check version number
Expected behavior
Recovery and system to have the same version.
Logs
Tests cached this https://github.com/rancher-sandbox/cOS-toolkit/runs/4097481553?check_suite_focus=true
Additional context
The text was updated successfully, but these errors were encountered: