I am aware that lot of people faced this problem in the past and it could be related to a network issue in our env. If anybody can point me to right direction would be helpful.
As you say, this looks like a network issue in your env. The controller VM is unable to reach simple streams.
However, since you’re providing a metadata source, you shouldn’t need this. Once this is resolved, you may find you run into another problem. It is possible to bootstrap juju in an air-gapped environment, but takes a bit of work.
What version of juju are you using?
Could you try specifying --bootstrap-base ubuntu@22.04? It’s possible Juju is defaulting to ubuntu@20.04 if it’s an older version, which obviosuly isn’t included in the metadata-source youv’e provided.
I am using 3.5.4-genericlinux-amd64 and tried -bootstrap-base ubuntu@22.04 and ~/simplestreams same problem persists
we already have it deployed on LXD Baremetal cluster and everything works we are in the process of testing on openstack and deploying on our production use cases globally on openstack platform juju orchestrator with k8s backed by openstack private cloud. Hope we make it work.