After updating to Fedora 29, I am receiving the following error while trying to apply a template with params_from_vars:
The task includes an option with an undefined variable. The error was: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'oc_path'\n\nThe error appears to have been in '/home/jacob/Labs/industry-4.0-demo/bridge/.openshift-applier/roles/openshift-applier/roles/openshift-applier/tasks/process-template.yml': line 66, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: \"{{ oc_action | capitalize }} OpenShift objects based on template with params for '{{ entry.object}} : {{ content.name | default(template | basename) }}'\"
I have tried with both python2 and python3 with the same error.
Potentially of note is that the Retrieve oc client version step takes 1-2 seconds. Not sure how long it took to complete previously, but it seems like a step that should be nearly instantaneous.
After updating to Fedora 29, I am receiving the following error while trying to apply a template with
params_from_vars:The task includes an option with an undefined variable. The error was: 'ansible.utils.unsafe_proxy.AnsibleUnsafeText object' has no attribute 'oc_path'\n\nThe error appears to have been in '/home/jacob/Labs/industry-4.0-demo/bridge/.openshift-applier/roles/openshift-applier/roles/openshift-applier/tasks/process-template.yml': line 66, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: \"{{ oc_action | capitalize }} OpenShift objects based on template with params for '{{ entry.object}} : {{ content.name | default(template | basename) }}'\"I have tried with both python2 and python3 with the same error. Potentially of note is that the
Retrieve oc client versionstep takes 1-2 seconds. Not sure how long it took to complete previously, but it seems like a step that should be nearly instantaneous.