Bug #2188
closed
Reloading the Policy Template Library doesn't always reload everything
Added by Nicolas CHARLES over 12 years ago.
Updated over 11 years ago.
Category:
Web - Config management
Description
I've came across a case when I had a 2.1 version of a policy template in the file system, and commited in the git, but not present in the LDAP tree. Reloading or changing the git by commiting new pt didn't make it appear in it.
The only workaround was to explicitely make a commit in the PT
- Target version changed from 2.3.6 to 2.3.7
- Target version changed from 2.3.7 to 2.3.8
- Target version changed from 2.3.8 to Ideas (not version specific)
- Assignee set to François ARMAND
- Target version changed from Ideas (not version specific) to 2.4.0~rc1
This looks like it may be related to #2613
- Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Ha. I tried to reproduce this, without success
- Target version changed from 2.4.0~rc2 to 2.4.0~rc1
I can't reproduce this bug too.
Francois, Nicolas, do you have any idea about how we could do that ?
I created new "techniques" or new "version" of actual techniques, but when commited, reload display them...
- Status changed from New to Discussion
If no one can reproduce this bug, we should close that ticket
François, Jon, what should we do with this ticket ? Reject it ?
- Status changed from Discussion to Rejected
Yes, I reject that one as "not reproducible, even by the reporter who is also a dev on that part of Rudder and tried dirty tricks with the code below his eyes to try to reproduce it".
Also available in: Atom
PDF
Updated by 
Updated by Nicolas PERRON 
Updated by 
Updated by 
Updated by