red x's on APRV 0 votes
Bug #980927 reported by
Monty Taylor
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Core Infrastructure |
Fix Released
|
Medium
|
Darragh Bailey |
Bug Description
Merged changesets are showing red x's in the Approved column for people who did not vote APPR.
Changed in openstack-ci: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Darragh Bailey (dbailey-k) |
tags: | added: gerrit |
Changed in openstack-ci: | |
status: | Triaged → Fix Released |
Changed in openstack-ci: | |
milestone: | none → folsom |
To post a comment you must log in.
it's due to 2 things
1) any user with permissions to set a score for a given category will have that score recorded in the DB on review publish even if it is 0 and no change from the starting value
2) gerrit makes any category score retrieved from the DB that matches the category min score with a rejected flag in the UI
Since the approved category in the openstack gerrit was created with (min, max) of (0, 1), this means any time a core reviewer reviews a change but isn't the person to set the 'Approved' category to 1, then it will appear in the UI that they rejected the changed.
options to solve:
1) change approved category to go from -1 to +1, so -1 becomes the new min
2) prevent default scores/no scores from being recorded
3) add an additional test along with matching minimum value
Option 1 only requires a DB update and a service restart
Other options require code changes to gerrit and require consideration as to whether they are acceptable upstream.