ansible issueshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues2020-02-24T17:27:11+01:00https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/63Fix died las1012020-02-24T17:27:11+01:00sg7149Fix died las101las101 did not come up again after reboot.
fsck fails and Ctrl+d does not work to get a prompt, yet.las101 did not come up again after reboot.
fsck fails and Ctrl+d does not work to get a prompt, yet.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/46Jabref missing on Fedora 292019-01-16T09:51:07+01:00sg7149Jabref missing on Fedora 29Fedora 29 does not provide jabref.
There is a package called jabref, but its dependency on `jempbox` is not fulfilled.
There are also known upstream bugs, blocking the current versions of jabref to work under Fedora 29:
https://help.jab...Fedora 29 does not provide jabref.
There is a package called jabref, but its dependency on `jempbox` is not fulfilled.
There are also known upstream bugs, blocking the current versions of jabref to work under Fedora 29:
https://help.jabref.org/en/Installation#fedora-and-openjdk
https://bugzilla.redhat.com/show_bug.cgi?id=1644712
https://github.com/JabRef/jabref/issues/4473https://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/6nfs-server2018-06-07T15:49:47+02:00sg7149nfs-serverImplement rule for
* nfs-server
* lasarchiv1Implement rule for
* nfs-server
* lasarchiv1https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/108Opera installation failing when GNOME group should be installed2021-09-03T14:12:42+02:00sg7149Opera installation failing when GNOME group should be installedCalling host: asterix.las.kit.edu (Fedora 32)
Failing nodes: asterix
Summary
-------
Running the Opera role fails when trying to install GNOME group. It seems that the group was renamed.
Steps to reproduce
------------------
Try to...Calling host: asterix.las.kit.edu (Fedora 32)
Failing nodes: asterix
Summary
-------
Running the Opera role fails when trying to install GNOME group. It seems that the group was renamed.
Steps to reproduce
------------------
Try to install opera via the ansible role on Fedora 32 (GNOME may already be installed).
What is the current bug behavior?
---------------------------------
Fails when trying to group install "@GNOME".
What is the expected correct behaviour?
---------------------------------------
The GNOME group is installed and Opera installation succeeds.
Relevant logs and/or screenshots
--------------------------------
```
TASK [opera : install dependencies] ********************************************************************************************************************************************************************************************************
fatal: [asterix.las.kit.edu]: FAILED! => {"changed": false, "msg": "No group GNOME available.", "results": []}
```
Possible fixes
--------------
Use the correct name for the GNOME group.zx8344samira.fatehi@kit.eduzx8344samira.fatehi@kit.eduhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/106Opera 2020 on Fedora 332022-06-29T11:45:44+02:00sg7149Opera 2020 on Fedora 33Failing nodes: methusalix, idefix
Summary
-------
Running operafea-post fails with errors.
Steps to reproduce
------------------
(How one can reproduce the issue - this is very important)
What is the current bug behavior?
--------...Failing nodes: methusalix, idefix
Summary
-------
Running operafea-post fails with errors.
Steps to reproduce
------------------
(How one can reproduce the issue - this is very important)
What is the current bug behavior?
---------------------------------
(What actually happens)
What is the expected correct behaviour?
---------------------------------------
(What you should see instead)
Relevant logs and/or screenshots
--------------------------------
```
/usr/local/share/Opera_2020/code/bin/operafea-post
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib64/dri)
libGL error: failed to load driver: swrast
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libifcoremt.so.5 00007F2EBD00F522 for__signal_handl Unknown Unknown
libpthread-2.32.s 00007F2EB68CE1E0 Unknown Unknown Unknown
libQt5OpenGL.so.5 00007F2EB90663E1 _ZN9QGLFormat18op Unknown Unknown
operafea-post 00005625BA7193E0 Unknown Unknown Unknown
operafea-post 00005625BA719D9B Unknown Unknown Unknown
operafea-post 00005625BA7191A3 Unknown Unknown Unknown
operafea-post 00005625BA718069 Unknown Unknown Unknown
operafea-post 00005625B9DBCFED Unknown Unknown Unknown
operafea-post 00005625BA4A2148 Unknown Unknown Unknown
operafea-post 00005625B9DFE281 Unknown Unknown Unknown
libc-2.32.so 00007F2EB34BD1E2 __libc_start_main Unknown Unknown
operafea-post 00005625B9DB7AF9 Unknown Unknown Unknown
```
Possible fixes
--------------
Tried installing `libglvnd-opengl` to provide `/lib64/libOpenGL.so.0.0.0` which was missing, but was on a working Fedora 31 host.ue5734ue5734https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/93teamviewer installation stopps updates2020-08-17T09:57:29+02:00sg7149teamviewer installation stopps updatesCalling host: obelix.las.kit.edu (Fedora 31)
Failing nodes: pepe, asterix
Summary
-------
Updates fail, because teamviewer repo cannot be found
Steps to reproduce
------------------
enable the teamviewer repositories () and run `dn...Calling host: obelix.las.kit.edu (Fedora 31)
Failing nodes: pepe, asterix
Summary
-------
Updates fail, because teamviewer repo cannot be found
Steps to reproduce
------------------
enable the teamviewer repositories () and run `dnf update`
What is the current bug behavior?
---------------------------------
```
Failed to synchronize cache for repo 'tvinternal_dev'
Ignoring repositories: tvinternal_dev
```
when running via ansible, it fails due to timeouts.
What is the expected correct behaviour?
---------------------------------------
Update runs without any problems.
Relevant logs and/or screenshots
--------------------------------
```
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
```
Possible fixes
--------------
As a workaround one can deactivate the repository, but then teamviewer will not get updates!
/cc @vn4918lp5884lp5884https://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/80VGA-port @ ThinkCentres2020-02-17T15:54:47+01:00sg7149VGA-port @ ThinkCentresThe VGA-port on ThinkCentres seems to misbehave on Linux.
ThinkCentres (new M920t) with VGA connected to a VGA-Display boots and when switching to a higher resolution during booting (the monitor searches for signal and turns off).
Durin...The VGA-port on ThinkCentres seems to misbehave on Linux.
ThinkCentres (new M920t) with VGA connected to a VGA-Display boots and when switching to a higher resolution during booting (the monitor searches for signal and turns off).
During installation with KDE-Live-System it was possible to switch to a non-graphical console (ctrl+alt+2) and to login there and reboot (killing X did not help).
Probably it's possible to fix it with the right boot-flags.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/74MS fonts2019-10-28T18:15:54+01:00sg7149MS fontsCalling host: obelix.las.kit.edu (Fedora 30)
Failing nodes: asterix, obelix
Summary
-------
MS fonts installation (client role) fails, because of certificate issues of sf.net
Steps to reproduce
------------------
Run client role
...Calling host: obelix.las.kit.edu (Fedora 30)
Failing nodes: asterix, obelix
Summary
-------
MS fonts installation (client role) fails, because of certificate issues of sf.net
Steps to reproduce
------------------
Run client role
What is the current bug behavior?
---------------------------------
Client role fails when reaching the MS fonts task
What is the expected correct behaviour?
---------------------------------------
MS fonst install
Relevant logs and/or screenshots
--------------------------------
```
TASK [clients : install fonts] **************************************************************************************************************************************************************************************************************
fatal: [asterix.las.kit.edu]: FAILED! => {"changed": false, "msg": "Failed to validate the SSL certificate for kent.dl.sourceforge.net:443. Make sure your managed systems have a valid CA certificate installed. You can use validate_certs=
False if you do not need to confirm the servers identity but this is unsafe and not recommended. Paths checked for this platform: /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs, /usr/share/ca-certificates/cacert.org,
/etc/ansible. The exception msg was: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1076).", "status": -1, "url": "https://kent.dl.sourceforge.net/project/mscorefonts2/rpms/msttcore-fonts-ins
taller-2.6-1.noarch.rpm"} ```
Possible fixes
--------------
(If you can, link to the line of code that might be responsible for the problem)
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/72Fix munin2019-08-28T14:46:52+02:00sg7149Fix muninMunin does not provide proper graphs for the clients (asterix: empty graphs, obelix: broken graphics)Munin does not provide proper graphs for the clients (asterix: empty graphs, obelix: broken graphics)https://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 @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/68deprecation: TRANSFORM_INVALID_GROUP_CHARS2020-02-24T17:24:49+01:00sg7149deprecation: TRANSFORM_INVALID_GROUP_CHARSCalling host: obelix.las.kit.edu (Fedora 29)
Failing nodes: asterix (Fedora 30)
Summary
-------
Deprecation warning
Steps to reproduce
------------------
sites.yml
What is the current bug behavior?
-------------------------------...Calling host: obelix.las.kit.edu (Fedora 29)
Failing nodes: asterix (Fedora 30)
Summary
-------
Deprecation warning
Steps to reproduce
------------------
sites.yml
What is the current bug behavior?
---------------------------------
deprecation warning
What is the expected correct behaviour?
---------------------------------------
no warning
Relevant logs and/or screenshots
--------------------------------
```
[DEPRECATION WARNING]: The TRANSFORM_INVALID_GROUP_CHARS settings is set to allow bad characters in group names by default, this will change, but still be user configurable on deprecation. This feature will be removed in version 2.10.
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details
```
Possible fixes
--------------
(If you can, link to the line of code that might be responsible for the problem)
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/67NFS might not be mounted on start2020-08-24T17:46:02+02:00sg7149NFS might not be mounted on startCalling host: asterix.las.kit.edu (Fedora 29)
Failing nodes: asterix.las.kit.edu
Summary
-------
NFS is not mounted on boot.
Steps to reproduce
------------------
Boot the computer
What is the current bug behavior?
--------------...Calling host: asterix.las.kit.edu (Fedora 29)
Failing nodes: asterix.las.kit.edu
Summary
-------
NFS is not mounted on boot.
Steps to reproduce
------------------
Boot the computer
What is the current bug behavior?
---------------------------------
las-archiv1 is not mounted though it is in the fstab
What is the expected correct behaviour?
---------------------------------------
las-archiv1 is mounted after booting
Possible fixes
--------------
Probably the mounts are done before the network target is reached and therefore the NFS export is not viewable at that time, yet.
/cc @gethmannhttps://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/52pyepics does not work on CN with Python 32019-02-14T15:21:55+01:00sg7149pyepics does not work on CN with Python 3pyepics is not importable with Python 3
@ucegg : I cannot reproduce this behaviour, so please elaborate on this issue.
My try shows the following expected behaviour:
```
messuser@las94:~$ python2
Python 2.7.15 (default, Oct 15 2018, 18...pyepics is not importable with Python 3
@ucegg : I cannot reproduce this behaviour, so please elaborate on this issue.
My try shows the following expected behaviour:
```
messuser@las94:~$ python2
Python 2.7.15 (default, Oct 15 2018, 18:36:25)
[GCC 7.3.1 20180712 (Red Hat 7.3.1-6)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import epics
>>> exit()
messuser@las94:~$ python3
Python 3.6.6 (default, Jul 19 2018, 16:29:00)
[GCC 7.3.1 20180303 (Red Hat 7.3.1-5)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import epics
>>> exit()
```
and not an `ImportError`https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/48OKI printer fails when used with evince2020-08-24T17:44:41+02:00sg7149OKI printer fails when used with evinceCalling host: las113.las.kit.edu (Fedora 29)
Summary
-------
When I try to print a PDF opened with evince, the OKI fails and needs a restart.
Steps to reproduce
------------------
Print e.g. [Github-Forking.pdf](/uploads/abfd6b7cc5b...Calling host: las113.las.kit.edu (Fedora 29)
Summary
-------
When I try to print a PDF opened with evince, the OKI fails and needs a restart.
Steps to reproduce
------------------
Print e.g. [Github-Forking.pdf](/uploads/abfd6b7cc5bc48e8b151901e9848be8a/Github-Forking.pdf) with evince. Duplex
What is the current bug behavior?
---------------------------------
Schwerer Ausnahmefehler ...
Bitte starten Sie den Drucker neu
What is the expected correct behaviour?
---------------------------------------
Works like it does in okular
Relevant logs and/or screenshots
--------------------------------
```
TODO
```
Possible workaround
-------------------
Just as a workaround: use okular instead of evince.
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/47NFS users dir2019-01-22T16:23:08+01:00sg7149NFS users dirCalling host: lasXXX.las.kit.edu (Fedora XX)
Failing nodes: las127
Summary
-------
NFS mount does not show new mounted `las-archiv1/users`
What is the current bug behavior?
---------------------------------
directory is empty
Wha...Calling host: lasXXX.las.kit.edu (Fedora XX)
Failing nodes: las127
Summary
-------
NFS mount does not show new mounted `las-archiv1/users`
What is the current bug behavior?
---------------------------------
directory is empty
What is the expected correct behaviour?
---------------------------------------
users directory (new disk) should also appear at /las-archiv1/users via NFS
Possible fixes
--------------
also export `/las-archiv1/users`
/cc @gethmann @lp5884lp5884lp5884https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/44latex fails2019-10-28T18:15:54+01:00sg7149latex failshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/43ntp role fails2019-01-10T18:01:06+01:00sg7149ntp role failsCalling host: las126.las.kit.edu (Fedora 27)
Failing nodes: las115 (Fedora 29)
Summary
-------
(Summarize the bug encountered concisely)
Steps to reproduce
------------------
(How one can reproduce the issue - this is very importan...Calling host: las126.las.kit.edu (Fedora 27)
Failing nodes: las115 (Fedora 29)
Summary
-------
(Summarize the bug encountered concisely)
Steps to reproduce
------------------
(How one can reproduce the issue - this is very important)
What is the current bug behavior?
---------------------------------
(What actually happens)
What is the expected correct behaviour?
---------------------------------------
(What you should see instead)
Relevant logs and/or screenshots
--------------------------------
```
TASK [common : set time server] *************************************************************************************************************************************************************************************************************
ok: [las115.las.kit.edu]
TASK [common : insert SCC into ntp configuration] *******************************************************************************************************************************************************************************************
fatal: [las115.las.kit.edu]: FAILED! => {"changed": false, "msg": "Path /etc/ntp.conf does not exist !", "rc": 257}
to retry, use: --limit @/root/ansible/sites.retry
PLAY RECAP **********************************************************************************************************************************************************************************************************************************
las115.las.kit.edu : ok=25 changed=1 unreachable=0 failed=1
```
Possible fixes
--------------
(If you can, link to the line of code that might be responsible for the problem)
/cc @gethmann