Actions
Bug #4531
closedChanging Client-server communication configuration should trigger a promise regeneration
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When we change the "Require time synchronization between nodes and policy server" or "Use reverse DNS lookups on nodes to reinforce authentication to policy server", nothing happens (no promise regeneration, nothing)
So the changes are not taken into account, until a new promise generation, and nothing warns the users that the change is not automatic.
so we shall either warn the user that the change is not automatic, or deploy (if possible, not in workflow) automatically
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.3 to 2.9.4
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.4 to 2.9.5
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 2.9.5 to 2.9.6
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.9.6 to 2.9.7
Updated by Jonathan CLARKE over 10 years ago
- Target version changed from 2.9.7 to 150
Updated by Vincent MEMBRÉ over 10 years ago
- Target version changed from 150 to 2.10.4
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.10.4 to 2.6.18
Updated by Nicolas PERRON over 10 years ago
- Target version changed from 2.6.18 to 2.10.5
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.5 to 2.10.6
Updated by Matthieu CERDA about 10 years ago
- Target version changed from 2.10.6 to 2.10.7
Updated by Vincent MEMBRÉ about 10 years ago
- Target version changed from 2.10.7 to 2.10.8
Updated by Jonathan CLARKE almost 10 years ago
- Status changed from New to Rejected
This is no longer the case.
Actions