Charm ignores config-changed after registration ran successful

Bug #1805169 reported by Pedro Guimarães
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
landscape-client-charm
Triaged
Medium
Unassigned

Bug Description

Once charm has received correct registration_key and successfully registered with landscape-server, any further config changes via "juju config" are ignored, although client.conf is correctly updated. Restarting the service landscape-client sets it to work with new config.

Charm should run service restart on config-changed hook, for any changes made.

Tags: field-medium
Revision history for this message
Narinder Gupta (narindergupta) wrote :

FCE team is facing the same problem on all deployments.
juju run --application landscape-client 'sudo systemctl restart landscape-client.service'

fixes it but charm should be updated to restart the service after config change.

tags: added: field-medium
Revision history for this message
David Coronel (davecore) wrote :

This is still an issue with the upstream cs:landscape-client-31 charm.

The landscape-client charm should restart the landscape client service on config-changed hook for any changes made.

Simon Poirier (simpoir)
Changed in landscape-client-charm:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.