Walter - Unfortunately I can't provide the code as this is on a client's off-line network. Todd, I'll look again at when I use the chrony tasks.
On Thursday, October 26, 2023 at 9:32:36 AM UTC-4 Todd Lewis wrote: > Hi Kathy, > > Files, templates, plugins, etc. that live in various local roles aren't > available to your playbook tasks until those roles are accessed, for > example through the roles: playbook keyword or import_role or include_role > . > > From your description, it appears that you've accessed your yum role but > not your chrony role at the point you tried to use your etc.chrony.conf.j2 > template. > -- > Todd > > > On 10/26/23 7:22 AM, Kathy L wrote: > > Good morning. I have two roles in a multi-role playbook, for yum, then > chrony. The yum module works fine, but the chrony playbook fails on copying > a template. The odd thing is, the error I get indicates ansible is looking > in the yum module for chrony's template. here is the specific error > message; > > Could not find or access chrony.conf.j2 > Searched in: > /work/roles/yum/templates/chrony.conf.j2 > /work/roles/yum/chrony.conf.j2 > /work/roles/yum/tasks/chrony.conf.j2 > /work/templates/etc.chrony.conf.j2 > > Why is it searching in the yum role for a chrony template? The template > is in /work/roles/chrony/templates/chrony.conf.j2. > > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/efe73dbf-7f61-4a5e-88dc-97cfd22824c2n%40googlegroups.com.
