I am not sure if there's anything to fix here for the ntp charm. The ntp charm shouldn't really be installed in a container. In general, It should be installed alongside a principal charm that's on a bare-metal machine.
In situations like charm upgrade, The ntp charm could end up installing the chrony package again even if it's a container where it was previously removed. And ceph-mon charm could remove it again. In the case of ntp being a sub-ordinate of ceph-mon container and when ceph-mon removes chrony package, the ntp unit goes into 'blocked' state which seems reasonable to me given it shouldn't be there in the container in the firt place. So the only things I could think of are: - update ntp charm's doc that it shouldn't be installed in a container - provide a clear error message if ntp is deployed on a container Thoughts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852441 Title: In bionic, one of the ceph packages installed causes chrony to auto- install even on lxd To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-mon/+bug/1852441/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
