Actions
Bug #18711
closed
rollback error when trying to revert allowed networks: "event log xxx don't have a matching commitId"
Bug #18711:
rollback error when trying to revert allowed networks: "event log xxx don't have a matching commitId"
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Files
Updated by François ARMAND over 5 years ago
- Related to Bug #17720: If a second rollback starts when a first is processing, system group/technique may be lost added
Updated by François ARMAND over 5 years ago
- Subject changed from rollback error for all event: "event log xxx don't have a matching commitId" to rollback error when trying to revert allowed networks: "event log xxx don't have a matching commitId"
- Status changed from New to Rejected
OK. So actually, it's "normal". Not user-normal, but "technically normal".
Allowed networks are stored in a system directive. And system directives are not persisted in git. So there is no commit to revert to.
I'm closing it, BUT: we really need to change that. Allowed networks are a config as other, and they should not be directly in a system technique.
Updated by François ARMAND over 5 years ago
- Related to Architecture #18730: Move allowed network data to settings added
Actions