Tâche #23764
Scénario #23759: EOLE 2.7.0 : Le serveur doit s'instancier si l'EAD3 est activé
Adapter l'initialisation des clés du minion aux changements faits par Ubuntu
Associated revisions
Salt-master is running as 'salt': must adapt posttemplate script
ref #23764
Minion's certificates were not copied into /var/lib directory
ref #23764
The base environment's top file is evaluated first
ref #23764
salt-master is running as 'salt'
ref #23764
History
#1 Updated by Fabrice Barconnière almost 5 years ago
- Status changed from Nouveau to En cours
#2 Updated by Fabrice Barconnière almost 5 years ago
- % Done changed from 0 to 100
- Remaining (hours) changed from 2.0 to 1.0
- test-instance-acaeolebaseewt-2.7.0-amd64 ?
- test-instance-acadc1-2.7.0-amd64 ?
#3 Updated by Fabrice Barconnière almost 5 years ago
- % Done changed from 100 to 80
Reste encore un pb :
-------------------------------------------------------------------------------- Exécution des scripts postservice -------------------------------------------------------------------------------- run-parts: executing /usr/share/eole/postservice/00-actions reconfigure ## Synchronisation des modules SaltStack ## [CRITICAL] The Salt Master has rejected this minion's public key! To repair this issue, delete the public key for this minion on the Salt Master and restart this minion. Or restart the Salt Master in open mode to clean out the keys. The Salt Minion will now exit.
#4 Updated by Fabrice Barconnière almost 5 years ago
L'appairage se fait bien maintenant mais il y a encore un problème :
## Synchronisation des modules SaltStack ## [ERROR ] The 'ead' saltenv has no top file, and no matches were found in the top file for the default_top saltenv (base) local:
#5 Updated by Fabrice Barconnière over 4 years ago
Modifier la configuration du master : https://docs.saltstack.com/en/latest/ref/configuration/minion.html#std:conf_minion-top_file_merging_strategy
À voir l'impact
#6 Updated by Fabrice Barconnière over 4 years ago
Du côté de saltstack, ça semble OK.
Par contre, on ne peut pas se connecter à l'EAD3 :- /var/log/eoleflask/eoleflask.log
2018-04-30 10:39:10,339: eoleflask - Unable to load module 'ead3fileserver': No module named auth Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/eoleflask/loader.py", line 80, in load_app m = __import__(module) File "/usr/lib/python2.7/dist-packages/ead3fileserver/__init__.py", line 18, in <module> from ead3fileserver import api File "/usr/lib/python2.7/dist-packages/ead3fileserver/api.py", line 8, in <module> import salt.auth ImportError: No module named auth
#7 Updated by Fabrice Barconnière over 4 years ago
- % Done changed from 80 to 100
- Remaining (hours) changed from 1.0 to 0.25
Pour l'EAD3, un scénario a été ouvert : #23796
#8 Updated by Scrum Master over 4 years ago
- Status changed from En cours to Résolu
#9 Updated by Joël Cuissinat over 4 years ago
Idem, j'arrive sur la mire d'authentification puis impossible de se connecter.
J'obtiens la même erreur dans les logs.
#10 Updated by Joël Cuissinat over 4 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) changed from 0.25 to 0.0