Activity - Rudder - Issue Tracker

Activity

From 2016-08-09 to 2016-08-09

2016-08-09

18:01 Bug #8829 (Pending technical review): New method calls are considered valid, although they are empty which leads to error when validated via API: PR https://github.com/Normation/ncf/pull/418 Vincent MEMBRÉ
17:35 Bug #8829 (In progress): New method calls are considered valid, although they are empty which leads to error when validated via API: Vincent MEMBRÉ
17:29 Bug #8829 (Released): New method calls are considered valid, although they are empty which leads to error when validated via API: When adding a new method in a Technique in ncf editor, without
Form is initialized with 'undefined' value which a... Vincent MEMBRÉ
18:01 Revision 44fd46bd (ncf): Fixes #8829: New method calls are considered valid, although they are empty which leads to error when validated via API: Vincent Membré
16:50 Bug #8826 (Pending release): Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Applied in changeset commit:de7730486e047d47cd79b503d7c721cb79491d6a. Vincent MEMBRÉ
12:26 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): On those which are saved in Technique editor after patch:... Dmitry Svyatogorov
12:23 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): If I read my history correctly:
Rudder 3.2.5, generates log_rudder with 2 parameters => Wrong, corrected here
Rud... Vincent MEMBRÉ
12:17 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Do your other rudder_reporting.cf file contains *log_rudder* with 2 parameters, *log_rudder* with 4 parameters or *lo... Vincent MEMBRÉ
12:05 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Ok, the patch works, but all user techniques have to be saved again (to implement ncf_rudder.py).
So, there although... Dmitry Svyatogorov
11:22 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): ... Dmitry Svyatogorov
11:18 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Here is the patch:
To apply it on your server Rudder:... Vincent MEMBRÉ
11:07 Bug #8826 (Pending technical review): Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): PR https://github.com/Normation/ncf/pull/416 Vincent MEMBRÉ
11:06 Bug #8826 (In progress): Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Vincent MEMBRÉ
11:05 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): I'll give you a patch to fix how those files are generated Vincent MEMBRÉ
11:04 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): as an easy workaround, you can modify that file /var/rudder/share/42a34eff-213c-42fd-abf7-6fef5cca8d27/rules.new/cfen... Vincent MEMBRÉ
10:57 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): I'll improve the error message and also the UI checks! Vincent MEMBRÉ
10:55 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Thanks, so you kept blank fields in some 'command execution result' and you got an error on saving ?
The error is... Vincent MEMBRÉ
10:53 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Found the first issue (on logger arity), as stated in the error messages, it generate wrong bundle call for rudder_re... Vincent MEMBRÉ
10:49 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): TZ_UTC is old technique (but that I tried to resave).
Now I try to create completelly new technique as a hot workaro... Dmitry Svyatogorov
10:43 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Hello Dmitry, thanks for reporting this issue! and sorry about this ...
What is the version of the ncf package in... Vincent MEMBRÉ
10:39 Bug #8826: Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): Moreover: the new technique creation is now broken at all:... Dmitry Svyatogorov
10:33 Bug #8826 (Released): Reporting generated for rudder techniques has broken reporting promises ( log with 2 params ): After upgrade from 3.2.4 to 3.2.5 (ubuntu 14.04, dpkg from rudder repo, "apt-get upgrade"), each user technique broke... Dmitry Svyatogorov
16:50 Revision 65f74149 (ncf): Merge branch 'bug_8826/technique_editor_is_broken_in_rudder_3_2_5_pr': Normation GIT merger
16:39 Revision de773048 (ncf): Fixes #8826: Technique Editor is broken in Rudder 3.2.5: Vincent Membré
15:50 Architecture #8759: Document how to build a standard agent to allow easier usage by external build systems or for new platforms: Florian Heigl wrote:
> Please note that what's in master is not helping anyone who wants to *use* rudder since that'... Jonathan CLARKE
14:06 Bug #8828 (Rejected): Bad font in the left frame of the webapp since 3.2.5: Since rudder 3.2.5, left side (tree) in the web looks ugly, because it implements some custom font instead of system ... Dmitry Svyatogorov
12:43 Bug #8825: crontab frequency does not support reserved string @reboot: petite coquille dans le changelog
le ticket peut etre clos
merci encore Jérémy HOCDÉ
12:15 Bug #8825: crontab frequency does not support reserved string @reboot: Jonathan CLARKE wrote:
> Oh, sorry, wait. No, that *is not* the right location. That is the distribution standard co... Jérémy HOCDÉ
11:58 Bug #8825: crontab frequency does not support reserved string @reboot: Jonathan CLARKE wrote:
> Thanks for the report Jérémy.
>
> The allowed strings are defined by a (rather long) reg... Jérémy HOCDÉ
11:54 Bug #8825: crontab frequency does not support reserved string @reboot: Oh, sorry, wait. No, that *is not* the right location. That is the distribution standard copy of Techniques. Please d... Jonathan CLARKE
11:53 Bug #8825: crontab frequency does not support reserved string @reboot: No, that's the correct location, but this is a git repository. After making changes you need to git add <file> && git... Jonathan CLARKE
11:47 Bug #8825: crontab frequency does not support reserved string @reboot: Jérémy HOCDÉ wrote:
> Hello
>
> is it possible to add manually special prefixes into technique (file) "Cron daem... Jérémy HOCDÉ
11:31 Bug #8825: crontab frequency does not support reserved string @reboot: Thanks for the report Jérémy.
The allowed strings are defined by a (rather long) regex in https://github.com/Norma... Jonathan CLARKE
11:00 Bug #8825: crontab frequency does not support reserved string @reboot: Hello
is it possible to add manually special prefixes into technique (file) "Cron daemon configuration version 3.... Jérémy HOCDÉ
11:46 User story #8827 (Rejected): Per-user API keys: It would be a nice addition not to have all API keys stored at the same level but to have per-user API keys.
It co... Matthieu CERDA
11:45 User story #8071 (Pending release): Add 'Windows Server 2012 R2' as OS condition: Applied in changeset commit:e5ff6b3879a348f6df28df2d933beaffe8c48661. Vincent MEMBRÉ
11:38 User story #8071 (Pending technical review): Add 'Windows Server 2012 R2' as OS condition: PR https://github.com/Normation/ncf/pull/417 Vincent MEMBRÉ
11:36 User story #8071 (In progress): Add 'Windows Server 2012 R2' as OS condition: Vincent MEMBRÉ
11:45 Revision 692c9c87 (ncf): Merge branch 'v0.x': Normation GIT merger
11:38 Revision e5ff6b38 (ncf): Fixes #8071: Add 'Windows Server 2012 R2' as OS condition: Vincent Membré
11:32 Bug #8164 (Rejected): Compliance progress bar keeps scrolling: Thanks for confirming it now works, Alexandre. Closing this. Jonathan CLARKE

Also available in: Atom