Project

General

Profile

Actions

Bug #13769

closed

SSH provisioning fails when sql logging level is set to 'error'

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
Orchestration
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Current logger calls return `true`|`false` depending whether the current level
allows the logging message or not.

In the orchestration, we happened to have the logger call as the last
call of the orchestration method (https://github.com/theforeman/foreman/blob/1.10.1/app/models/concerns/orchestration/ssh_provision.rb#L66).

When the method returns non-true value, it's considered as failure and the whole thing
tries to get rollbacked.


Related issues 3 (3 open0 closed)

Related to Foreman - Bug #13771: Failure in after_commit orchestration is very hard to debugNew02/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

Also available in: Atom PDF