Actions
Bug #4559
closed
A rare race condition can lead to an error when looking at compliance while a deployment is in progress
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On very unlucky cases, it is possible to have a divide by 0 error on the display of rules.
It happens when we try to display the Rules pages while the expected reports are created (last step of deployment)
In the logs, it appears at
saving expected reports for xxxxxx
divide by 0 error in rulegrid
saving expected reports for yyyyy
Updated by Nicolas CHARLES over 11 years ago
- Status changed from New to Pending technical review
- Assignee set to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/459
PR is there
https://github.com/Normation/rudder/pull/459
Updated by Nicolas CHARLES over 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 4f1739e8f524f0a93cbbade0d143fcc8a84e8945.
Updated by Anonymous over 11 years ago
Applied in changeset a284544fd1f5a9371c92ee648d1ee4e71006d4e0.
Updated by Jonathan CLARKE
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.12, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-March/000083.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: https://www.rudder-project.org/site/get-rudder/downloads/
Actions