Updating tags after deployment updates /etc/landscape/client.conf on deployed units, but tags are not applied to the corresponding records in Landscape

Bug #1924595 reported by Paul Goins
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
landscape-client-charm
New
Undecided
Unassigned

Bug Description

I wanted to add a tag to an already-deployed environment to the landscape-client config, and was hoping for that to update the tags of all machines managed by that charm.

It looks like while the tags field does get created in /etc/landscape/client.conf after making such an update, however the actual computer records in landscape don't receive updated tags.

Do we want to support that type of usage? If so, this needs to be fixed I think; and if not (perhaps because of not wanting to overwrite user-applied tags), we may want to document such in config.yaml's description of the tags field.

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.