Project

General

Profile

Bug #39098

Remplacer la ressource tidy par une cronjob

Added by Gabriel Filion 9 months ago. Updated about 1 month ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
-
Start date:
2022-01-31
Due date:
% Done:

0%

RT ticket:
Affected versions:
Points:
1
Sprint:

Description

J'ai remarqué que la ressource de type "tidy", qui déjà est tannante parce que ça output qqch même s'il y a rien à faire, peut causer des restarts de services de manière plutôt inutile.

  Notice: /Stage[main]/Ganeti::Config/Tidy[/var/lib/ganeti/queue]: Tidying 3 files
  Info: Applying configuration version '1648839732'
  Notice: /Stage[main]/Ganeti::Config/File[/var/lib/ganeti/queue/job-90477]/ensure: current_value 'file', should be 'absent' (noop)
  Notice: /Stage[main]/Ganeti::Config/File[/var/lib/ganeti/queue/job-90476]/ensure: current_value 'file', should be 'absent' (noop)
  Notice: /Stage[main]/Ganeti::Config/File[/var/lib/ganeti/queue/job-90475]/ensure: current_value 'file', should be 'absent' (noop)
[...]
  Notice: Class[Ganeti::Config]: Would have triggered 'refresh' from 3 events
  Info: Class[Ganeti::Config]: Scheduling refresh of Class[Ganeti::Service]
  Notice: Class[Ganeti::Service]: Would have triggered 'refresh' from 1 event
  Info: Class[Ganeti::Service]: Scheduling refresh of Service[ganeti]
  Notice: /Stage[main]/Ganeti::Service/Service[ganeti]: Would have triggered 'refresh' from 1 event
  Notice: Class[Ganeti::Service]: Would have triggered 'refresh' from 1 event
  Notice: Class[Ganeti]: Would have triggered 'refresh' from 2 events

Les restarts font en sorte que les nodes sont pas rejoignable par le master du cluster pendant quelques secondes à chaque fois et ça peut faire échouer certaines commandes.

Donc je pense qu'on voudrait remplacer ça par une cronjob qui fait le même ménage mais sans déclancher un restart du service.

Voir: https://gitlab.com/shared-puppet-modules-group/puppet-ganeti/-/issues/11

History

#1 Updated by Gabriel Filion 8 months ago

  • Due date changed from 2022-02-04 to 2022-02-25

#2 Updated by Gabriel Filion 7 months ago

  • Due date changed from 2022-02-25 to 2022-03-04

#3 Updated by Gabriel Filion 7 months ago

  • Due date changed from 2022-03-04 to 2022-04-08

#4 Updated by Gabriel Filion 6 months ago

  • Description updated (diff)

#5 Updated by Gabriel Filion 6 months ago

  • Due date changed from 2022-04-08 to 2022-04-15

#6 Updated by Gabriel Filion 6 months ago

  • Due date changed from 2022-04-15 to 2022-04-22

#7 Updated by Gabriel Filion 5 months ago

  • Due date changed from 2022-04-22 to 2022-05-13

#8 Updated by Gabriel Filion 4 months ago

  • Due date changed from 2022-05-13 to 2022-06-10

low low low your priority
gently sitting by
steadily steadily steadily awaiting
further down the calendar

#9 Updated by Gabriel Filion 4 months ago

  • Due date changed from 2022-06-10 to 2022-07-08

#10 Updated by Gabriel Filion 3 months ago

  • Due date changed from 2022-07-08 to 2022-07-13

#11 Updated by Gabriel Filion 3 months ago

  • Due date changed from 2022-07-13 to 2022-08-17

#12 Updated by Gabriel Filion about 2 months ago

  • Due date changed from 2022-08-17 to 2022-09-05

#13 Updated by Gabriel Filion about 1 month ago

  • Due date deleted (2022-09-05)
  • Assignee deleted (Gabriel Filion)

Je pense pas avoir le temps de travailler sur ça avant mon départ. Donc je relâche ça dans le backlog. j'ai fait signe aussi à anarcat comme quoi je laissais tomber la tâche.

Also available in: Atom PDF