Skip to content
This repository was archived by the owner on Jul 16, 2026. It is now read-only.
This repository was archived by the owner on Jul 16, 2026. It is now read-only.

On relation removal, chrony package and config are not removed as expected #70

Description

@ggouzi

Bug Description

Upon removing chrony-client relation, the charm should remove the chrony package and erased the chrony configuration is wrote itself.

https://github.com/canonical/chrony-client-operator/blob/main/src/charm.py#L65

However, this behavior does not exist.

After removing the chrony-client relation to the main app, the chrony package still exists and the chrony configuration is still present.

Workaround: apt remove chrony

Impact

Low (minor issue or cosmetic problem)

Impact Rationale

No response

To Reproduce

juju deploy ubuntu
juju deploy chrony-client
juju relate chrony-client ubuntu
juju remove-relation chrony-client ubuntu
juju ssh 0 -- cat /etc/chrony/chrony.conf
juju ssh 0 -- chronyc sources

Environment

  • Juju 3.6.24
  • chrony-client latest/stable rev 52

Relevant log output

N/A

Additional context

juju remove-relation chrony-client ubuntu
juju ssh 0 -- apt list chrony  
Listing... Done
chrony/noble-updates,now 4.5-1ubuntu4.2 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
juju ssh 0 -- ls /etc/chrony/chrony.conf
/etc/chrony/chrony.conf

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions