NS instantiation stuck in "scheduled" state

After setting OSM, including a VIM with Openstack & a K8s Cluster, when instantiating a new NS, the instantiation is created but the status is in “scheduled” state indefinitely.

CleanShot 2022-05-19 at 09.39.04@2x

What could be the problem?



It is possible that you are facing problems with one or more OSM components/services. Been there before… :frowning:
That time, I rebooted OSM’s machine and the components got up and running and kept stable for a long time. It is not uncommon for us to be rebooting OSM, unfortunately.

Although, you can have a more ‘severe’ problem at hands.
The best thing you could do is to check the lcm’s logs in K8s.

You can then check them by executing the command kubectl logs <pod_name> -n osm
Using this logs I think you’ll be able to better grasp what is the root cause of the issues you’re facing.

If you need additional help, I’m here :slight_smile:

Rafael Direito