Open aasserzo opened 3 years ago
Hi @aasserzo, I've faced this bug too. I've found that it's caused by recent change to the cmdProbe structure, you can see the source here: https://github.com/litmuschaos/chaos-operator/blob/7e75803234f80c608c22306f844577a4f69431f5/pkg/apis/litmuschaos/v1alpha1/chaosengine_types.go#L230
Apparently, the docs weren't updated after the change.
Now the source
is indeed an object, but not a string. To replicate the inline behaviour on newer versions, just omit the source
field.
Hi @aasserzo, I've faced this bug too. I've found that it's caused by recent change to the cmdProbe structure, you can see the source here: https://github.com/litmuschaos/chaos-operator/blob/7e75803234f80c608c22306f844577a4f69431f5/pkg/apis/litmuschaos/v1alpha1/chaosengine_types.go#L230
Apparently, the docs weren't updated after the change.
Now the
source
is indeed an object, but not a string. To replicate the inline behaviour on newer versions, just omit thesource
field.
Thanks for your comment! I will omit the source field and start using a later release. I do think, however, this should be addressed in documentation, and a more informative error should be worded.
How can this work in Litmus v2.0.x, when the change in the mentioned CRD was introduced with that version?
What happened: Assuming the 2.1.0 operator is installed, and the appropriate RBAC yaml is applied, When the chaosengine yaml is applied with the following probe:
Then the following error is thrown:
What you expected to happen: I expect this probe to pass validation, as it does in Litmus 2.0.0
How to reproduce it (as minimally and precisely as possible): Install Litmus operator 2.1.0 Apply a chaosengine yaml with the aforementioned probe in the experiment spec
Anything else we need to know?: This works as-is in Litmus 2.0.0