Actions
Bug #25380
closed
Score enum values are not updated before 8.1~rc1
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Very Small
Priority:
140
Name check:
To do
Fix check:
To do
Regression:
No
Description
In #24637 there have been changes to add the F and X values to the score enum type in the Postgres database, but the change were not really compatible from 8.1~beta to 8.1~rc up to now i.e. 8.2.
So some requests will not work when adding those values in a column, for example :
ERROR score - An error occurred while treating score event of type 'class com.normation.rudder.score.ComplianceScoreEvent': SystemError: error when inserting global score for node 'root''; cause was: org.postgresql.util.PSQLException: ERROR: invalid input value for enum score: "F" ->
We need to support adding F and X by doing a migration during boot.
Updated by Clark ANDRIANASOLO 3 months ago
- Related to Bug #24637: Improvements on score: F score, rework tooltip, improve messages added
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5844
Updated by François ARMAND 3 months ago
- Status changed from Pending technical review to Rejected
I'm absolutly sorry, I didn't see the pb was for things happening during beta/rc. I thought it was a change between 8.1 and 8.2. We don't support upgrade for developpement cycle (at least until RC, and RC it depends).
So this bug is not relevant, it's a developer problem, not a Rudder one.
Actions