Open sebay opened 8 months ago
Seems it is a 3.4.0 UI wrong instruction which is misleading. When enabling chaos it asked to apply: https://raw.githubusercontent.com/litmuschaos/litmus/master/mkdocs/docs/3.0.0-beta10/litmus-portal-crds-3.0.0-beta10.yml This is old CRD. It should ask to apply something like: https://github.com/litmuschaos/litmus/blob/f86aad1328bcc580c97cc1ab57ee217880e7fb08/mkdocs/docs/3.4.0/litmus-portal-crds-3.4.0.yml
@Saranya-jena @hrishavjha please take a look at this
What happened: Trying to get a basic container kill to work without success with Yaml created from 3.4.0 UI. Trying to save a fixed Yaml will not let me save it.
Logs:
{"mainLogs":"W0304 02:03:16.394831 1 client_config.go:552] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.\n2024/03/04 02:03:16 Error Creating Resource : ChaosEngine.litmuschaos.io 'container-kill-mcilxqr5' is invalid: [spec.experiments[0].spec.probe[0].runProperties.interval: Invalid value: 'string': spec.experiments[0].spec.probe[0].runProperties.interval in body must be of type integer: 'string', spec.experiments[0].spec.probe[0].runProperties.probePollingInterval: Invalid value: 'string': spec.experiments[0].spec.probe[0].runProperties.probePollingInterval in body must be of type integer: 'string', spec.experiments[0].spec.probe[0].runProperties.probeTimeout: Invalid value: 'string': spec.experiments[0].spec.probe[0].runProperties.probeTimeout in body must be of type integer: 'string']\n"}
What you expected to happen: It should kill container Where can this issue be corrected? (optional)
UI or backend or both. How to reproduce it (as minimally and precisely as possible): Workflow generated from UI using cmd probe
Anything else we need to know?: