Projet

Général

Profil

Scénario #32219

Mis à jour par Joël Cuissinat il y a environ 3 ans

h3. Pas №11 №<X>

Erreurs suspectes au reconfigures sur hapy3 :
<pre>
run-parts: executing /usr/share/eole/postservice/99-init-hapy-master reconfigure
run-parts: executing /usr/share/eole/postservice/99-init-k8s-service reconfigure
kubernetes application disabled
run-parts: executing /usr/share/eole/postservice/99-one-hooks-manager reconfigure
[one.hook.update] Cannot process request, no leader found
Warning: vm-close_ports_on_shutdown hook creation failed !
[one.hook.update] Cannot process request, no leader found
Warning: vm-close_ports_on_stop hook creation failed !
[one.hook.update] Cannot process request, no leader found
Warning: vm-open_ports hook creation failed !
run-parts: executing /usr/share/eole/postservice/99-z-ha reconfigure
</pre> …

h3. Pas №14 №<Y>

Erreur (fatale) au reconfigure de hapy1 :
<pre>
run-parts: executing /usr/share/eole/postservice/30-one-mng reconfigure
Wait for oned to be started.
The default cluster name is already "default"
Host default already present in cluster
[ERROR][Hosts sync failed]
run-parts: /usr/share/eole/postservice/30-one-mng exited with return code 1
Erreur : postservice
</pre> …

* le service *OneFlow* est signalé en erreur sur les 3 machines
* sur hapy2 et hapy3, le diagnose signale également :
<pre>
opennebula-flow.service loaded failed
opennebula-gate.service loaded failed
opennebula-hem.service loaded failed
</pre>

h3. Exécution Squash-TM

* https://dev-eole.ac-dijon.fr/squash/executions/11947 https://dev-eole.ac-dijon.fr/squash/executions/<NUMÉRO>

Retour