juju deploy permissions error

1

Receiving the following error when trying to deploy ceph-osd via juju

image
image1464×329 104 KB

2

Looks like a snap issue perhaps? Given that it can’t read stuff from /home.

Off the top of my head, sudo snap connect juju:home or sudo snap install juju --classic

3

I moved ceph.yaml to /home/user/.local/share/juju and did gave my user permissions to it and it finally worked.

4

I’ve run into a failed deployment on one of my machines though, how do I re-deploy or fix this machine?

image
image1651×401 99.1 KB

5

Hey Patrick, its hard to fully diagnose this without the controller log. You can get it with:

juju scp -m controller 0:/var/log/juju/machine-0.log .

This assumes your controller is running on machine 0 in the controller model. The charm install appears to be failing as it says in the debug message.

From the status output it looks like on machine 0 you have 3 ceph-mon units running in lxd containers and also one ceph osd unit running straight on the machine. Its generally not reccomended to mix running units in lxd containers and on the host machine itself, though technically it should work.

6

Oh I was just following this guide: Charmed Ceph manual install | Ubuntu.

Ceph-4 is a standalone machine deployed in MAAS, as well as Ceph-3 and ceph-2. Machine 0 in that screenshot is referring to ceph-4, to me it looks like my ceph-mon deployments are across all 3 machines not just machine 0.

My issue is that machine 2 failed deployment because of a timeout, and I’m not sure how to restart the deployment.

7

I have the machine in a ready state again, but how do I redeploy using juju to just have that one machine retry?

image
image1239×418 97.5 KB

8

image
image1787×381 135 KB

My “hook failed: “install”” logs, no idea whats going on here.

9

This is what I get when I try to run ./hooks/install from the node itself:

image
image1236×400 80.4 KB

10

Unsupported cloud: source option jammy-bobcat

This looks like the real error. I’m not familiar with Ceph though, I can’t tell you what it means.

If you want to try running hooks manually, you need to set up PATH and possibly environment for the call. For example, for k8s:

  • you’re in /var/lib/juju
  • the hook may be agents/unit-grafana-agent-k8s-0/charm/hooks/install
  • the hook tool may be tools/unit-grafana-agent-k8s-0/config-get

A simpler way is to follow https://juju.is/docs/juju/juju-debug-hook