Management or provisioning cluster manifest reports .status.agentDeplyment field, which should reflect the status of the agent deployment on the child cluster. In a scenario that something or someone removes components of the agent deployment on the child cluster, the field is not getting updated, which prevents turtles from re-applying agent manifests.
What did you expect to happen?
Turtles to be able to identify missing components on the child cluster and successfully execute import procedure.
How to reproduce it?
It is a race condition in a scenario when the provisioning cluster manifest is getting replaced with management cluster.
It is possible to reproduce by removing some parts of the import components on the child cluster, while the agent is not connected.
What steps did you take and what happened?
Management or provisioning cluster manifest reports
.status.agentDeplyment
field, which should reflect the status of the agent deployment on the child cluster. In a scenario that something or someone removes components of the agent deployment on the child cluster, the field is not getting updated, which prevents turtles from re-applying agent manifests.What did you expect to happen?
Turtles to be able to identify missing components on the child cluster and successfully execute import procedure.
How to reproduce it?
It is a race condition in a scenario when the
provisioning
cluster manifest is getting replaced withmanagement
cluster.It is possible to reproduce by removing some parts of the import components on the child cluster, while the agent is not connected.
Example of the failure: https://github.com/rancher/turtles/actions/runs/9709318524/attempts/1?pr=575
Last turtles logs:
Child cluster does not have a
cattle-system
namespace.Rancher Turtles version
v0.8.0
Anything else you would like to add?
No response
Label(s) to be applied
/kind bug