Project

General

Profile

Tâche #23774

Scénario #23699: Créer l'application "Déploiement" (working title) dans Zéphir UI

Corriger le problème d'insertion du retour d'exécution d'un job

Added by William Petit almost 3 years ago. Updated almost 3 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
04/23/2018
Due date:
% Done:

0%

Remaining (hours):
0.0

Description

Après l'envoi d'un message 'v1.execution.salt.configuration.deploy', le message d'erreur suivant apparaît dans les logs de Zéphir:

postgres_1             | 2018-04-26T09:59:43.195585253Z 2018-04-26 09:59:43.195 UTC [11430] ERROR:  duplicate key value violates unique constraint "jids_pkey" 
postgres_1             | 2018-04-26T09:59:43.195674427Z 2018-04-26 09:59:43.195 UTC [11430] DETAIL:  Key (jid)=(20180426095942815135) already exists.
postgres_1             | 2018-04-26T09:59:43.206001683Z 2018-04-26 09:59:43.195 UTC [11430] STATEMENT:  INSERT INTO jids
postgres_1             | 2018-04-26T09:59:43.206030727Z                    (jid, load)
postgres_1             | 2018-04-26T09:59:43.206068786Z                     VALUES ('20180426095942815135', '{"fun_args": ["eole.configuration.deploy"], "jid": "20180426095942815135", "return": {"file_|-Deploy config.eol_|-/etc/eole/config.eol_|-managed": {"comment": "Source file salt://eole/configuration/files/1/config.eol not found", "pchanges": {}, "name": "/etc/eole/config.eol", "start_time": "12:58:43.001456", "result": false, "duration": 4.952, "__run_num__": 1, "__sls__": "eole.configuration.deploy", "changes": {}, "__id__": "Deploy config.eol"}, "file_|-Deploy aggregate.xml_|-/etc/eole/aggregate.xml_|-managed": {"comment": "Source file salt://eole/configuration/files/1/aggregate.xml not found", "pchanges": {}, "name": "/etc/eole/aggregate.xml", "start_time": "12:58:42.975258", "result": false, "duration": 25.946, "__run_num__": 0, "__sls__": "eole.configuration.deploy", "changes": {}, "__id__": "Deploy aggregate.xml"}}, "retcode": 2, "success": true, "cmd": "_return", "_stamp": "2018-04-26T09:59:43.185191", "fun": "state.apply", "id": "1", "out": "highstate"}')

Associated revisions

Revision 67864c9c (diff)
Added by William Petit almost 3 years ago

Get around 'pgjsonb' saltmaster's return limitations

The current 'pgjsonb' returner do not enable us to detect the state of a job by
looking into the 'jids' table (see
https://github.com/saltstack/salt/issues/47327).

This change adds a 'completed' column to the query result that circumvent
this limitation.

ref #23774

Revision 0e3a1257 (diff)
Added by William Petit almost 3 years ago

Complete execution.salt.jobs.list results with job status

ref #23730
ref #23774

Revision b66ffbe0 (diff)
Added by William Petit almost 3 years ago

Properly extract jobs status in jobs listing query

ref #23774

Revision ff7a6f5b (diff)
Added by William Petit almost 3 years ago

Properly extract jobs status in jobs listing query

ref #23774

Revision 80830770 (diff)
Added by William Petit almost 3 years ago

Fix job status display

ref #23774
ref #23699

History

#1 Updated by William Petit almost 3 years ago

  • Description updated (diff)

#2 Updated by William Petit almost 3 years ago

  • Status changed from Nouveau to En cours

#3 Updated by William Petit almost 3 years ago

  • Assigned To set to William Petit

#4 Updated by William Petit almost 3 years ago

  • Status changed from En cours to Nouveau
  • Parent task changed from #23735 to #23699

#5 Updated by William Petit almost 3 years ago

  • Status changed from Nouveau to En cours

#6 Updated by William Petit almost 3 years ago

Problème lié au bug upstream https://github.com/saltstack/salt/issues/22171

#7 Updated by William Petit almost 3 years ago

  • Status changed from En cours to Résolu

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

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

Also available in: Atom PDF