Cannot deploy ceph-proxy charm to LXD container

[Bartosz Woronicz]

while I can deploy without any problem to VM or baremetal
ubuntu@k8sddev-juju-0:~$ juju deploy ceph-proxy ceph-proxy-deneb
Deployed "ceph-proxy-deneb" from charm-hub charm "ceph-proxy", revision 72 in channel quincy/stable on ubuntu@22.04/stable

it fails on deploying to lxd container

ubuntu@k8sddev-juju-0:~$ juju deploy --channel=quincy/stable --to lxd:0 ceph-proxy ceph-proxy-deneb
ERROR selecting releases: charm or bundle not found for channel "quincy/stable", base "amd64/ubuntu/22.04/stable"
available releases are:
  channel "pacific/stable": available bases are: ubuntu@20.04
  channel "octopus/beta": available bases are: ubuntu@20.04, ubuntu@18.04
  channel "luminous/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "reef/edge": available bases are: ubuntu@22.04, ubuntu@23.10, ubuntu@23.04
  channel "quincy/stable": available bases are: ubuntu@22.04, ubuntu@20.04, ubuntu@23.04, ubuntu@22.10
  channel "octopus/candidate": available bases are: ubuntu@20.04, ubuntu@18.04
  channel "latest/candidate": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@14.04, ubuntu@12.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10, ubuntu@19.10, ubuntu@19.04, ubuntu@18.10, ubuntu@17.10, ubuntu@17.04, ubuntu@16.10
  channel "pacific/candidate": available bases are: ubuntu@20.04
  channel "openstack-train/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "pacific/beta": available bases are: ubuntu@20.04
  channel "openstack-stein/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "reef/beta": available bases are: ubuntu@22.04, ubuntu@23.10, ubuntu@23.04
  channel "nautilus/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "mimic/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "latest/edge": available bases are: ubuntu@22.04, ubuntu@20.04, ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@14.04, ubuntu@12.04, ubuntu@23.10, ubuntu@23.04, ubuntu@22.10, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10, ubuntu@19.10, ubuntu@19.04, ubuntu@18.10, ubuntu@17.10, ubuntu@17.04, ubuntu@16.10
  channel "octopus/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "quincy/candidate": available bases are: ubuntu@22.04, ubuntu@20.04, ubuntu@23.04, ubuntu@22.10
  channel "quincy/beta": available bases are: ubuntu@22.04, ubuntu@20.04, ubuntu@23.04, ubuntu@22.10
  channel "openstack-rocky/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "openstack-queens/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
  channel "octopus/stable": available bases are: ubuntu@20.04, ubuntu@18.04
  channel "latest/beta": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@14.04, ubuntu@12.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10, ubuntu@19.10, ubuntu@19.04, ubuntu@18.10, ubuntu@17.10, ubuntu@17.04, ubuntu@16.10
  channel "reef/stable": available bases are: ubuntu@22.04, ubuntu@23.10, ubuntu@23.04
  channel "reef/candidate": available bases are: ubuntu@22.04, ubuntu@23.10, ubuntu@23.04
  channel "quincy/edge": available bases are: ubuntu@22.04, ubuntu@20.04, ubuntu@23.04, ubuntu@22.10
  channel "pacific/edge": available bases are: ubuntu@20.04, ubuntu@18.04, ubuntu@16.04, ubuntu@21.10, ubuntu@21.04, ubuntu@20.10
ERROR failed to deploy charm "ceph-proxy"

[Bartosz Woronicz (mastier1)]

That controller is on manual machine

Interestingly , the same works on localhost

mastier@drakkar:~$ juju add-model ceph
Added 'ceph' model on localhost/localhost with credential 'localhost' for user 'admin'
mastier@drakkar:~$ juju deploy --channel=quincy/stable --to lxd:0 ceph-proxy ceph-proxy-deneb
Deployed "ceph-proxy-deneb" from charm-hub charm "ceph-proxy", revision 72 in channel quincy/stable on ubuntu@22.04/stable
mastier@drakkar:~$ juju status
Model Controller Cloud/Region Version SLA Timestamp
ceph localhost-localhost localhost/localhost 3.3.1 unsupported 23:59:43+01:00

App Version Status Scale Charm Channel Rev Exposed Message
ceph-proxy-deneb waiting 0/1 ceph-proxy quincy/stable 72 no waiting for machine

Unit Workload Agent Machine Public address Ports Message
ceph-proxy-deneb/0 waiting allocating waiting for machine

[Bartosz Woronicz (mastier1)]

So seems that problem is manual machine deployment

When done via bundle, all works:

Located charm "ceph-proxy" in charm-hub, channel quincy/stable
Executing changes:
- upload charm ceph-proxy from charm-hub for base ubuntu@22.04/stable with architecture=amd64
- deploy application ceph-proxy from charm-hub on ubuntu@22.04/stable
- set constraints for easyrsa to ""
- set constraints for etcd to ""
- upload charm keystone from charm-hub for base ubuntu@22.04/stable with architecture=amd64
- set constraints for keystone to ""
- upload charm keystone-ldap from charm-hub for base ubuntu@22.04/stable with architecture=amd64
- set constraints for kubeapi-load-balancer to ""
- set constraints for kubernetes-control-plane to ""
- set constraints for kubernetes-worker to ""
- set constraints for mysql-innodb-cluster to ""
- set constraints for vault to ""
- add relation kubernetes-control-plane - storage-routing
- add relation kubernetes-worker - storage-routing
Deploy of bundle completed.

[Billy Olsen (billy-olsen)]

This appears to be an issue with Juju being able to resolve the charm, but it does not appear to be an issue with the ceph-proxy charm itself. As such, I've added the Juju project and marked the ceph-proxy charm task as invalid.

[Joseph Phillips (manadart)]

I suspect we are not capturing/passing architecture information when using manual machines.

Adding "#charmhub=TRACE" to logging configuration might help by showing us what we are sending to and getting back from Charmhub.

[Alastair Flynn (aflynn50)]

This is a manifestation of bug: https://bugs.launchpad.net/juju/+bug/2054375
A fix for this has just been committed on 3.3, should be out with the next version.

[Bartosz Woronicz (mastier1)]

Sounds great! Thank you! Looking forward to.