I’m starting to get tired of this bundle. It supposed to make my life easier but I’ve already spent 2 days debugging things.
So, OSM and microk8s have been installed, but microstack fails with errors (at: sudo microstack.init --auto):
and a few lines below:
Below is a huge clipping of my terminal. Again, it is very bad that you have so many new member rules applied… I can’t post 2nd screenshot and I can’t upload a file (.rtf, .pdf) of my terminal outputs… This makes sharing my problem and asking for advice very difficult.
Anyway, below is the clipping of the error:
Note that I have tried numerous times on –channel=edge/rocky and once on –channel=edge. Same error. Funny thing is that yesterday, on my other installation I got the same error a few times, but then had an idea and resolved it. But I can’t remember what I did trying around staff. Certain thing is that I deviated from the procedure above. I kept the terminal log until the point of the problem but sadly not the solution. So, in this installation I came to a dead end.
So, if I get no response from you in the next days… I guess I’m dropping it
Thanks for testing out the new dev stack. Sorry to hear you’ve run into so many troubles with it!
Most of the team has just traveled back from the Hackfest in Patras, so it may take a day or two for them to respond. We’re eager to understand the problems you faced, so we can make the experience better for everyone.
Let me confirm first that I am using Ubuntu 18.04 LTS as mentioned above on a fresh VM installation on vbox at each attempt. Regarding resources, I gave the VM 16GB memory, ~80GB disk and 4CPUs as recommended.
I keep monitoring the juju status during deployment and on the problem of: “ERROR cannot deploy bundle: cannot add charm “cs:~charmed-osm/grafana-k8s-21”:” the juju status could not give a printout at all. With my workaround on iptables I didn’t see any issue on juju status.
I am not behind a proxy on home computer that I tried installation.
My current problem is Microstack, so I can’t really follow the installation step on your instructions. Enhancements on performance are highly appreciated, but I’m trying to figure out the problem before trying from scratch for a 4th/5th time.
I will use your email to send you a command log from MobaXterm since I can’t upload it here
I have checked this on one of the terminals… the DNS was running. I haven’t kept a sceenshot of that but I will next time I’ll start it up. I have send you an email with the main terminal output
My other terminal was mainly used to check juju status kube-system pods etc, so I didn’t save it afterwards…
I was always doing fresh installations before and haven’t really got a chance before to power off and power on the VM. Today, to get the printout you requested I powered it on again… but juju status printouts nothing (it is hanged) and get pods gives status unknown. About an hour has passed from powering on.
i would swear that they were both ok last time I had it opened. I even tried the microstack init after everything on juju status appeared running.
At any case, the settings of the VM is also shown above… (I had to combine 3 images into one)
Sorry for the late answer.
Regarding the Grafana dashboard, this is a known issue. You can import the dashboard manually. You can find OSM dashboards in devops repository in /installers/docker/grafana folder. The dashboards you need to import are: osm-sample-dashboard.json and osm-system-dashboard.json.
And regarding the status of mon-k8s, it takes some minutes to the pod in order to be available. In case, the issue persists, then try the following commmand that will restart the agent: microk8s.kubectl -n osm delete pods mon-k8s-operator-0 --force --grace-period 0
Thanks for the response.
I think something went wrong during my charmed osm installation and Grafana is not configured properly. However, I was able to query the metrics via osm_prometheus under ‘Explore’
Regarding the juju status, the above command did not work and I’m yet to find out how to restart terminated components.