First steps with Charmed OSM

I am also getting this error while triggering installation script with --charmed flag

cmd: ./install_osm.sh --charmed

error: permanently dropping privs did not work: File exists
permanently dropping privs did not work: File exists
Microk8s storage failed to enable
permanently dropping privs did not work: File exists

Please help !!!

I am stuck

Hello @rachit24,

Where are you installing OSM? Could you tell me please the OS you are using, the memory, disk, and cpus that you are allocating to the machine?

I have updated the instructions to deploy the latest release of OSM (Release TEN)

Please provide me the link where can i find the latest instructions.

Thanks for replying.

Please find the below details.

OS - Ubuntu 20.4 and 18.04
Memory- 32GB
disk- 150 GB
cpu-16

Hi @davigar15,

Thanks for the installation guide!,
I have encountered the following problem at the end of the installation:

14 / 14 services active
OSM with charms deployed
Trying to install osmclient from channel 10.0/stable
Se ha instalado osmclient (10.0/stable) v10.0.1-0-g42e87fa por OSM Support (osmsupport)
osmclient snap installed
ERROR: Error 404: <html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.19.0</center>
</body>
</html>

ERROR: Error 404: <html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.19.0</center>
</body>
</html>

Your installation is now complete, follow these steps for configuring the osmclient:

1. Create the OSM_HOSTNAME environment variable with the NBI IP

export OSM_HOSTNAME=nbi.192.168.68.105.nip.io:443

2. Add the previous command to your .bashrc for other Shell sessions

echo "export OSM_HOSTNAME=nbi.192.168.68.105.nip.io:443" >> ~/.bashrc

DONE

After creating the variables appears the following issue:

osm version
ERROR: Error 404: <html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.19.0</center>
</body>
</html>

How can i solve it? Thanks

1 Like

Hello,

I’m getting the same error as mentioned here along with an ValueError: A role (--compute or --control) must be specified when using --auto error regarding microstack initialization proccess, when trying to install OSM along with microstack using the command : ./install_osm.sh --charmed --microstack .

Are these known issues?
Thanks in advance.

Same error here

Hello @virs,

There was a fix for that that probably hasn’t land in ReleaseTEN yet.

I updated the instructions to get the installer from master:

To fix the issue you could delete the current installation and execute the command above again. (to uninstall: juju kill-controller osm-vca -t 0 -y)

Hello, there is an upstream bug to track the microstack issue.

As a workaround, install OSM without the --microstack option, and instead, after the installation, execute the following:

sudo snap install microstack --devmode --channel beta
sudo snap set microstack config.network.ports.dashboard=8080
sudo microstack.init --auto --control

. /var/snap/microstack/common/etc/microstack.rc
microstack.openstack network create --enable --no-share osm-ext
microstack.openstack subnet create osm-ext-subnet --network osm-ext \
                                                    --dns-nameserver 8.8.8.8 \
                                                    --subnet-range 172.16.0.0/24
microstack.openstack router create external-router
microstack.openstack router add subnet external-router osm-ext-subnet
microstack.openstack router set --external-gateway external external-router
for i in $(microstack.openstack security group list | awk '/default/{ print $2 }'); do
    microstack.openstack security group rule create $i --protocol icmp --remote-ip 0.0.0.0/0
    microstack.openstack security group rule create $i --protocol tcp --remote-ip 0.0.0.0/0
done

curl https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img | microstack.openstack image create --public --container-format=bare --disk-format=qcow2 ubuntu16.04
curl https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd64.img | microstack.openstack image create --public --container-format=bare --disk-format=qcow2 ubuntu18.04
export VIM_NAME=microstack
osm vim-create --name $VIM_NAME --user "$OS_USERNAME" --password "$OS_PASSWORD" \
    --auth_url "$OS_AUTH_URL/v3" --tenant "$OS_USERNAME" --account_type openstack \
    --config='{use_floating_ip: True, management_network_name: osm-ext}'

That should fix it :wink:

4 Likes

Hi, I did this but I’m still getting the same error that @vris when accessing the UI:

When I run the command:
microk8s.kubectl -n osm describe ingress,
I get in the default backend
default-http-backend:80 (<error: endpoints "default-http-backend" not found>)
There is no connection with the NBI. How can I fix this. Thank you.

1 Like

Hello @davigar15, I am having the same issue as described by @virs. I tried the fix that you identified but it didn’t work, I’m still having the 404 errors when trying to use osm commands.

This is clearly an issue with version 10, I installed version 9 and everything works correctly. Looks like the ingress is not routing correctly the requests or does not have a correct route to the service hence falling in the default backend and given that this one is not defined as you can see in my previous post, it throws a 404 error.

@gruyaume, @amh94, and @virs:

Have you tested what I explained in the following comment?

Hi, yeah, i tried what you suggested but it didn’t work either at least for me. Then I uninstalled again and install version nine.

Yes, i tried that but it didn´t work

Thanks, i will try installing version nine according to the instructions suggested

Same as the others, I tried but it didn’t work. I just tried with version nine but I got the “permanently dropping privs did not work: File exists” which looks like an intermittent issue. I will re-try again…

Hi all!

I followed tutorial : Juju | The simplest way to deploy and maintain applications in the cloud
and noticed that I have differences between outputs from tutorial and my outputs:

  1. After typing command ‘juju clouds --controller osm-vca’ I got only lxd-cloud and microk8s
  2. After typing command ‘juju status ui-k8s | grep kubernetes | awk ‘{print $8}’’ I got zero matches
  3. After typing commands ‘microstack.openstack network list’ and ‘microstack.openstack router list’, commands were not found
  4. After typing ‘osm vim-list’, output didn’t list any vim

Other outputs from step ‘understanding installation steps’ (linked in first line) are fine.
I installed microstack using snap, but I don’t know how to connect microstack with osm the way it should be done during installation osm charmed.

  1. Now when I try to follow steps https://juju.is/tutorials/charmed-osm-get-started#4-onboarding-vnfs I cannot create basic NS, because of vim microstack not found.
    osm ns-create --ns_name basic-06-proxy-charm
    –nsd_name ha_proxy_charm-ns
    –vim_account microstack
    –config ‘{
    vld: [ { name: mgmtnet, vim-network-name: osm-ext } ]
    }’
    I attached screenshot with outputs. Does anyone have an idea what should I do, if this differences are normal and how I can connect vim microstack with osm? Thanks for help in advance.

Hi
I was installing OSM on Ubuntu 18.04 (8CPU/16GB RAM/ 80GB HDD/Single VM running over VMware workstation). It is stuck in DNS enabled. I followed this post not sure what is wrong, can you please suggest. Please see the status.

Thank you
Best Regards
K