32-0-IT instructions and rules issueshttps://git.scc.kit.edu/groups/las-it-organisation/32-0-IT-InstructionsAndRules/-/issues2020-11-18T16:54:27+01:00https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/101Opera binaries to PATH2020-11-18T16:54:27+01:00sg7149Opera binaries to PATHAdd the main Opera binaries to the global PATH environment variable, so that they are available in all terminals.
* operafea-modeller*
* operafea-op3solve*
* operafea-post*
* operafea-readtrack*
* operafea-manager*
* operafea-pp*Add the main Opera binaries to the global PATH environment variable, so that they are available in all terminals.
* operafea-modeller*
* operafea-op3solve*
* operafea-post*
* operafea-readtrack*
* operafea-manager*
* operafea-pp*zx8344samira.fatehi@kit.eduzx8344samira.fatehi@kit.eduhttps://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 #9https://git.scc.kit.edu/las-it-organisation/32-0-IT-InstructionsAndRules/ansible/-/issues/103get rid of old IPA related tasks and documentation2020-08-14T10:40:38+02:00sg7149get rid of old IPA related tasks and documentationAfter IPA is replaced by KIT-AD's LDAP one needs to clean the roles and the documentationAfter IPA is replaced by KIT-AD's LDAP one needs to clean the roles and the documentationKIT-ADhttps://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/107Add the KIT-AD integration2021-04-23T16:03:28+02:00sg7149Add the KIT-AD integrationSummary
-------
The AD integration is not automated so some behaviours are unexpected (las-archiv1 permissions on other computers) and setting up new computers involves manual work.
Steps to reproduce
------------------
1. SSH to a m...Summary
-------
The AD integration is not automated so some behaviours are unexpected (las-archiv1 permissions on other computers) and setting up new computers involves manual work.
Steps to reproduce
------------------
1. SSH to a machine that is not yours and try to access /mnt/las-archiv1.
2. Setup a new computer.
What is the current bug behaviour?
---------------------------------
1. Permission denied, because I'm not in the users group.
2. No login with KIT account possible
What is the expected correct behaviour?
---------------------------------------
1. Access granted (I am part of the group users)
2. Login with KIT account works.
Relevant logs and/or screenshots
--------------------------------
```
[sg7149@methusalix ~]$ ls -la /mnt/las-archiv1/
ls: cannot open directory '/mnt/las-archiv1/': Permission denied
```
Possible fixes
--------------
Implement the KIT-LAS_LDAP guide.yuancun.nieyuancun.niehttps://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.edu