udconsumer should re-announce it's hostname to udprovider if config template-hostname is adjusted.
Bug #1895760 reported by
Drew Freiberger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
userdir-ldap-charms |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When using relation between udprovider and udconsumer, if udconsumer side of relation is using a template-hostname, it should be passed to udprovider for udprovider to link that hosts' key(s) with the template rather than the actual hostname provided from the consumer.
Currently, the udconsumer is looking for /var/cache/
The udconsumer can still request hostname.domain, but the provider should squash that to template-hostname within the sshdist user's auth-keys config.
summary: |
- when udconsumer changes hostname, reconfigure rsync/authorized_keys + When changing template-hostname, trigger relation-set toward udprovider + with new hostname |
summary: |
- When changing template-hostname, trigger relation-set toward udprovider - with new hostname + udconsumer should re-announce it's hostname to udprovider if config + template-hostname is adjusted. |
Changed in charm-userdir-ldap: | |
status: | New → Triaged |
importance: | Undecided → Low |
information type: | Proprietary → Public |
To post a comment you must log in.
Actually, this does seem to work properly, but the relation data does not properly change when config changes on the consumer side. udconsumer should re-announce it's hostname to udprovider if config template-hostname is adjusted.