-
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Hi @abmuslim, Thank you for reaching out! The issue you observe is typically due to a failure during scenario deployment. If you scroll down on the Execute tab you should see a list of network elements being deployed from your scenario. The save, event & dashboard buttons become enabled only once all network elements are in "Running" state. If one element is stuck in another state (e.g. "Pending") you will need to determine why your k8s pod is failing to start (e.g. bad image name, etc.). You can check the k8s pods logs to debug this. I also recommend trying to deploy the demo1 scenario to get a better understanding and more familiarity with the platform. The documentation on platform usage and demo1 can be found here: I hope this helps. |
Beta Was this translation helpful? Give feedback.
Hi @abmuslim,
Thank you for reaching out!
The issue you observe is typically due to a failure during scenario deployment. If you scroll down on the Execute tab you should see a list of network elements being deployed from your scenario. The save, event & dashboard buttons become enabled only once all network elements are in "Running" state. If one element is stuck in another state (e.g. "Pending") you will need to determine why your k8s pod is failing to start (e.g. bad image name, etc.). You can check the k8s pods logs to debug this.
I also recommend trying to deploy the demo1 scenario to get a better understanding and more familiarity with the platform. The documentation on platform usa…