Project

General

Profile

Scénario #31010

Le service onenode est en erreur sur Hâpy (2.8.0-beta1)

Added by Joël Cuissinat 11 months ago. Updated 10 months ago.

Status:
Terminé (Sprint)
Priority:
Normal
Assigned To:
Category:
-
Start date:
04/10/2020
Due date:
11/27/2020
% Done:

100%

Estimated time:
0.00 h
Story points:
1.0
Remaining (hours):
0.00 hour
Velocity based estimate:
Release:
Release relationship:
Auto

Description

  • Pas №11

Erreur au déploiement de la VM :

Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/100/0/deployment.0

Indice :

root@hapy:~# service onenode status
● onenode.service - OpenNebula Node starter
     Loaded: loaded (/lib/systemd/system/onenode.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Thu 2020-11-05 11:19:53 CET; 40s ago
    Process: 2857 ExecStart=/usr/share/eole/sbin/onevm-all -c ${CREDS} -a resume (code=exited, status=1/FAILURE)
   Main PID: 2857 (code=exited, status=1/FAILURE)

nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/one/ruby/opennebula/xml_utils.rb:19:in `<top (required)>'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/one/ruby/opennebula.rb:27:in `<top (required)>'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
nov. 05 11:19:53 hapy onevm-all[2857]:         from /usr/share/eole/sbin/onevm-all:28:in `<main>'
nov. 05 11:19:53 hapy systemd[1]: onenode.service: Main process exited, code=exited, status=1/FAILURE
nov. 05 11:19:53 hapy systemd[1]: onenode.service: Failed with result 'exit-code'.
nov. 05 11:19:53 hapy systemd[1]: Failed to start OpenNebula Node starter.

Solutions à mettre en œuvre

  • trouver pourquoi le service ne démarre pas (reproductible sur aca.hapy-2.8.0b1-instance-default) et corriger

Critères d'acceptation

  • le déploiement de VM est fonctionnel
  • le test squash est passant

Subtasks

Tâche #31131: Vérifier les dépendances rubyFerméPhilippe Caseiro


Related issues

Related to Distribution EOLE - Tâche #31153: Valider le scénario Le service onenode est en erreur sur Hâpy (2.8.0-beta1) Fermé 11/16/2020
Related to Distribution EOLE - Scénario #31222: Le déploiement de VM doit être fonctionnel sur Hâpy 2.8.0 Terminé (Sprint) 11/17/2020 12/18/2020

History

#1 Updated by Joël Cuissinat 11 months ago

  • Copied from Tâche #30975: Correction <ID_DU_TEST> - <nom test> - <NOM DU JEU DE DONNÉES> (2.8.0-beta1) added

#2 Updated by Joël Cuissinat 11 months ago

  • Copied from deleted (Tâche #30975: Correction <ID_DU_TEST> - <nom test> - <NOM DU JEU DE DONNÉES> (2.8.0-beta1))

#3 Updated by Joël Cuissinat 11 months ago

  • Description updated (diff)

#4 Updated by Joël Cuissinat 11 months ago

Dans un autre test, je constate également :

root@hapy:~# diagnose 
*** Test du module hapy version 2.8.0 (hapy 0000000A) ***

Attention, serveur opérationnel mais des services ne sont pas démarrés :

onenode.service loaded failed
opennebula-showback.service loaded failed

...

#5 Updated by Joël Cuissinat 11 months ago

  • Parent task deleted (#30862)

#6 Updated by Joël Cuissinat 11 months ago

  • Tracker changed from Tâche to Scénario
  • Subject changed from Correction HP-001-02 - Test Pré paramétrage HAPY avec image EOLE (2.8.0-beta1) to Le service onenode est en erreur sur Hâpy (2.8.0-beta1)
  • Due date set to 11/06/2020

#7 Updated by Gilles Grandgérard 11 months ago

  • Target version changed from sprint 2020 43-45 Equipe MENSR to sprint 2020 46-48 Equipe MENSR

#8 Updated by Gilles Grandgérard 11 months ago

Le test Jenkins a la même erreur

https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-hapy-002-2.8.0-amd64/168/console

18:32:51             Attention, serveur opérationnel mais des services ne sont pas démarrés :
18:32:51             onenode.service loaded failed
18:31:01             Job for onenode.service failed because the control process exited with error code.
18:31:01             See "systemctl status onenode.service" and "journalctl -xe" for details.

#9 Updated by Gilles Grandgérard 11 months ago

  • Target version changed from sprint 2020 46-48 Equipe MENSR to Prestation Cadoles MEN 46-48
  • Story points set to 1.0

#10 Updated by Joël Cuissinat 11 months ago

  • Description updated (diff)
  • Release set to EOLE 2.8.0

#11 Updated by Emmanuel GARETTE 11 months ago

  • Assigned To set to Philippe Caseiro

#12 Updated by Joël Cuissinat 10 months ago

  • Related to Tâche #31153: Valider le scénario Le service onenode est en erreur sur Hâpy (2.8.0-beta1) added

#13 Updated by Daniel Dehennin 10 months ago

Pour le problème de déploiement de la machine, j’ai ça dans les logs :

root@hapy:~# cat /var/log/one/0.log 
Tue Nov 24 09:49:26 2020 [Z0][VM][I]: New state is ACTIVE
Tue Nov 24 09:49:26 2020 [Z0][VM][I]: New LCM state is PROLOG
Tue Nov 24 09:49:26 2020 [Z0][VM][I]: New LCM state is BOOT
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/0/deployment.0
Tue Nov 24 09:49:26 2020 [Z0][VM][I]: Virtual Machine has no context
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/100/0/deployment.0' 'hapy' 0 hapy
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: error: Disconnected from qemu+tcp://localhost/system due to I/O error
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/100/0/deployment.0
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: error: End of file while reading data: Input/output error
Tue Nov 24 09:49:26 2020 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/100/0/deployment.0
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: ExitCode: 255
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: Successfully execute network driver operation: clean.
Tue Nov 24 09:49:26 2020 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Tue Nov 24 09:49:26 2020 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/100/0/deployment.0
Tue Nov 24 09:49:26 2020 [Z0][VM][I]: New LCM state is BOOT_FAILURE

libvirt n’écoute pas sur localhost ?

#14 Updated by Joël Cuissinat 10 months ago

  • Related to Scénario #31222: Le déploiement de VM doit être fonctionnel sur Hâpy 2.8.0 added

#15 Updated by Daniel Dehennin 10 months ago

Daniel Dehennin a écrit :

Pour le problème de déploiement de la machine, j’ai ça dans les logs :

[...]

libvirt n’écoute pas sur localhost ?

Cela fonctionne lorsque le template aca.hapy utilise

CPU_MODEL = [
  MODEL = "host-passthrough" ]

#16 Updated by Joël Cuissinat 10 months ago

  • Status changed from Nouveau to Terminé (Sprint)

Le service démarre bien sur une machine "instance-default" mais les VM ne démarrent toujours pas.

=> nouveau scénario #31222

Also available in: Atom PDF