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?
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
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...
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
-------
$ 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.
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
@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: