Project

General

Profile

Actions
Copy link

Bug #13771

open

Failure in after_commit orchestration is very hard to debug

Added by Ivan Necas almost 9 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When there is a failure in after_commit orchestration, there is no error message
shown in the UI that would indicate the error.
How to reproduce:

1. try to reproduce http://projects.theforeman.org/issues/13770
2. try to spot that something went wrong form the UI
3. no errors shown except a fraction of second when the task status rollback
appears

Related issues 4 (2 open — 2 closed)

Related to Foreman - Bug #13769: SSH provisioning fails when sql logging level is set to 'error'ClosedIvan Necas02/17/2016Actions
Related to Foreman - Bug #13770: SSH provisioning fails when no puppetca is assigned to the hostDuplicate02/17/2016Actions
Related to Foreman - Tracker #14002: Orchestration build around ActiveRecord hooks trackerNew03/02/2016

Actions
Related to Foreman - Bug #14004: After_commit failure doesn't handle the rollback for the actions performed from the pre_commit phase and active record objectsNew03/02/2016Actions
Actions
Copy link

Also available in: Atom PDF