juju set not firing config-changed when passed a yaml file

Bug #1015645 reported by Mark Mims
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Invalid
High
Unassigned

Bug Description

Everything works fine when I

    juju set <service_name> param=value

but

    juju set <service_name> --config <yaml_file>

doesn't seem to do anything but return

    INFO 'config_set' command finished successfully

First brought up:

    http://askubuntu.com/questions/151075/what-is-the-correct-way-to-set-config-options-to-a-juju-service-unit-with-a-file

he had different ordering, but that didn't make a difference.

I tried this with a couple of different charms, but no love... can somebody please verify?

Changed in juju:
importance: Undecided → High
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

This must have been a temporary problem.. I am able to do 'juju set servicename --config path/to/yaml' and get settings changed using latest trunk.

Changed in juju:
status: New → Invalid
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.