Bug #15307
closedGeneration status is empty and grey at every connection
Added by Alexis Mousset over 5 years ago. Updated about 5 years ago.
Description
We need to trigger a generation to see an actual status.
The event log for policy generation end are missing.
There is other missing event log: user login / logout.
Files
2019-07-31_22.44.38-Rudder_-_Search_Nodes.png (3.78 KB) 2019-07-31_22.44.38-Rudder_-_Search_Nodes.png | François ARMAND, 2019-07-31 22:49 | ||
console.png (228 KB) console.png | Alexis Mousset, 2019-08-05 10:35 |
Updated by François ARMAND over 5 years ago
- File 2019-07-31_22.44.38-Rudder_-_Search_Nodes.png 2019-07-31_22.44.38-Rudder_-_Search_Nodes.png added
- Target version changed from 6.0.0~beta1 to 5.0.13
Screenshot.
It may be linked to https://issues.rudder.io/issues/15315 because we have an elm error, and perhaps it's that that stop the JS to exec.
(It is not related to https://issues.rudder.io/issues/14941 because it works as expected in Rudder 5.0.12)
Updated by Nicolas CHARLES over 5 years ago
Problem in 5.1 is because there aren't any event for the end of policy generation:
182 2019-08-21 13:03 admin Policy update started automatically Automatically update policies
but no
Actor
Type
Description
14644 2019-08-21 15:04 admin Policy update finished successfully Successful policy update
Updated by Nicolas CHARLES over 5 years ago
- Target version changed from 5.0.13 to 6.0.0~beta1
cannot reproduce it in 5.0
Updated by Nicolas CHARLES over 5 years ago
error is within
val boxId: IOResult[Int] = transactIOResult(s"Error when persisting event log ${eventLog.eventType.serialize}")(xa => sql""" insert into eventlog (creationdate, modificationid, principal, eventtype, severity, data, reason, causeid) values(${eventLog.creationDate}, ${modId.value}, ${eventLog.principal.name}, ${eventLog.eventType.serialize}, ${eventLog.severity}, ${elt}, ${eventLog.eventDetails.reason}, ${eventLog.cause} ) """.update.withUniqueGeneratedKeys[Int]("id").transact(xa)) for { id <- boxId
that fails silently.
I don't even understand why
Updated by Nicolas CHARLES over 5 years ago
even replacing the values wih those of another eventype fails
my hypothesis is that there are two transactions in the same "run" so the second can't be done (as the success one depends on the started policy generation one)
Updated by Nicolas CHARLES over 5 years ago
postgres only sees
2019-08-21 16:52:54.941 CEST [15309] rudder@rudder LOG: could not receive data from client: Connection reset by peer
Updated by François ARMAND over 5 years ago
- Status changed from New to In progress
- Assignee changed from Nicolas CHARLES to François ARMAND
Updated by François ARMAND over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/2419
Updated by François ARMAND over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|562e2b19cabbd501d8bd9bacbb53ae0f6f488193.
Updated by Vincent MEMBRÉ about 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.0~beta1 which was released today.