ansible issueshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues2020-08-24T17:49:50+02:00https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/21(KIT)Latex installation fails because of failing copy2020-08-24T17:49:50+02:00sg7149(KIT)Latex installation fails because of failing copyCalling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las117 (Fedora 27)
Summary
``with_glob`` fails when used with ``copy`` and ``tempdir``
Steps to reproduce
Run the KITLaTeX tasks.
What is the current bug behavior?
Task...Calling host: las113.las.kit.edu (Fedora 27)
Failing nodes: las117 (Fedora 27)
Summary
``with_glob`` fails when used with ``copy`` and ``tempdir``
Steps to reproduce
Run the KITLaTeX tasks.
What is the current bug behavior?
Task `hack Helvetica into KIT styles due to broken font installation` fails because `copy tex files` does not work.
What is the expected correct behavior?
Files are copied and the task can run.
Relevant logs and/or screenshots
```
TASK [latex : copy pdf files] *********************************************************************************************************
task path: /home/gethmann/ansible/ansible/roles/latex/tasks/KITLaTeX.yml:68
[WARNING]: Unable to find '/tmp/ansiEtob1c/doc/latex/KIT' in expected paths.
```
/cc @gethmannhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/33Add GitLab backup script to a ansible role2021-09-03T15:50:44+02:00sg7149Add GitLab backup script to a ansible rolesg7149sg7149https://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/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/10ansible-pull service2018-06-07T15:51:08+02:00sg7149ansible-pull servicerun ansible-pull as a cronjob or a timed service.
Implement the rule for setup new hosts with this configrun ansible-pull as a cronjob or a timed service.
Implement the rule for setup new hosts with this confighttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/64automate adding of hosts2021-09-03T15:31:05+02:00sg7149automate adding of hostsUse the DNSVS-api to add the host also to the DNS
* sshfsUse the DNSVS-api to add the host also to the DNS
* sshfshttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/90Autoupdate on lab computers2020-07-15T15:40:04+02:00sg7149Autoupdate on lab computersChange the settings from security to all updates.
The computers are not used on a daily basis by one user, but may not be used interactively for some time. Hence the updates aren't triggered by the user, but there is also no user that ex...Change the settings from security to all updates.
The computers are not used on a daily basis by one user, but may not be used interactively for some time. Hence the updates aren't triggered by the user, but there is also no user that expects certain behaviour not to change.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/13Bootstrap wrapper script2021-09-03T15:58:06+02:00sg7149Bootstrap wrapper scriptA script that bootstraps the ansible installation of a host.
* Create the files in `host_vars` and edit `hosts`
Might interfere with issues #10 and #4 and with the `add_host.sh` script of the documentation repositoryA script that bootstraps the ansible installation of a host.
* Create the files in `host_vars` and edit `hosts`
Might interfere with issues #10 and #4 and with the `add_host.sh` script of the documentation repositoryhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/3ControlSystemStudio auf 126 fixen2018-02-08T18:06:06+01:00sg7149ControlSystemStudio auf 126 fixenJava wirft seit dem Upgrade auf Fedora 24 Fehler und CSS startet nicht.Java wirft seit dem Upgrade auf Fedora 24 Fehler und CSS startet nicht.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/45Create test infrastructure for ansible2021-09-03T15:41:08+02:00sg7149Create test infrastructure for ansibleTest ansible roles with GitLab-CI.
[ ] CI runners that start a new Docker of the currently supported Fedoras and run `sites.yml`Test ansible roles with GitLab-CI.
[ ] CI runners that start a new Docker of the currently supported Fedoras and run `sites.yml`https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/40Create the default directory structure2021-09-14T17:15:53+02:00sg7149Create the default directory structureFor new users, create the default directory structure based on the organisation document.
This should be possible by creating it at `/etc/skel`.For new users, create the default directory structure based on the organisation document.
This should be possible by creating it at `/etc/skel`.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/2CUPS printer in ansible2018-03-31T01:10:47+02:00sg7149CUPS printer in ansibleprinting does not work since Fedora 24 upgrade and running client role nor with KDE print menu (this may be an root locked password issue)
io/hpmud/jd.c 93: unable to read device-id
Jul 20 22:34:07 las113.las.kit.edu hp[26249]: prnt/...printing does not work since Fedora 24 upgrade and running client role nor with KDE print menu (this may be an root locked password issue)
io/hpmud/jd.c 93: unable to read device-id
Jul 20 22:34:07 las113.las.kit.edu hp[26249]: prnt/backend/hp.c 825: INFO: open device failed stat=12: hp:/net/HP_LaserJet_P2015_Series?zc=NPI8A10C3; will retry in 30 seconds...
sg7149sg7149https://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/7dhcpd2018-05-23T09:40:35+02:00sg7149dhcpddhcpd server rolle für server und secondary einrichtendhcpd server rolle für server und secondary einrichtenhttps://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/37Docker Gitlab-CI runner2021-09-03T15:49:17+02:00sg7149Docker Gitlab-CI runner* [x] Install GitLab-CI runners (docker) on a proper computer (ask @gethmannn for documentation on the installation on Fedora and it's pitfalls) and
* [ ] create example `.gitlab-ci.yml` files for typical use-cases
* [ ] LaTeX: compil...* [x] Install GitLab-CI runners (docker) on a proper computer (ask @gethmannn for documentation on the installation on Fedora and it's pitfalls) and
* [ ] create example `.gitlab-ci.yml` files for typical use-cases
* [ ] LaTeX: compilation of a document
* [ ] Python: linting PEP-8 or formatting with yapf
* [ ] shell: run shellcheck
* [ ] Document how to use the CI
* [ ] For the owner of the repo
* [ ] For a user who might be confused about merge requests or push commands being rejected
Things to discuss:
* Worth it?
* las126 or las101
* install runner on all clients? That would be a much bigger task imho.https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/18elegant for Fedora 272017-11-22T09:24:15+01:00sg7149elegant for Fedora 27No RPMs available yetNo RPMs available yethttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/8elegant/blas2020-08-24T17:50:17+02:00sg7149elegant/blasgescheit die key-Verwaltung lösengescheit die key-Verwaltung lösenhttps://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/102Environment dependent epics configuration2020-07-15T14:59:38+02:00sg7149Environment dependent epics configurationEPICS is used for different purposes/environments which currently include:
* KARA
* LASMagLab
* TGU measurement
* Jena magnet setup
The configuration so far is only valid for one case only and the other configurations are changed by han...EPICS is used for different purposes/environments which currently include:
* KARA
* LASMagLab
* TGU measurement
* Jena magnet setup
The configuration so far is only valid for one case only and the other configurations are changed by hand which
- needs more steps for the installation and
- is error prone to (re-)running ansible.
This should be fixed.
See also issue #9