Describe the bug
Under circumstance not fully understood, the operator reaches the Ready milestone even though important tasks like the content re-import have not been started.
It is suspected that the following sequence occurs:
A deployment job updates the cmcc resource
The operator updates some resources, for example the image spec for an sts
This makes some of the components "not ready" ("Waiting for components, 19 of 20 ready: still waiting for ...")
However, the milestone remains Ready, as this was the last milestone before the update to the resource.
Any deployment job inspecting the cmcc state.milestone field will see the milestone Ready, and will conclude that the deployment, including for example the re-import, have finished.
To Reproduce
see above
Expected behavior
The state.milestone field should only report Ready if all components are ready.
Describe the bug Under circumstance not fully understood, the operator reaches the Ready milestone even though important tasks like the content re-import have not been started.
It is suspected that the following sequence occurs:
To Reproduce see above
Expected behavior The state.milestone field should only report Ready if all components are ready.