[BUG] Re-running changes on upstream repo

[ulvida]

Describe the bug
Using a copy of upstream master branch, the role fails saying:

TASK [sympa : Create a new database with name 'sympa'] *****************************************************************************************************************************************************
task path: /home/ulvida/tech/interior/UdelaRInterior/sympa/tasks/main.yml:23
fatal: [cazuela.interior.edu.uy]: FAILED! => {"changed": false, "msg": "The PyMySQL (Python 2.7 and Python 3.X) or MySQL-python (Python 2.X) module is required."}

To Reproduce

Ran with a controller on ubuntu 18 and an LXC on proxmox with debian stretch on the remote server.

Expected behavior

Probably is just a dependency to check.

I'll work on branch python-mysql

[ulvida]

In fact, the upstream role requires mysql installed and, if this is done with an ansible role, pymysql will be then be installed. However, as far as there is no dependency set, we could check it here.

[ulvida]

Sorting this first problem (adding this role before, when I run sympa role, it fails with (among other errors):

"head: cannot open '/etc/mailname' for reading: No such file or directory" 

Explorigng, this comes from the fact that I'm using a Proxmox LXC container, with is not a "pure" debian stretch, and it has not this file, which is supposed to be there by default.

[ulvida]

After solving precedent container bug, I come to a bug in the upstream role itself. Installation sympa task fails with:

        "Sympa configuration already located at /etc/sympa/sympa/sympa.conf", 
        "Upgrading Sympa internals (health check)", 
        "err Conf::_load_config_file_to_hash() Error at line 331: /etc/sympa/sympa/sympa.conf", 
        "err Conf::load() Errors while parsing main config file /etc/sympa/sympa/sympa.conf", 
        "Configuration file /etc/sympa/sympa/sympa.conf has errors.", 
        "dpkg: error processing package sympa (--configure):", 
        " subprocess installed post-installation script returned error exit status 255", 

[ulvida]

Line 331 was:

## dkim_selector
## The selector
dkim_selector

Indeed, the definition of a DKIM selector is needed

[ulvida]

PR was accepted and merged to the upstream code. Let's close this issue.