Feature #2757: Show errors logs in the production.log for the API - Foreman

Custom queries

3.10.0 release DONE
3.10.0 release TODO
3.11.0 release DONE
3.11.0 release TODO
3.8.1 release DONE
3.8.1 release TODO
3.9.2 release DONE
3.9.2 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Feature #2757

closed

Show errors logs in the production.log for the API

Added by Lukas Zapletal almost 11 years ago. Updated almost 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Tomáš Strachota

Category:

API

Target version:

1.3.0

Difficulty:

easy

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

When I call any Foreman New API service and it fails during saving in ActiveRecord, only ActiveRecord::RecordNotSaved exception (message) is shown and the reason (errors array) is hidden.

We need to use either save! method when saving or handing the active record object into the base controller for checks.

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Tomáš Strachota almost 11 years ago

Assignee set to Tomáš Strachota

I haven't managed to reproduce it. Can you please provide more details? What api version and resource you tried it with? Did you use foreman-api library or was it via curl?

Actions

Copy link

Updated by Lukas Zapletal almost 11 years ago

Tracker changed from Bug to Feature
Subject changed from Foreman API hides exceptions to Show errors logs in the production.log for the API

Actions

Copy link

Updated by Marek Hulán almost 11 years ago

Not sure whether it helps, but anyway.. I encountered similar error because of validation errors on some associated object a month ago. Save returned false (which is usually not checked) and errors on main object was empty. Could this be the cause? Particular problem I described is already fixed btw.

Actions

Copy link

Updated by Lukas Zapletal almost 11 years ago

Target version changed from 1.3.0 to 1.2.1

Marek, this must be something else. In my case, I do see errors array but there is no way of digging in the problem.

Since users are reporting issues with this on the channel, I am setting target version to 1.2.1. Tomas can you please provide fix for 1.2 stable? Users are starting with the API and hitting errors, this could help them to track validation problems.

Actions

Copy link