Hello,
I’m trying to install OSM v10 by using ./install_osm.sh -R ReleaseTEN --charmed and the deployment is pending just after the microk8s installation. Is anybody facing the same issue?
I’m attaching a screenshot for your reference:
Thanks in advance.
Hi,
When I deploy charmed OSM in OpenStack, I have to assign a floating ip for me to access the VM. May I ask how can I expose external ip to OSM so that I can access the services such as web ui, grafana etc.?
When I ran sudo microk8s.kubectl describe ingress -n osm it shows me internal hostname. However I need external hostname that uses the floating point ip. How can I do that?
Thanks, James
HI, I was trying to install OSM in Ubuntu 20.04. I am facing an error while giving authentication for OSM user interface. Could you please suggest me where I went wrong. Please see the screenshot of the error and juju status below.
Hello,
Charmed OSM changes the default password for security reasons. In the installation log the password you need to use is shown, but you can get it with this command:
juju config keystone admin-password
Use that password to log in the UI.
For the CLI you can set the password with the following command:
export OSM_PASSWORD=`juju config keystone admin-password`
Please, let me know if that fixes your problem.
Best regards,
Guillermo
Thank you for the suggestion Guillermo.
Regards, Jesty Mariam
Hi, I am trying to install osm charmed with microstack but I get this error when I am trying to use osm command (28, ‘Resolving timed out after 15000 milliseconds’) Maybe “–hostname” option or OSM_HOSTNAME environment variable needs to be specified Please refer to the screenshot below. Please let me know where I went wrong.
Did you export the OSM_HOSTNAME and OSM_PASSWORD environment variables? That information is printed out at the end of the installation.
Hello,
I’m trying to install OSM in Windows 11 with a multipass VM, following the info in How to get started with Charmed OSM
The last outputs of the command “./install_osm.sh --charmed” are the following:
...
Track k8scluster k8scluster_ok: https://osm.etsi.org/InstallLog.php?&installation_id=1673735435-It5UNJL3mrTmrqJm&local_ts=1673735840&event=k8scluster&operation=k8scluster_ok&value=&comment=&tags=
juju (2.9/stable) 2.9.37 from Canonical** installed
Track juju juju_ok: https://osm.etsi.org/InstallLog.php?&installation_id=1673735435-It5UNJL3mrTmrqJm&local_ts=1673736109&event=juju&operation=juju_ok&value=&comment=&tags=
Enabling MetalLB
Applying Metallb manifest
Warning: policy/v1beta1 PodSecurityPolicy is deprecated in v1.21+, unavailable in v1.25+
E0114 23:53:17.817290 9393 request.go:1101] Unexpected error when reading response body: http2: client connection lost
error when retrieving current configuration of:
Resource: "/v1, Resource=namespaces", GroupVersionKind: "/v1, Kind=Namespace"
Name: "metallb-system", Namespace: ""
from server for: "STDIN": Get "https://127.0.0.1:16443/api/v1/namespaces/metallb-system": http2: client connection lost
...
Any hint how to fix this error?
— Edit —
The situation doesn’t change not using multipass, but running the installation in a partition or a standalone Ubuntu PC. The results of the intermediate installation steps are
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
osm osm-vca microk8s/localhost 2.9.29 unsupported 18:24:10+01:00
Model "admin/osm" is empty.
$ microk8s.kubectl -n osm get all -n osm
NAME READY STATUS RESTARTS AGE
pod/modeloperator-866bfb7db9-vhz64 1/1 Running 2 (9m56s ago) 149m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/modeloperator ClusterIP 10.152.183.201 <none> 17071/TCP 149m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/modeloperator 1/1 1 1 149m
NAME DESIRED CURRENT READY AGE
replicaset.apps/modeloperator-866bfb7db9 1 1 1 149m
So grafana, kafka and statefulset.apps are missing
Thanks, Pietro
I am seeing the same error. Were you able to resolve the issue
hello @davigar I am trying to install charmed OSM on UBUNTU 20.04 by following the steps Any help would be appreciated here
ubuntu@mano:~$ ./install_osm.sh --charmed
Checking required packages to add ETSI OSM debian repo: software-properties-common apt-transport-https
OK …
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
DNS is enabled
Microk8s storage failed to enable
microk8s is not running. Use microk8s inspect for a deeper inspection.
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.