Activity
From 2012-09-04 to 2012-09-04
2012-09-04
- 23:27 Revision 00e2b2bc (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Refs #2848 - Add cf-served.cf promise in the list of inputs of both policy servers and nodes... - 22:24 User story #2782 (Released): Use a real diff viewing for Directive modification event log
- Looks good to me! Thanks Jean.
- 17:20 User story #2782: Use a real diff viewing for Directive modification event log
- That seems ok.
Jon, I let you see with Jean for the look'n'feel you want for the result. - 15:02 User story #2782: Use a real diff viewing for Directive modification event log
- The result :
!diff_only_background_lighter.png! - 22:22 Bug #2354 (Discussion): Error not displayed on archive screen
- François ARMAND wrote:
> That seems to be working, and so if no error are displayed at some time, it should be consi... - 17:10 Bug #2354 (Released): Error not displayed on archive screen
- That seems to be working, and so if no error are displayed at some time, it should be considered as an other bug (for...
- 19:04 Bug #2822 (In progress): A rudder upgrade does not add a default role to users in rudder-users.xml if they were admins in 2.3
- the last commit need a condition to not upgrade users which could contain "role" (even if should not happends from a ...
- 19:03 Revision c05a12bf (rudder-packages): Refs #2822 - Add conditions in rudder-upgrade script to upgrade users from Rudder 2.3 (and be administrator of Rudder)
- 18:52 Revision e00c58e7 (rudder): Refs #2772 : renaming method for the PI grid in popup so that it has a name matching what it does
- 18:43 Bug #2772: The popup with the PI list on the CR page doesn't allow for more than 10 PIs
- Well, that does what is expected. But leaving the method name as it is when it doesn't do what it says is akward....
- 18:13 Bug #2810: Bad reference to scala-tools repos in maven files
- Hum, I'm a bit surprised. Shouldn't you replace the urls rather than simply removing them ?
- 18:05 Bug #2859 (Released): The ajax loader spinner is not transparent
- This seems valid, thank you
- 17:53 Bug #2607: Launching Cfengine Community cf-serverd... make an error
- Ha. I've been able to reproduce this bug.
It happens when the promises are invalid AND the cfengine databases (BDB) ... - 17:06 Bug #2607 (In progress): Launching Cfengine Community cf-serverd... make an error
- 17:41 Bug #2844 (Pending technical review): Rudder sysadmin log file depends on the user locale which restart the jetty
- Applied in changeset commit:3527adaff61f109127a2ec8ea9a821f2959a4a54.
- 17:40 Revision 3527adaf (rudder-packages): Fixes #2844 - Avoid jetty to change locale in its logs
- 17:27 Bug #2848 (Released): The initial promises on a node have a disturbing error message about rudder-passwords.conf
- Looks good, thanks.
- 17:24 Bug #2848 (Pending technical review): The initial promises on a node have a disturbing error message about rudder-passwords.conf
- Jonathan CLARKE wrote:
> Nicolas PERRON wrote:
> > Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf517... - 13:30 Bug #2848 (Discussion): The initial promises on a node have a disturbing error message about rudder-passwords.conf
- Nicolas PERRON wrote:
> Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf5175581.
This looks fine, ex... - 12:54 Bug #2848 (Pending technical review): The initial promises on a node have a disturbing error message about rudder-passwords.conf
- Applied in changeset commit:a8de663138a0b18deebed8d2cf9bb14bf5175581.
- 17:23 Revision 84b31c67 (rudder-techniques): Refs #2848 - Add cf-served.cf promise in the list of inputs of both policy servers and nodes
- 17:21 Bug #2851 (Released): Viewing Directive modification diff in the event logs is too ugly
- I closed that one, the relevant description is in #2782.
- 15:02 Bug #2851 (Pending technical review): Viewing Directive modification diff in the event logs is too ugly
- The commit is in #2782.
- 14:41 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Jean VILVER wrote:
> Jonathan CLARKE wrote:
> > [...]
> > OK, I see what you mean. How about we keep the black tex... - 14:38 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Another one, but with lighter colors.
- 14:33 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- that's ok for me, thank you
- 14:29 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Jonathan CLARKE wrote:
> [...]
> OK, I see what you mean. How about we keep the black text, but use the softer back... - 12:25 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Nicolas CHARLES wrote:
> Jonathan CLARKE wrote:
> > Thanks for looking into this Jean.
> >
> > Without hesitatio... - 12:11 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Jonathan CLARKE wrote:
> Thanks for looking into this Jean.
>
> Without hesitation, I prefer diff_option_by_defau... - 12:05 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- Thanks for looking into this Jean.
Without hesitation, I prefer diff_option_by_default.png. The background colour ... - 12:01 Bug #2851: Viewing Directive modification diff in the event logs is too ugly
- I prefer diff_only_background_differences.png most !But I'm not Jon :)
- 12:00 Bug #2851 (Discussion): Viewing Directive modification diff in the event logs is too ugly
- I have 3 other solutions, see screenshots attached. What do you think Jon ?
- 17:15 Bug #2836 (Released): Problem layout in 2.4 documentation
- That seems to work, thanks !
- 17:10 Revision cf9c5c44 (rudder): add title to popup
- 16:44 Bug #2826: The very first display of a node fails
- François ARMAND wrote:
> Do all the "lazy" really buy us something ? I'm not at ease with them, I don't see why we s... - 16:28 Bug #2826: The very first display of a node fails
- Do all the "lazy" really buy us something ? I'm not at ease with them, I don't see why we should have them, and so I ...
- 16:25 Bug #2860: priority does not appear to have an effect for directives derived from multi-instance techniques
- Michael, I've just pushed a patch that should correct your problem. If everything goes right, you should have nightly...
- 16:21 Bug #2860 (Pending technical review): priority does not appear to have an effect for directives derived from multi-instance techniques
- Applied in changeset commit:f2570bba8bc6e4f8415ceed0758d2be8ab8eabc2.
- 15:12 Bug #2860: priority does not appear to have an effect for directives derived from multi-instance techniques
- Ha, this is an interesting bug. We make sure several time that the order is correct, but several time we pipe the dat...
- 14:48 Bug #2860: priority does not appear to have an effect for directives derived from multi-instance techniques
- Indeed, the order doesn't seem to be respected. I'm checking what could go wrong
Thank you Michael - 14:44 Bug #2860: priority does not appear to have an effect for directives derived from multi-instance techniques
- 13:39 Bug #2860 (Released): priority does not appear to have an effect for directives derived from multi-instance techniques
- This is on Rudder 2.4 beta3
According to the tooltip of Priority field in directive settings, for multi-instance t... - 16:20 Revision f2570bba (cf-clerk): Fixes #2860 : Enforce the ordering of directives when writing promises
- 16:13 Bug #2835 (Released): Rudder 2.4.0~beta3 fails to install Rudder server at rudder-reports stage with error message about "connections on Unix domain socket"
- Nicolas PERRON wrote:
> Matthieu or Jon, could you review the last commit (3ee97fb9b3117b1a348bfa38f8afb64d0d3677a1)... - 16:04 Bug #2835 (Pending technical review): Rudder 2.4.0~beta3 fails to install Rudder server at rudder-reports stage with error message about "connections on Unix domain socket"
- Matthieu or Jon, could you review the last commit (3ee97fb9b3117b1a348bfa38f8afb64d0d3677a1), please ?
- 16:03 Bug #2835 (New): Rudder 2.4.0~beta3 fails to install Rudder server at rudder-reports stage with error message about "connections on Unix domain socket"
- This bug has not been fixed
- 14:58 Revision deca9236 (rudder): Refs #2782 Improve Directive diff in Events log
- 14:58 Revision b04338f7 (rudder): Refs #2782 Improve Directive diff in Events log
- 14:31 Bug #2187 (Rejected): If a new version PT is present on the filesystem, but not loaded in Rudder, there are error on display
- This bug is very old, and I couldn't reproduice it.
Hence, I reject it - 08:27 Bug #2187 (Discussion): If a new version PT is present on the filesystem, but not loaded in Rudder, there are error on display
- Nicolas, can you still reproduce this bug?
- 12:53 Revision a8de6631 (rudder-techniques): Fixes #2848 - Change inputs of promises.st from initial-promises in order to be dynamic
- 11:07 Revision 3ee97fb9 (rudder-packages): Refs #2835 - Remove a redirection on a while loop in rudder-reports postinst which doesn't work with sh on Debian
- 10:52 Bug #2719: Can't enter a reason for creating, cloning or deleting a group
- Jean VILVER wrote:
> Jon, can you describe the workflow that you want when creating and cloning a group?
I sugges... - 10:18 User story #2791: When a node is accepted, an error or a warning should be displayed if its hostname or ip is already present
- Jean VILVER wrote:
> I'm thinking to put the duplicate node (with a hostname or a IP already present) in the Accept ... - 08:27 Bug #2188: Reloading the Policy Template Library doesn't always reload everything
- This looks like it may be related to #2613
- 08:26 User story #2132: Improve process for upgrading techniques
- 08:18 Bug #2854: Service started at boot check fails on Red Hat
- Thanks for that info. Sorry I didn't reply earlier, I hadn't seen your response... /me slaps forehead.
This does i... - 08:09 Revision 77a91d58 (rudder-packages): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
- * branches/rudder/2.3:
Fixes #2857 - Consider logback.xml as a config file in rudder-webapp package - 08:08 Revision e3443be5 (rudder-techniques): Merge branch 'branches/rudder/2.4'
- * branches/rudder/2.4:
Add test in check-techniques.sh to make sure that the deprected body classes classes_trigger...
Also available in: Atom