Project

General

Profile

Bug #16439

Not report compliance because of scala.UninitializedFieldError

Added by François ARMAND 9 months ago. Updated 7 months ago.

Status:
Released
Priority:
N/A
Category:
Web - Compliance & node report
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
92

Description

The job in charge of processing node execution fails to start in 5.0.16-nightly because of an unitialized field:

[2019-12-19 08:56:00] ERROR application - scala.UninitializedFieldError: Uninitialized field: /home/jenkins/workspace/mvn-rudder-5.0/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/batch/FetchNodeExecutions.scala: 62
[2019-12-19 08:56:00] ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
scala.UninitializedFieldError: Uninitialized field: /home/jenkins/workspace/mvn-rudder-5.0/webapp/sources/rudder/rudder-core/src/main/scala/com/normation/rudder/batch/FetchNodeExecutions.scala: 62
        at com.normation.rudder.batch.FindNewReportsExecution.executeTask(FetchNodeExecutions.scala:62)
        at com.normation.rudder.batch.AbstractScheduler$StatusManager$TaskProcessor$$anonfun$messageHandler$2.applyOrElse(AbstractScheduler.scala:197)
        at com.normation.rudder.batch.AbstractScheduler$StatusManager$TaskProcessor$$anonfun$messageHandler$2.applyOrElse(AbstractScheduler.scala:190)
        at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:38)
        at net.liftweb.actor.SpecializedLiftActor.execTranslate(LiftActor.scala:338)
        at net.liftweb.actor.SpecializedLiftActor.execTranslate$(LiftActor.scala:338)
        at com.normation.rudder.batch.AbstractScheduler$StatusManager$TaskProcessor$.execTranslate(AbstractScheduler.scala:188)
        at net.liftweb.actor.SpecializedLiftActor.proc2(LiftActor.scala:304)
        at net.liftweb.actor.SpecializedLiftActor.$anonfun$processMailbox$1(LiftActor.scala:226)
        at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
        at net.liftweb.actor.SpecializedLiftActor.around(LiftActor.scala:240)
        at net.liftweb.actor.SpecializedLiftActor.around$(LiftActor.scala:239)
        at com.normation.rudder.batch.AbstractScheduler$StatusManager$TaskProcessor$.around(AbstractScheduler.scala:188)
        at net.liftweb.actor.SpecializedLiftActor.processMailbox(LiftActor.scala:226)
        at net.liftweb.actor.SpecializedLiftActor.$anonfun$$bang$3(LiftActor.scala:189)
        at net.liftweb.actor.LAScheduler$$anon$2$$anon$3.run(LiftActor.scala:76)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
#1

Updated by François ARMAND 9 months ago

I restarted Rudder and the problem didn't occure, so I don't know if it's non deterministic or only happen on first boot.

#2

Updated by François ARMAND 9 months ago

  • Status changed from New to In progress
#3

Updated by François ARMAND 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/2683
#4

Updated by François ARMAND 9 months ago

  • Status changed from Pending technical review to Pending release
#5

Updated by Nicolas CHARLES 8 months ago

  • Priority changed from 94 to 93
#6

Updated by Alexis MOUSSET 7 months ago

  • Priority changed from 93 to 92
#7

Updated by Vincent MEMBRÉ 7 months ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.16 which was released today.

Also available in: Atom PDF