Activity log for bug #2048333

Date Who What changed Old value New value Message
2024-01-05 13:46:33 Boris Lukashev bug added bug
2024-01-05 13:47:07 Boris Lukashev description When adding ceph-fs to an existing cluster with `juju deploy ceph-fs -n 3 --to lxd:0,lxd:1,lxd:2 --config ceph-public-network=10.10.122.0/24`, the containers never resolve as they are brought up on the ceph-cluster-network without the vNIC for the ceph-public network which both the mon and radosgw containers on the same host are given... Locks up charm provisioning since the containers exist but not on the right network. Bit of a show-stopper When adding ceph-fs to an existing cluster with `juju deploy ceph-fs -n 3 --to lxd:0,lxd:1,lxd:2 --config ceph-public-network=10.10.122.0/24`, the containers never resolve as they are brought up on the ceph-cluster-network without the vNIC for the ceph-public network which both the mon and radosgw containers on the same host are given... Locks up charm provisioning since the containers exist but not on the right network. Bit of a show-stopper. Quincy/stable on 22.04 (both host and LXD)
2024-01-08 15:31:37 Alex Kavanagh charm-ceph-fs: status New Incomplete