Actions
Bug #22527
closed
PostgreSQL error doobie.util.invariant$UnexpectedEnd$
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
Sometimes, when we are creating a new campaign, the event is correctly created but then it is skipped with a PostgreSQL related error:
This event will be skipped. Reason: An error occurred when processing event: SystemError: error when getting campaign event with id d1c5a2b1-6bea-4140-b601-3c25ce10fa98; cause was: doobie.util.invariant$UnexpectedEnd$: ResultSet exhausted; more rows expected. ->
Trying to delete the campaign result in error 500.
It used to be linked with the creation of a campaign with the same name than one deleted, or with the creation of a campaign without a name.
Updated by Nicolas CHARLES about 1 year ago
It also happened at a customer, when changing the time/date of an upcoming campaign, and resaving it
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5078
Updated by Anonymous about 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder:rudder|59edca8ae5b367986aeab8c7a4c6cbf6bdf28e3c.
Updated by Vincent MEMBRÉ about 1 year ago
- Project changed from 92 to Rudder
- Target version changed from 7.2 to 7.3.8
Updated by Alexis Mousset about 1 year ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.3.8 and 8.0.1 which were released today.
Actions