Closed jonmwalton closed 3 years ago
Hi @jonmwalton, I just found this one 2 hours ago ... I think I have a Jinja templating issue but I cannot reproduce it outside a container environment to troubleshoot it for the moment. I'll let you know my findings.
This is probably due to Jinja escaping charaters ({% +%}
) that are not supported in current Operator SDK Ansible version. These characters were introduced with #53
Hey ! I've produced a new quay.io/microcks/microcks-ansible-operator:1.4.1
container image version. Could you check on your side?
Hey ! I've produced a new
quay.io/microcks/microcks-ansible-operator:1.4.1
container image version. Could you check on your side?
Will it be available in the OperatorHub of Openshift? Not sure how I will be able to test if it isn't.
Yes the image has been patched. You should just ensure to kill your operator pod to force re-pulling the image.
It's working fine again. Thanks for fixing so quickly!!
Since v1.4.1 the operator now fails to install a vanilla MicrocksInstall CRD. Most of the components get deployed except for the actual console. The error can be seen in the attached log. microcks-ansible-operator-68f54b6bcd-d6vhx-microcks-ansible-operator.log