32-0-IT instructions and rules issueshttps://git.scc.kit.edu/groups/las-it-organisation/32-0-IT-InstructionsAndRules/-/issues2020-05-04T12:32:11+02:00https://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/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/14skipping of elegant SDDSToolKit fails on F WS 252017-10-09T13:05:30+02:00sg7149skipping of elegant SDDSToolKit fails on F WS 25Though this should be skipped (like it does, when using the debug module), it does not and therefore fails.
role: elegant/tasks/elegant.yml lines 44 onwards
computer: las-gethmann.las.kit.edu
```
TASK [elegant : install SDDSToolKit] ...Though this should be skipped (like it does, when using the debug module), it does not and therefore fails.
role: elegant/tasks/elegant.yml lines 44 onwards
computer: las-gethmann.las.kit.edu
```
TASK [elegant : install SDDSToolKit] ********************************************************************************************************************************************************************************************************
fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "module_stderr": "No handlers could be found for logger \"dnf\"\nTraceback (most recent call last):\n File \"/tmp/ansible__ZtL8C/ansible_module_dnf.py\", line 534, in <module>\n main()\n File \"/tmp/ansible__ZtL8C/ansible_module_dnf.py\", line 530, in main\n ensure(module, base, params['state'], params['name'], params['autoremove'])\n File \"/tmp/ansible__ZtL8C/ansible_module_dnf.py\", line 364, in ensure\n _install_remote_rpms(base, filenames)\n File \"/tmp/ansible__ZtL8C/ansible_module_dnf.py\", line 322, in _install_remote_rpms\n pkgs.append(base.add_remote_rpm(filename))\n File \"/usr/lib/python2.7/site-packages/dnf/base.py\", line 925, in add_remote_rpm\n return self.sack.add_cmdline_package(path)\nIOError: Can not load RPM file: 26: u'3.5.1-1'}.fedora.25.x86_64.rpm.\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
```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/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/53sublime-merge2019-02-08T20:48:36+01:00sg7149sublime-mergehttps://www.sublimemerge.com/docs/linux_repositories#dnf
might be a software that is useful for new git users and those who prefer GUIs over CLI and do not use IDEs (PyCharm) either.https://www.sublimemerge.com/docs/linux_repositories#dnf
might be a software that is useful for new git users and those who prefer GUIs over CLI and do not use IDEs (PyCharm) either.https://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/25texlive package names might change in future Fedora releases2021-09-03T14:43:48+02:00sg7149texlive package names might change in future Fedora releasesFedora 27 does not use the current stable TexLive version 2017.
For the next Fedora release the names of the texlive packages might change, because there is an [issue about renaming](https://bugzilla.redhat.com/show_bug.cgi?id=1505342) f...Fedora 27 does not use the current stable TexLive version 2017.
For the next Fedora release the names of the texlive packages might change, because there is an [issue about renaming](https://bugzilla.redhat.com/show_bug.cgi?id=1505342) from `texlive` into `texlive-base` and `texlive`.
Test via copr:
```
dnf copr enable spot/texlive
```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/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.