Fix when openstack_cacert starts with a slash

[peter-c-larsson]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:

Fix the issue that was introduced with this PR #4665 When having files starting with / causing the following error:

fatal: [kube-node-1]: FAILED! => {"msg": "The conditional check 'openstack_cacert' failed. The error was: template error while templating string: unexpected '/'. String: {% if /etc/ansible/certificate.pem %} True {% else %} False {% endif %}\n\nThe error appears to have been in '/kube-ansible/kubespray/roles/kubernetes/node/tasks/main.yml': line 186, 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: Write cacert file\n ^ here\n"}

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Discovered in the 2.10.4 branch so I guess this should be backported into that branch as well and not sure about the correct order.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Welcome @peter-c-larsson!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubespray has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: peter-c-larsson
To complete the pull request process, please assign ant31
You can assign the PR to them by writing /assign @ant31 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[alijahnas]

I also got this problem even if OS_CACERT doesn't start with /
It's some deeper problem with ansible handling string variables in conditionals which is discussed here ansible/ansible-lint#457 and here ansible/ansible#39414
The solution in this PR is still relevant and is needed to fix the bug. +1

[alijahnas]

Hello, a fix is needed in order for things to work properly. I can create a new PR if the original author can't continue the work.

[peter-c-larsson]

@alijahnas Feel free to create a new PR since I have some problem to sort out the CLA thing and close this one. Thanks in advance.