Hi, My OSM interface was working properly but all of a sudden I am unable to access the OSM UI. It is showing something went wrong as an error.
Please help me where I went wrong. Please find the screenshot for reference.
Hello,
Maybe a dumb question, but how you get back this information? Is it possible to get just the last part to export properly or we should REDO the overall deployment?
Thanks, Nicolas
Answering to my own question 
And it worked, but in UI I see the operational status in ERROR state.
Edit : The best fitted answer is more like
export OSM_PASSWORD='juju config keystone admin-password'
export OSM_HOSTNAME='juju config nbi site_url'
But I think that there is missing the 443 port and we shouldn’t request to HTTPS, am i wrong?
Hello Pietro
Looks like there was an issue with your installation of microk8s. Could you provide the output of the microk8s status command?
You can try to reinstall osm, but I would try to do it in a clean VM.
I suggest you to follow this tutorial: Installation tutorial
Hello Suresh
The same answer that I provided to Pietro.
Looks like there was an issue with your installation of microk8s. Could you provide the output of the microk8s status command?
You can try to reinstall osm, but I would try to do it in a clean VM.
I suggest you to follow this tutorial: Installation tutorial
Hello Nicolas
You are right, you need to add the port 443 and remove the “https://” if you are installing an OSM in release 12 or before.
In case you install release 13, the command would be juju config nbi external-hostname, and the returned value doesn’t contain “https://”
I hope that helps.
Hello @fsoldatos ,
You should update your last line, I had my cluster in OSM that was in error state : 1- Because of HTTPS Self Signed 2- Because of Microstack AUTH URL already having v3
The correct cmd line should be :
osm vim-create --name $VIM_NAME --user "$OS_USERNAME" \
--password "$OS_PASSWORD" --auth_url "$OS_AUTH_URL" \
--tenant "$OS_USERNAME" --account_type openstack \
--config='{use_floating_ip: True, management_network_name: osm-ext, insecure: True}'
Thanks also to @gcalvino
Hi @gcalvino,
I’m following that tutorial.
As far as the status, here follows the output:
microk8s is running
high-availability: no
datastore master nodes: 127.0.0.1:19001
datastore standby nodes: none
addons:
enabled:
dns # CoreDNS
ha-cluster # Configure high availability on the current node
ingress # Ingress controller for external access
metallb # Loadbalancer for your Kubernetes cluster
storage # Storage class; allocates storage from host directory
disabled:
ambassador # Ambassador API Gateway and Ingress
cilium # SDN, fast with full network policy
dashboard # The Kubernetes dashboard
dashboard-ingress # Ingress definition for Kubernetes dashboard
fluentd # Elasticsearch-Fluentd-Kibana logging and monitoring
gpu # Automatic enablement of Nvidia CUDA
helm # Helm 2 - the package manager for Kubernetes
helm3 # Helm 3 - Kubernetes package manager
host-access # Allow Pods connecting to Host services smoothly
inaccel # Simplifying FPGA management in Kubernetes
istio # Core Istio service mesh services
jaeger # Kubernetes Jaeger operator with its simple config
kata # Kata Containers is a secure runtime with lightweight VMS
keda # Kubernetes-based Event Driven Autoscaling
knative # The Knative framework on Kubernetes.
kubeflow # Kubeflow for easy ML deployments
linkerd # Linkerd is a service mesh for Kubernetes and other frameworks
metrics-server # K8s Metrics Server for API access to service metrics
multus # Multus CNI enables attaching multiple network interfaces to pods
openebs # OpenEBS is the open-source storage solution for Kubernetes
openfaas # OpenFaaS serverless framework
portainer # Portainer UI for your Kubernetes cluster
prometheus # Prometheus operator for monitoring and logging
rbac # Role-Based Access Control for authorisation
registry # Private image registry exposed on localhost:32000
traefik # traefik Ingress controller for external access
The issue is that the installation fails to connect
Bootstrap complete, controller "osm-vca" is now available in namespace "controller-osm-vca"
Now you can run
juju add-model <model-name>
to create a new model to deploy k8s workloads.
Track bootstrap_k8s bootstrap_k8s_ok: https://osm.etsi.org/InstallLog.php?&installation_id=1675938237-omPN1Pev3LcDNDca&local_ts=1675938261&event=bootstrap_k8s&operation=bootstrap_k8s_ok&value=&comment=&tags=
Creating OSM model
Added 'osm' model on microk8s/localhost with credential 'microk8s' for user 'admin'
Deploying OSM with charms
Creating Password Overlay
ERROR resolving with preferred channel: Post "https://api.charmhub.io/v2/charms/refresh": dial tcp 127.0.0.1:443: connect: connection refused
{}
ERROR application "vca" not found (not found)
{}
ERROR application "nbi" not found (not found)
{}
ERROR application "ng-ui" not found (not found)
{}
ERROR application "grafana" not found (not found)
{}
ERROR application "prometheus" not found (not found)
Waiting for deployment to finish...Hi @gcalvino
Installed on a new fresh Ubuntu installation; same result:
$ ./install_osm.sh --charmed --small-profile --k8s_monitor
...
Restarting kubelet
DNS is enabled
Creating Juju controller "osm-vca" on microk8s/localhost
Bootstrap to Kubernetes cluster identified as microk8s/localhost
Fetching Juju Dashboard 0.8.1
Creating k8s resources for controller "controller-osm-vca"
Downloading images
Starting controller pod
Bootstrap agent now started
Contacting Juju controller at 192.168.1.189 to verify accessibility...
Bootstrap complete, controller "osm-vca" is now available in namespace "controller-osm-vca"
Now you can run
juju add-model <model-name>
to create a new model to deploy k8s workloads.
Track bootstrap_k8s bootstrap_k8s_ok: https://osm.etsi.org/InstallLog.php?&installation_id=1676120445-7L4IkhgoqFjDv4aW&local_ts=1676120791&event=bootstrap_k8s&operation=bootstrap_k8s_ok&value=&comment=&tags=
Creating OSM model
Added 'osm' model on microk8s/localhost with credential 'microk8s' for user 'admin'
Deploying OSM with charms
Creating Password Overlay
ERROR resolving with preferred channel: Post "https://api.charmhub.io/v2/charms/refresh": dial tcp 127.0.0.1:443: connect: connection refused
{}
ERROR application "vca" not found (not found)
{}
ERROR application "nbi" not found (not found)
{}
ERROR application "ng-ui" not found (not found)
{}
ERROR application "grafana" not found (not found)
{}
ERROR application "prometheus" not found (not found)
Waiting for deployment to finish...
Model "osm" is empty.
0 / 15 services active
...
0 / 15 services active
Timed out waiting for OSM services to become ready
### sab 11 feb 2023, 14:16:41, CET check_osm_deployed: FATAL error: deploy_osm Timed out waiting for services to become ready
Track end fatal: https://osm.etsi.org/InstallLog.php?&installation_id=1676120445-7L4IkhgoqFjDv4aW&local_ts=1676121401&event=end&operation=fatal&value=deploy_osm&comment='Timed_out_waiting_for_services_to_become_ready'&tags=
BACKTRACE:
### FATAL_TRACK /usr/share/osm-devops/common/logging 40
### check_osm_deployed /usr/share/osm-devops/installers/charmed_install.sh 326
### deploy_charmed_osm /usr/share/osm-devops/installers/charmed_install.sh 298
### main /usr/share/osm-devops/installers/charmed_install.sh 552
### MAIN non_file_source 0
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
-------
### sab 11 feb 2023, 14:16:42, CET main: FATAL error: charmed_install charmed_install.sh failed
Track end fatal: https://osm.etsi.org/InstallLog.php?&installation_id=1676120445-7L4IkhgoqFjDv4aW&local_ts=1676121402&event=end&operation=fatal&value=charmed_install&comment='charmed_install.sh_failed'&tags=
BACKTRACE:
### FATAL_TRACK /usr/share/osm-devops/common/logging 40
### main /usr/share/osm-devops/installers/full_install_osm.sh 1230
### MAIN non_file_source 0
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
### MAIN non_file_source
-------Hello Pietro
I cannot reproduce your error. Seems to be something related with your networking. Please try the following:
juju deploy osm-vca-integrator --channel=13.0/stable
If you get the same error (that is what I am expecting), then there is a network issue with your environment.
Hello @gcalvino,
here follows the output:
$ juju deploy osm-vca-integrator --channel=13.0/stable
ERROR resolving with preferred channel: Post "https://api.charmhub.io/v2/charms/refresh": dial tcp 127.0.0.1:443: connect: connection refused
As far as my network configuration, the installation is on a single machine (my PC) with a fresh Ubuntu installation, the OSM installation is the first command issued on this machine and there is no problem to download anything is needed.
Hello Pietro,
Here we need some support from the Juju team.
Please, register in mattermost with this invitation. And ask the question in the following channel.
I am also in that channel, so I will help you with the question they may ask.
Best regards,
Guillermo
Hey, I want to follow this tutorial, but after entering command “./install_osm.sh --charmed” the installation gets stuck on “creating k8s resources for controller “controller-osm-vca”” and then exits with error that no controller is registered. I have clean install of Ubuntu 20.04 LTE, 12 CPU, 16GB RAM and 90 GB of HDD. How can I resolve this problem? Thanks
Hi,
Have you got an answer or you reinstalled your OSM?
Nicolas
Probably a bit late but the following solved this for me (I have to run this if I reboot the host running OSM):
microk8s.kubectl rollout restart statefulset ng-ui -n osm
1 Like
Hi, I am trying to install open source mano on ubuntu 20.04 with the configuration mentioned above, This is the screenshot
@venkatmanavarthi Did you manage to solve the NBI issue you faced? I can see it’s an authentication issue as per below logs from nbi pod but don’t know details about authentication workflow to Keystone
cherrypy.process.wspbus.ChannelFailures: AuthException('Error during user role listing using Keystone: The request you have made requires authentication. (HTTP 401) (Request-ID: req-e00adb14-96cd-4c17-976a-485ea5c5a3e3)')
On Keystone pod I can see error but not sure about the correlation:
2024-04-06T22:23:03.121Z [container-agent] socket.timeout: timed out
2024-04-06T22:23:03.493Z [container-agent] 2024-04-06 22:23:03 ERROR juju.worker.uniter.operation runhook.go:153 hook "keystone-pebble-ready" (via hook dispatching script: dispatch) failed: exit status 1
2024-04-06T22:23:03.493Z [container-agent] 2024-04-06 22:23:03 ERROR juju.worker.uniter pebblepoller.go:101 pebble poll failed for container "keystone": failed to send pebble-ready event: hook failed
Which Operating System you are using ?
I tried with Ubuntu 22.04 and current one is 20.04
shokry@charmed-osm-15:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal