Project

General

Profile

Actions

Bug #9263

closed

Architecture #2787: Use Doobie or Slick in place of SpringTemplate / squeryl / pur JDBC

Error on report batch: NULL for non option type & on eventlog

Added by François ARMAND over 7 years ago. Updated over 7 years ago.

Status:
Released
Priority:
1
Category:
Architecture - Code maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

On real data, when executing the batch for new reports, we get:


[2016-10-07 11:55:19] ERROR report - Could not get node execution reports in the RudderSysEvents table, cause is: could not
                      get Reports <- Could not fetch the last completed runs from database. <- SQL `NULL` read at column 1 (JDBC type BigInt) but
                      mapping is to a non-Option type; use Option here.

The culprit seem to be: ReportsJdbcRepository#getRuns

A similar issue arise when looking on event logs in getEventLogByCriteria(criteria : Option[String], optLimit:Option[Int] = None, orderBy:Option[String])

Actions #1

Updated by François ARMAND over 7 years ago

  • Subject changed from Error on report batch: NULL for non option type to Error on report batch: NULL for non option type & on eventlog
  • Description updated (diff)
Actions #2

Updated by François ARMAND over 7 years ago

  • Status changed from New to In progress
Actions #3

Updated by François ARMAND over 7 years ago

  • Description updated (diff)
  • Status changed from In progress to New
Actions #4

Updated by Nicolas CHARLES over 7 years ago

When aplying a directive to a rule, I get the following error:

[2016-10-07 12:05:13] ERROR historization - Error with update rules historization process <- Could not update the rules historization information in base. <- L'élément du batch 0 
                 insert into rulesdirectivesjoin (rulepkeyid, rulesdirectivesjoin)
                 values (105, '78e7889c-b5f2-41ed-a7af-269e1098d101')
                a été annulé. Appeler getNextException pour en connaître la cause.
[2016-10-07 12:05:13] ERROR historization - Root cause was: L'élément du batch 0 
                 insert into rulesdirectivesjoin (rulepkeyid, rulesdirectivesjoin)
                 values (105, '78e7889c-b5f2-41ed-a7af-269e1098d101')
                a été annulé. Appeler getNextException pour en connaître la cause.
[2016-10-07 12:05:13] ERROR com.normation.rudder.batch.AsyncDeploymentAgent$DeployerAgent - Error when updating policy, reason Could not update the rules historization information in base. <- L'élément du batch 0 
                 insert into rulesdirectivesjoin (rulepkeyid, rulesdirectivesjoin)
                 values (105, '78e7889c-b5f2-41ed-a7af-269e1098d101')
                a été annulé. Appeler getNextException pour en connaître la cause.

Actions #5

Updated by François ARMAND over 7 years ago

  • Status changed from New to Pending technical review
  • Assignee changed from François ARMAND to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder/pull/1243
Actions #6

Updated by François ARMAND over 7 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #7

Updated by Benoît PECCATTE over 7 years ago

  • Target version changed from 4.0.0~rc2 to 318
Actions #8

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 318 to 4.0.0~rc2
Actions #9

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 4.0.0~rc2 to 4.0.0~rc1
Actions #10

Updated by Alexis Mousset over 7 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.0.0 which was released the 10th November 2016.

Actions

Also available in: Atom PDF