Re: Sudden issues with pki role
The role not working was a python related issue, the solution is
to edit lines 92 and 93 of
/home/username/.local/share/debops/debops/ansible/roles/cron/tasks/main.yml
as follows:
my_dict.keys()[0]
This syntax is not valid anymore with Python 3.
The correct Python3/Jinja2 syntax is:
my_dict.keys()|list|first
source:
https://github.com/nmasse-itix/threescale-cicd/issues/33#issuecomment-451...
On 14-09-2020 13:34, Jason van der Leeuw wrote:
Hi,
I just noticed that the pki config on a server got skewed. Our pki
config has always worked fine. On trying to run it now with
$ debops -v service/pki -l affected.server
I get:
===================
TASK [cron : Manage cron environment variables] *
fatal: [server.name]: FAILED! =>
msg: |-
The task includes an option with an undefined variable. The error
was: dict_keys object has no element 0
The error appears to be in
'/home/username/.local/share/debops/debops/ansible/roles/cron/tasks/main.yml':
line 89, column 3, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
- name: Manage cron environment variables
^ here
===================
But obviously I have never edited this file.
To test another role, I tried running the service/nginx role, which
finishes fine. How do I get the pki role working again? Any suggestion
is welcome.
Jason