When Lexorank duplicate rank problem is fixed through REST API, it does not clear the failure reason

Issue Summary

This is reproducible on Data Center: yes

Steps to Reproduce

1. Deliberately update the database so that two rows in the "AO_60DB71_LEXORANK" table have the same Rank value. 
2. Run the Lexorank check in the UI.  It will fail on the last test - the duplicate rank test. 
3. Follow the https://confluence.atlassian.com/jirakb/how-to-fix-duplicate-rank-values-for-a-rank-field-779159224.html to get the results of the integrity checks from the endpoint /rest/greenhopper/1.0/lexorank/integrity.  The last check will fail and list the failure reason with the duplicated value.  
4. Run the REST API call via Postman to fix the duplicate rank. 
5. Run the integrity check again from the endpoint   /rest/greenhopper/1.0/lexorank/integrity.  

Expected Results

It will have fixed the Lexorank duplicate and clear the failure reason. 

Actual Results

The duplicate rank issue is fixed and the test passes but it still lists a failure reason:

"name":"Duplicate ranks check","description":"Checks if there are any duplicate rank values for a rank field.","passed":true,"failureReason":"Detected duplicate ranks for rank field 10100 : {0|i0001j:=2}","fatal":false  

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available