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
This behaviour is ultimately the result of rollout.Spec.Selector being nil when calling labelsutil.CloneSelectorAndAddLabel and seems to be a result of the logic within controller.go where any error returned by c.refResolver.Resolve(r) is initially ignored (only handled later here)
Checklist:
Describe the bug
When using
workloadRef
, controller will end up recovering from panic if referenced workload does not exist.Due to the panic the
status
on theRollout
is also never updated.To Reproduce
Apply following YAML to cluster of your choice.
Monitor controller logs to observe "recover from panic" (see logs below).
Describe rollout
Expected behavior
Controller should gracefully handle this situation and set appropriate status (could reuse
InvalidSpec
) and message detailing the problem.Screenshots
Version
v1.8.0
Logs
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: