Project

General

Profile

Tâche #28362

Scénario #28274: Hapy: Étudier pourquoi la VM reste en état PENDING

Configuration systemd incorrecte pour opennebula-scheduler.service

Added by Gilles Grandgérard almost 2 years ago. Updated almost 2 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Daniel Dehennin
Target version:
sprint 2019 21-23 Equipe MENSR
Start date:
04/29/2019
Due date:
% Done:

100%

Remaining (hours):
0.0

Description

mai 20 18:29:02 hapy systemd[1]: multi-user.target: Found ordering cycle on opennebula-scheduler.service/stop
mai 20 18:29:02 hapy systemd[1]: multi-user.target: Found dependency on opennebula.service/stop
mai 20 18:29:02 hapy systemd[1]: multi-user.target: Found dependency on multi-user.target/stop
mai 20 18:29:02 hapy systemd[1]: multi-user.target: Job opennebula-scheduler.service/stop deleted to break ordering cycle starting with multi-user.target/stop

Associated revisions

Revision 28f098d4 (diff)
Added by Daniel Dehennin almost 2 years ago

Break the loop between OpenNebula services and libvirtd

Since the activation of “opennebula-scheduler.service” in the XML for
HA setup, there is a loop in the services then systemd exclude
the scheduler service from the start services.

This breaks the dependencies of bastion too.

  • systemd/opennebula-schedule.service.d/multi-user.conf: execute after
    “multi-user.service”.
  • systemd/opennebula-flow.service.d/multi-user.conf: execute after
    “multi-user.service”.
  • systemd/opennebula-sunstone.service.d/multi-user.conf: execute after
    “multi-user.service”.
  • systemd/opennebula.service.d/multi-user.conf: execute after
    “multi-user.service”.
  • systemd/opennebula.service.d/libvirtd.conf: new name of the
    dependency management on “libvirtd.service”. Do not manage
    dependency on multi-user.target in this file for consistency with
    other files.
  • eole-one-master.mk: install new service overrides.

Ref: #28362

Revision b1a97653 (diff)
Added by Daniel Dehennin almost 2 years ago

OpenNebula scheduler service is named “opennebula-scheduler.service”

Ref: #28362

Revision 36145bf9 (diff)
Added by Daniel Dehennin almost 2 years ago

Remove old override

Ref: #28362

History

#1 Updated by Gilles Grandgérard almost 2 years ago

  • Status changed from Nouveau to En cours

#2 Updated by Scrum Master almost 2 years ago

  • Status changed from En cours to Nouveau

#3 Updated by Scrum Master almost 2 years ago

  • Status changed from Nouveau to En cours

#4 Updated by Scrum Master almost 2 years ago

  • Description updated (diff)
  • Assigned To set to Daniel Dehennin

#5 Updated by Daniel Dehennin almost 2 years ago

Le problème vient de l’activation du service opennebula-scheduler.service dans un dictionnaire qui entraîne une boucle de démarrage.

Il faut donc revoir toute la chaîne de dépendance, surtout que les services sont sensés démarrer après bastion.

#6 Updated by Daniel Dehennin almost 2 years ago

  • % Done changed from 0 to 100

#7 Updated by Scrum Master almost 2 years ago

  • Status changed from En cours to Résolu

#8 Updated by Joël Cuissinat almost 2 years ago

  • Subject changed from Configuratiion systemd incorrect opennebula-scheduler.service to Configuration systemd incorrect opennebula-scheduler.service

#9 Updated by Joël Cuissinat almost 2 years ago

  • Subject changed from Configuration systemd incorrect opennebula-scheduler.service to Configuration systemd incorrecte pour opennebula-scheduler.service

#10 Updated by Joël Cuissinat almost 2 years ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) set to 0.0

Sera validé par la campagne 2.7.1-RC1

Also available in: Atom PDF