snappy config command does not restart service after setting the configuration

Bug #1484641 reported by Simon Eisenmann on 2015-08-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

The docs for snappy config command at says: "When the configuration is applied the service will be restarted by snappy automatically."

Though the service does not get restarted. Spreed WebRTC just got a configuration and then it is applied with `snappy config spreed-webrtc /tmp/spreed-webrtc.yaml` the service is not restarted by snappy.

To test yourself with spreed-webrtc (on armhf):

sudo snappy install spreed-webrtc
sudo snappy config spreed-webrtc > /tmp/spreed-webrtc.yaml
# Now modify something (eg the ports)
sudo vi /tmp/spreed-webrtc.yaml
sudo snappy config spreed-webrtc /tmp/spreed-webrtc.yaml

This is problematic, as there is no way to restart a snap provided service easily when you just know the name of the snap. One needs to know the systemd service name which is complicated.

Michael Vogt (mvo) on 2015-08-24
Changed in snappy:
status: New → Triaged
importance: Undecided → High
Chad Miller (cmiller) wrote :

Within new configuration hook, this may could be

snapctl reload appnameinyaml

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers