ansible issueshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues2020-05-15T09:54:00+02:00https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/75Replace bwSync&Share with Nextcloud2020-05-15T09:54:00+02:00sg7149Replace bwSync&Share with NextcloudHost: lasXXX.las.kit.edu
OS: Fedora XX
Software name:
--------------
Nextcloud client for KIT's bwSync&Share
Date:
------
End of 2019
Software installation instruction if not in repos:
------------------------------------------------...Host: lasXXX.las.kit.edu
OS: Fedora XX
Software name:
--------------
Nextcloud client for KIT's bwSync&Share
Date:
------
End of 2019
Software installation instruction if not in repos:
--------------------------------------------------
Maybe at https://nextcloud.com/de/install/#install-clients with the URL: https://bwsyncandshare.kit.edu
Possibly also interesting for:
-------------------------------
http://help.bwsyncandshare.kit.edu/134.php
/cc @project-managerlp5884lp5884https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/95lasarchiv1 role fails sometimes2020-05-14T18:00:01+02:00sg7149lasarchiv1 role fails sometimesCalling host: obelix.las.kit.edu (Fedora 31)
Failing nodes: pepe, faulus
Summary
-------
Running the newly merged code !43 it first failed for some hosts, but not for all.
After having a look at https://github.com/ansible/ansible/issu...Calling host: obelix.las.kit.edu (Fedora 31)
Failing nodes: pepe, faulus
Summary
-------
Running the newly merged code !43 it first failed for some hosts, but not for all.
After having a look at https://github.com/ansible/ansible/issues/29814 and changing `remounted` to `mounted` again succeeded.
But `mounted` initially failed, so maybe it is the bug and we cannot do much about it in our role. From the github-issue, I understand the documentation like it should work with `mounted` which is more consistent with the idea of stateless-ness though I read the documentation of the `mount` module differently the last time.
Steps to reproduce
------------------
Run `ansible-playbook --vault-password-file password nfs.yml --skip-tags fonts`.
What is the current bug behavior?
---------------------------------
SOMETIMES:
Hosts with unmounted /mnt/las-archiv1 and not installed fail. Broken, and correctly mounted /mnt/las-archiv1 machines do not fail.
What is the expected correct behaviour?
---------------------------------------
ALWAYS: None of the machines fail and all have a mounted /mnt/las-archiv1
Relevant logs and/or screenshots
--------------------------------
```
TASK [lasarchiv : remount lasarchiv1] ********************************************************************************
fatal: [homoeopatix.las.kit.edu]: FAILED! => {"changed": false, "msg": "Error remounting /mnt/las-archiv1: umount: /mnt/las-archiv1: not mounted.\n"}
changed: [methusalix.las.kit.edu]
changed: [majestix.las.kit.edu]
changed: [troubadix.las.kit.edu]
fatal: [faulus.las.kit.edu]: FAILED! => {"changed": false, "msg": "Error remounting /mnt/las-archiv1: umount: /mnt/las-archiv1: no mount point specified.\n"}
fatal: [pepe.las.kit.edu]: FAILED! => {"changed": false, "msg": "Error remounting /mnt/las-archiv1: umount: /mnt/las-archiv1: not mounted.\n"}
changed: [idefix.las.kit.edu]
```
https://github.com/ansible/ansible/issues/29814
Possible fixes
--------------
(If you can, link to the line of code that might be responsible for the problem)
/cc @vn4918https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/91Add networking to common role2020-05-13T12:10:22+02:00sg7149Add networking to common roleAdd some basic networking setup to the common role (maybe via nmcli-module)
* [ ] DNS v4, v6
* [ ] Default gateway v4 v6
* [x] Hostname
* [ ] dhclient on start
* [ ] auto negotiationAdd some basic networking setup to the common role (maybe via nmcli-module)
* [ ] DNS v4, v6
* [ ] Default gateway v4 v6
* [x] Hostname
* [ ] dhclient on start
* [ ] auto negotiationhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/92ansible ipv6 vs root2020-05-13T10:44:29+02:00sg7149ansible ipv6 vs rootansible tries to use IPv6 now that our hosts have proper DNS for IPv6.
Unfortunately the SSH-key for root only allows the IPv4 of obelix, so that running ansible fail atm.
One should either change the SSH-allowed IP addresses.
Or one sh...ansible tries to use IPv6 now that our hosts have proper DNS for IPv6.
Unfortunately the SSH-key for root only allows the IPv4 of obelix, so that running ansible fail atm.
One should either change the SSH-allowed IP addresses.
Or one should force ansible to use IPv4 only.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/5IPA-setup2020-05-04T12:34:48+02:00sg7149IPA-setupIPA setup in ansibleIPA setup in ansiblehttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/4ansible-pull2020-05-04T12:33:50+02:00sg7149ansible-pullUpdate documentation on ansible-pullUpdate documentation on ansible-pullsg7149sg7149https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/22Run ansible as root with certificats2020-05-04T12:32:11+02:00sg7149Run ansible as root with certificatsRun ansible as root to avoid sudo-timeouts on slow hard disks.
* [x] certificate for root on one host
* [x] root login via ssh
* [ ] edit tasks not to use become any longer?Run ansible as root to avoid sudo-timeouts on slow hard disks.
* [x] certificate for root on one host
* [x] root login via ssh
* [ ] edit tasks not to use become any longer?https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/32sshd template causes error2020-05-04T12:30:17+02:00sg7149sshd template causes errorCalling host: las113.las.kit.edu (Fedora 27)
Failing nodes: localhost -i local
Summary
-------
ansible fails with an error message in the firewalld role complaining about syntax errors.
Steps to reproduce
------------------
run `an...Calling host: las113.las.kit.edu (Fedora 27)
Failing nodes: localhost -i local
Summary
-------
ansible fails with an error message in the firewalld role complaining about syntax errors.
Steps to reproduce
------------------
run `ansible-playbook latex.yml -l localhost --vault-id @prompt -K -i local`
What is the current bug behavior?
---------------------------------
fails with an error on my Fedora 27. Might work on Fedora 28.
What is the expected correct behaviour?
---------------------------------------
continue and install a proper sshd config
Relevant logs and/or screenshots
--------------------------------
```
TASK [common : install firewalld] ******************************************************
fatal: [127.0.0.1]: FAILED! => {"msg": "The conditional check '((ansible_distribution == \"Fedora\" and ansible_distribution_major_version < 28) or (ansible_distribution == \"CentOS\" and ansible_distribution_major_version >= 7))' failed. The error was: Unexpected templating type error occurred on ({% if ((ansible_distribution == \"Fedora\" and ansible_distribution_major_version < 28) or (ansible_distribution == \"CentOS\" and ansible_distribution_major_version >= 7)) %} True {% else %} False {% endif %}): '<' not supported between instances of 'AnsibleUnsafeText' and 'int'\n\nThe error appears to have been in '/home/gethmann/ansible/ansible/roles/common/tasks/sshd.yml': line 8, 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: install firewalld\n ^ here\n"}
```
Possible fixes
--------------
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/65script to add ipa-replica to dns2020-05-04T12:21:08+02:00sg7149script to add ipa-replica to dnsScript the change of the DNS entries for a new IPA replica.
Add the SRV entries to DNSVS
See [IPA docu](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide...Script the change of the DNS entries for a new IPA replica.
Add the SRV entries to DNSVS
See [IPA docu](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/creating-the-replica) and the [NETVS docu](https://www-net-doku.scc.kit.edu/webapi/release/intro/)
```
_ldap._tcp
_kerberos._tcp
_kerberos._udp
_kerberos-master._tcp
_kerberos-master._udp
_ntp._udp
_kpasswd._tcp
_kpasswd._udp
```Network movehttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/70integrate ipa-healthcheck into munin2020-05-04T12:19:48+02:00sg7149integrate ipa-healthcheck into muninIntegrate the very new ipa-healthcheck tool into munin and/or a warning system, so one gets informed when a system fails.
Caution: one probably should take care of nodes that go down expectedly, because they run on clients.Integrate the very new ipa-healthcheck tool into munin and/or a warning system, so one gets informed when a system fails.
Caution: one probably should take care of nodes that go down expectedly, because they run on clients.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/89Add fix to missing users at CN login screen2020-03-03T14:43:07+01:00sg7149Add fix to missing users at CN login screenFailing nodes: nichtsalsverdrus (Fedora LXQt)
Summary
-------
Users with UIDs of the IPA range and not the typical Linux user range (1000+) weren't shown in the login screen and one cannot type a user name either.
Steps to reproduce
...Failing nodes: nichtsalsverdrus (Fedora LXQt)
Summary
-------
Users with UIDs of the IPA range and not the typical Linux user range (1000+) weren't shown in the login screen and one cannot type a user name either.
Steps to reproduce
------------------
Log out and have a look at the login screen of the LXQt (SDDM) Fedora.
What is the current bug behavior?
---------------------------------
No users shown with too large UID (until workaround)
What is the expected correct behaviour?
---------------------------------------
All users selectable as login users.
Possible fixes
--------------
Fixed it (but not in ansible and not with a good upper limit, but only a value that is larger than the largest UID that is in use and small enough to show users.
If the UID is too large no user is shown at all.
In the `/etc/sddm.conf` one has to add the following lines:
```
HideUsers=nfsnobody
MaximumUid=1911111111
```
and restart sddm/Xorg.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/85Opera on Fedora 312020-03-02T14:52:39+01:00sg7149Opera on Fedora 31To work around Opera not starting on Fedora 31 I linked the libhwloc.so.5->libhwloc.so.15.
Maybe one should also copy libhwloc.so.5 from CentOS7 (kantine) instead of linking the new one.
Probably also the new Opera 2020 will not depend ...To work around Opera not starting on Fedora 31 I linked the libhwloc.so.5->libhwloc.so.15.
Maybe one should also copy libhwloc.so.5 from CentOS7 (kantine) instead of linking the new one.
Probably also the new Opera 2020 will not depend on libhwloc.so.15, because their webpage claims to support RHEL7, but not RHEL8 and even RHEL8 seems to have libhwloc.so.5 instead of .15.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/88SDDM not showing users2020-03-01T01:10:33+01:00sg7149SDDM not showing usersOnly the installation (local) user is displayed at the login screen.
[My documentation](https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/systemdocu/-/blob/master/ipa/freeipa.md#sddmlogin-manager)
suggests, that ...Only the installation (local) user is displayed at the login screen.
[My documentation](https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/systemdocu/-/blob/master/ipa/freeipa.md#sddmlogin-manager)
suggests, that it might help to add the network as a dependency to the sddm.service
```
SDDM/Login-Manager
In the case that KDE’s default login manager SDDM does not show any accounts to select for logging in, the following might help: Copy sddm.service from /lib/systemd/system to /etc/systemd/system, and add a line After=network.target to the [Unit] section.
```
Implement it as part of the ipa-hosts role.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/54Unable to login via sddm2020-03-01T01:07:22+01:00sg7149Unable to login via sddmFailing nodes: las115
Summary
-------
One IPA only user cannot login via the login-manager sddm, but needs to login via the terminal and then `startx` by hand.
Steps to reproduce
------------------
Boot las115, try to login with a p...Failing nodes: las115
Summary
-------
One IPA only user cannot login via the login-manager sddm, but needs to login via the terminal and then `startx` by hand.
Steps to reproduce
------------------
Boot las115, try to login with a pure IPA user.
What is the current bug behavior?
---------------------------------
KDE Plasma does not start
What is the expected correct behaviour?
---------------------------------------
KDE Plasma starts.
Relevant logs and/or screenshots
--------------------------------
TODO
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/76Create role for TGU experimental computer2020-02-29T23:58:13+01:00sg7149Create role for TGU experimental computer* [ ] docu https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/systemdocu/blob/master/setup-tgu-coputer.md
* [ ] service files/timer docu
* [x] /home/messuser/README
* [ ] /etc/systemd/system/...
* [ ] ~/.ssh/...
* [...* [ ] docu https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/systemdocu/blob/master/setup-tgu-coputer.md
* [ ] service files/timer docu
* [x] /home/messuser/README
* [ ] /etc/systemd/system/...
* [ ] ~/.ssh/...
* [ ] git checkout of all repos
* [ ] add users
* [ ] network confighttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/83LASMagLab DHCPd with template instead of static file2020-02-29T23:16:35+01:00sg7149LASMagLab DHCPd with template instead of static fileOne might want to use a template for the DHCPd server entry in the `dhcpd.conf`, so that one does not have to change it for a new computer.
Hints/Ideas for the template:
* MAC address: ('ansible_interfaces' starts with 'enp') ['ansible_...One might want to use a template for the DHCPd server entry in the `dhcpd.conf`, so that one does not have to change it for a new computer.
Hints/Ideas for the template:
* MAC address: ('ansible_interfaces' starts with 'enp') ['ansible_enp????']['macaddress'] when ['ansible_enp???']['ipv4']['network'] == '192.168.0.0'
* Hostname: ['ansible_fqdn']
* IP: '192.168.0.1'
```
# DHCPd host
host {{'ansible_hostname'}} {
hardware ethernet {{ macaddress }};
fixed-address {{ ip }};
}
```https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/26EPICS_CA_ADDR_LIST hard is coded2020-02-24T17:39:28+01:00sg7149EPICS_CA_ADDR_LIST hard is codedCalling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las115
Summary
-------
Because the EPICS_CA_ADDR_LIST is hard coded for KARA in the `profile.d` file it is not practical for the Jena/TGU setup.
What is the current bug beh...Calling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las115
Summary
-------
Because the EPICS_CA_ADDR_LIST is hard coded for KARA in the `profile.d` file it is not practical for the Jena/TGU setup.
What is the current bug behavior?
---------------------------------
The environment variable `EPICS_CA_ADDR_LIST` is set to a server that is responsible for the KARA PVs, but not depending on the use-case for KARA, FLUTE or JENA/TGU.
What is the expected correct behaviour?
---------------------------------------
The variable should be like it is for a KARA role, and different or not set for a JENA/TGU role.
Iff it is not set, it should be noted in the docu and as a `msg`.
Possible fixes
--------------
Create a role for KARA/CSS and a role for Jena/TGU control system and one without it being set.
/cc @project-managerhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/28firewalld not working on Fedora 282020-02-24T17:37:09+01:00sg7149firewalld not working on Fedora 28Calling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las118
Summary
-------
All rules that work with the `firewalld` module do not work with Fedora 28, because the firewalld module depends on `python-firewalld` and does not wor...Calling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las118
Summary
-------
All rules that work with the `firewalld` module do not work with Fedora 28, because the firewalld module depends on `python-firewalld` and does not work with `python3-firewalld` as partly documented in the [documentation](https://docs.ansible.com/ansible/latest/modules/firewalld_module.html)
Steps to reproduce
------------------
Try to run the sshd task of the common role
What is the current bug behavior?
---------------------------------
The role stops at task `common : Open port 22 on Fedora/CentOS`
What is the expected correct behaviour?
---------------------------------------
The role common runs and the firewall opens port 22 for ssh.
Relevant logs and/or screenshots
--------------------------------
```
fatal: [las118.las.kit.edu]: FAILED! => {
"changed": false,
"module_stderr": "OpenSSH_7.6p1, OpenSSL 1.1.0h-fips 27 Mar 2018\r\ndebug1: Reading configuration data /home/gethmann/.ssh/config\r\ndebug1: /home/gethmann/.ssh/config line 124: Applying options for *\r\ndebug1: /home/gethmann/.ssh/config line 128: Deprecated option \"useroaming\"\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug3: /etc/ssh/ssh_config line 52: Including file /etc/ssh/ssh_config.d/05-redhat.conf depth 0\r\ndebug1: Reading configuration data /etc/ssh/ssh_config.d/05-redhat.conf\r\ndebug3: /etc/ssh/ssh_config.d/05-redhat.conf line 2: Including file /etc/crypto-policies/back-ends/openssh.config depth 1\r\ndebug1: Reading configuration data /etc/crypto-policies/back-ends/openssh.config\r\ndebug3: gss kex names ok: [gss-gex-sha1-,gss-group14-sha1-]\r\ndebug3: kex names ok: [curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1]\r\ndebug1: /etc/ssh/ssh_config.d/05-redhat.conf line 8: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 4 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 25187\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 1\r\nShared connection to las118.las.kit.edu closed.\r\n",
"module_stdout": "\r\nTraceback (most recent call last):\r\n File \"/tmp/ansible_VyTTtl/ansible_module_firewalld.py\", line 1017, in <module>\r\n main()\r\n File \"/tmp/ansible_VyTTtl/ansible_module_firewalld.py\", line 811, in main\r\n if fw_offline:\r\nNameError: global name 'fw_offline' is not defined\r\n",
"msg": "MODULE FAILURE",
"rc": 1
}
```
Possible fixes
--------------
Search for other ways (iptables) to open the port. Just as a work-around till Python 3 is supported.
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/31DHCPd on Ubuntu validation fails2020-02-24T17:34:58+01:00sg7149DHCPd on Ubuntu validation failsCalling host: las126.las.kit.edu (Fedora 27)
Failing nodes: las93
Summary
-------
The validation of the DHCPd config fails on Ubuntu (Lab computer).
There is at least one person experiencing the same issue,
https://superuser.com/quest...Calling host: las126.las.kit.edu (Fedora 27)
Failing nodes: las93
Summary
-------
The validation of the DHCPd config fails on Ubuntu (Lab computer).
There is at least one person experiencing the same issue,
https://superuser.com/questions/1286948/ansible-template-validation-fails-on-isc-dhcp-server , but no answer so far.
The file is not copied and the task aborts.
Steps to reproduce
------------------
Run the lab role with `validate: "{{ bin_path }} -t -cf %s"` activated.
What is the current bug behavior?
---------------------------------
The role fails and the files `host-list-maglab` and `dhcpd.conf` are not copied to the node.
What is the expected correct behaviour?
---------------------------------------
The task succeeds and the dhcpd.conf and the decrypted host-list-maglab file are at the node.
Relevant logs and/or screenshots
--------------------------------
```
failed: [las93.las.kit.edu] (item=maglab.hosts) => {"changed": false, "checksum": "6ba7f7faa00e05e763266888a31054cc20a58909", "exit_status": 1, "item": "maglab.hosts", "msg": "failed to validate", "stderr": "Internet Systems Consortium DHCP Server 4.2.4\nCopyright 2004-2012 Internet Systems Consortium.\nAll rights reserved.\nFor info, please visit https://www.isc.org/software/dhcp/\nCan't open /root/.ansible/tmp/ansible-tmp-1528358315.88-158600528943595/source: Permission denied\n", "stderr_lines": ["Internet Systems Consortium DHCP Server 4.2.4", "Copyright 2004-2012 Internet Systems Consortium.", "All rights reserved.", "For info, please visit https://www.isc.org/software/dhcp/", "Can't open /root/.ansible/tmp/ansible-tmp-1528358315.88-158600528943595/source: Permission denied"], "stdout": "", "stdout_lines": []}
failed: [las93.las.kit.edu] (item=dhcpd.conf) => {"changed": false, "checksum": "c8f8782d9486025107e622108f35cbea7f6da629", "exit_status": 1, "item": "dhcpd.conf", "msg": "failed to validate", "stderr": "Internet Systems Consortium DHCP Server 4.2.4\nCopyright 2004-2012 Internet Systems Consortium.\nAll rights reserved.\nFor info, please visit https://www.isc.org/software/dhcp/\nCan't open /root/.ansible/tmp/ansible-tmp-1528358317.34-230984934434610/source: Permission denied\n", "stderr_lines": ["Internet Systems Consortium DHCP Server 4.2.4", "Copyright 2004-2012 Internet Systems Consortium.", "All rights reserved.", "For info, please visit https://www.isc.org/software/dhcp/", "Can't open /root/.ansible/tmp/ansible-tmp-1528358317.34-230984934434610/source: Permission denied"], "stdout": "", "stdout_lines": []}
```
Possible fixes
--------------
Work around: Check the validity at your own host and don't use the validity check on the node.
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/69ssmtp fails every second time2020-02-24T17:29:24+01:00sg7149ssmtp fails every second timeCalling host: asterix.las.kit.edu (Fedora 30)
Failing nodes: asterix
Summary
-------
Every second time I run ansible-playbook sites.yml it fails at ssmtp rule
Steps to reproduce
------------------
run ansible twice
What is the c...Calling host: asterix.las.kit.edu (Fedora 30)
Failing nodes: asterix
Summary
-------
Every second time I run ansible-playbook sites.yml it fails at ssmtp rule
Steps to reproduce
------------------
run ansible twice
What is the current bug behavior?
---------------------------------
fails every second time
What is the expected correct behaviour?
---------------------------------------
does not fail
Relevant logs and/or screenshots
--------------------------------
```
[mail : install ssmtp and mailx] *******************************************************************************************************************************************************************************************************
failed: [asterix.las.kit.edu] (item=ssmtp) => {"ansible_loop_var": "item", "changed": false, "item": "ssmtp", "module_stderr": "/root/.ansible/tmp/ansible-tmp-1560283437.0299356-2401896733455/AnsiballZ_dnf.py:18: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses\n import imp\n", "module_stdout": "[master 1debf86] saving uncommitted changes in /etc prior to dnf run\n 1 file changed, 2 insertions(+)\n\n{\"msg\": \"Nothing to do\", \"changed\": false, \"results\": [\"Installed: ssmtp\"], \"rc\": 0, \"invocation\": {\"module_args\": {\"name\": [\"ssmtp\"], \"state\": \"present\", \"allow_downgrade\": false, \"autoremove\": false, \"bugfix\": false, \"disable_gpg_check\": false, \"disable_plugin\": [], \"disablerepo\": [], \"download_only\": false, \"enable_plugin\": [], \"enablerepo\": [], \"exclude\": [], \"installroot\": \"/\", \"install_repoquery\": true, \"install_weak_deps\": true, \"security\": false, \"skip_broken\": false, \"update_cache\": false, \"update_only\": false, \"validate_certs\": true, \"lock_timeout\": 0, \"conf_file\": null, \"disable_excludes\": null, \"download_dir\": null, \"list\": null, \"releasever\": null}}}\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 0}
```
Possible fixes
--------------
(If you can, link to the line of code that might be responsible for the problem)
/cc @gethmann