Activity
From 2015-03-12 to 2015-03-12
2015-03-12
- 21:09 Bug #6403 (Released): Postgresql misconfigured when not the default distrib package (ex: Centos 6 with Postgresql 9.3 from pgfoundry.org)
- Just fyi...
I was attempting to install rudder-reports to Centos 6x with Postgresql 9.3 from the pgdg repository h... - 19:09 Revision 9d56b14c (rudder-techniques): Merge pull request #642 from ncharles/bug_6389/enforce_file_content_technique_doesn_t_properly_migrate_lines_from_outside_the_zone_to_the_zone
- Fixes #6389: Enforce file content Technique doesn't properly migrate lin...
- 19:03 User story #1174: It is impossible to use Rudder in an environment without a complete DNS infrastructure
- I feel that this has already been, at least, partly solved. Can you update the ticket François if you agree ? Thanks :)
- 18:42 Bug #6382: Random sprurious "Unknown" reports in the Web Interface
- Ok, from what I understand this happened when the syslog configuration was invalid, and caused reports to be sent mul...
- 18:42 Bug #6381: File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- Applied in changeset rudder|commit:11a7bb1d9b7bf13a55d0e5c3d56ec9c598a630f5.
- 18:42 Bug #6381 (Pending release): File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- Applied in changeset rudder|commit:b1f71497395d5c5b9de2d4f435e7cda305bb7ed8.
- 15:47 Bug #6381: File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- New pull request: https://github.com/Normation/rudder/pull/837
- 15:17 Bug #6381: File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- Adding /var/log/rudder/core/rudder-webapp.log which is exactly in the same position as .../compliance/non-compliant-r...
- 14:36 Bug #6381 (Pending technical review): File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- 14:32 Bug #6381: File /var/log/rudder/{compliance/non-compliant-reports.log, core/rudder-webapp.log} are not correctly rotated
- The chosen solution is to use the default time rolling pattern, so that we are switching from a non working solution ...
- 18:41 Revision 02994780 (rudder): Merge pull request #837 from fanf/bug_6381/file_var_log_rudder_compliance_non_compliant_reports_log_is_not_correctly_rotated
- Fixes #6381: File /var/log/rudder/compliance/non-compliant-reports.log is not correctly rotated
- 18:41 Revision 11a7bb1d (rudder): Merge pull request #837 from fanf/bug_6381/file_var_log_rudder_compliance_non_compliant_reports_log_is_not_correctly_rotated
- Fixes #6381: File /var/log/rudder/compliance/non-compliant-reports.log is not correctly rotated
- 18:41 Revision 9009a24d (rudder-techniques): Merge pull request #643 from fanf/bug_6385/remove_var_log_rudder_compliance_non_compliant_reports_log_rotation_from_logrotate
- Fixes #6385: Remove /var/log/rudder/compliance/non-compliant-reports.log rotation from logrotate
- 18:10 Bug #6402: Rudder login page doesn't appear just after the webapp has been started
- Applied in changeset rudder|commit:2849979413e3c9c3195734e20426d57da4b9a858.
- 18:10 Bug #6402 (Pending release): Rudder login page doesn't appear just after the webapp has been started
- Applied in changeset rudder|commit:0ed0c60e32d20f4e72ac65806e9a7210b59cc161.
- 18:07 Bug #6402 (Pending technical review): Rudder login page doesn't appear just after the webapp has been started
- PR https://github.com/Normation/rudder/pull/838
- 18:07 Bug #6402 (In progress): Rudder login page doesn't appear just after the webapp has been started
- 18:06 Bug #6402 (Released): Rudder login page doesn't appear just after the webapp has been started
- If you restart jetty, apache and the browser don't seem to notice that it has finished
- 18:09 Revision 40c920f6 (rudder): Merge pull request #838 from peckpeck/bug_6402/rudder_login_page_doesn_t_appear_just_after_the_webapp_has_been_started
- Fixes #6402: Rudder login page doesn't appear just after the webapp has been started
- 18:09 Revision 28499794 (rudder): Merge pull request #838 from peckpeck/bug_6402/rudder_login_page_doesn_t_appear_just_after_the_webapp_has_been_started
- Fixes #6402: Rudder login page doesn't appear just after the webapp has been started
- 18:07 Revision 9e49cf89 (rudder): Fixes #6402: Rudder login page doesn't appear just after the webapp has been started
- 18:07 Revision 0ed0c60e (rudder): Fixes #6402: Rudder login page doesn't appear just after the webapp has been started
- 18:02 Bug #6399: On debian based system, link ncf-api-virtualenv apache conf is not created
- Applied in changeset rudder-packages|commit:fae8732be59e3da0ae54c1c845325d66163bd983.
- 18:02 Bug #6399 (Pending release): On debian based system, link ncf-api-virtualenv apache conf is not created
- Applied in changeset rudder-packages|commit:b92e6e1b3650ac649ca231bcbe915b4d133dcef3.
- 16:57 Bug #6399 (Pending technical review): On debian based system, link ncf-api-virtualenv apache conf is not created
- PR is radis: https://github.com/Normation/rudder-packages/pull/631
- 12:41 Bug #6399 (Released): On debian based system, link ncf-api-virtualenv apache conf is not created
- After a nightly install of 3.0.3/2.11.9 nightly, I cannot access the technique editor
I got a 'Not Found' error
- 18:02 Revision fae8732b (rudder-packages): Merge pull request #631 from Kegeruneku/bug_6399/int/6399_do_not_set_ncfapivirtualenv_symlink_as_config
- Fixes #6399: Correct ncf-api-virtualenv conffiles on Debian packages
- 18:01 User story #26 (New): Allows an update of the inventories from the API
- If it's updating inventories via API rest, it is not done (and surely not #5848)
We can only export our data, not ... - 17:18 User story #26 (Rejected): Allows an update of the inventories from the API
- Rejecting, as it has already been done in #5843 :)
- 17:55 Bug #6390 (Pending technical review): Use new data/error fields in ncf-builder
- PR here: https://github.com/Normation/ncf/pull/178
- 17:40 User story #6401 (Released): Have a pretty 404 Page, explaining what is wrong
- We should have a pretty 404 page that says that Rudder has been stopped or is in maintenance mode.
- 16:56 Revision b92e6e1b (rudder-packages): Fixes #6399: Correct ncf-api-virtualenv conffiles on Debian packages
- 16:37 Revision 6dc298dc (ncf): Fixes #6376: Properly catch all error in ncf api
- 16:32 User story #6400 (Resolved): Harmonize the logrotate files in the Techniques/Initial promises
- The logrorate files are not standardized in initial promises/techniques
Some have delay compress, other don't, namin... - 15:47 Bug #6385 (Pending technical review): Remove /var/log/rudder/compliance/non-compliant-reports.log rotation from logrotate
- 15:40 Revision 23c84649 (rudder-techniques): Fixes #6385: Remove /var/log/rudder/compliance/non-compliant-reports.log rotation from logrotate
- 15:27 Revision 8fb8e9d4 (rudder): Fixes #6381: File /var/log/rudder/compliance/non-compliant-reports.log is not correctly rotated
- 15:27 Revision b1f71497 (rudder): Fixes #6381: File /var/log/rudder/compliance/non-compliant-reports.log is not correctly rotated
- 14:36 Bug #6396: Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- Reverted in 3.0 (cfengine 3.6.3) since this bug only affects 2.11 (cfengine 3.6.0) by commit rudder-packages|commit:b...
- 12:20 Bug #6396: Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- Applied in changeset rudder-packages|commit:0e7c05b93091ebd0e37441ebace08df401c555c8.
- 12:20 Bug #6396 (Pending release): Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- Applied in changeset rudder-packages|commit:63987582ef2f32d40f455f0d624d9621572eda76.
- 12:16 Bug #6396 (Pending technical review): Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- PR https://github.com/Normation/rudder-packages/pull/630
- 11:35 Bug #6396 (Released): Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- On AIX, using parsestringarrayidx with more than 2000 read bytes, the agent may hang, or cf-promises may fail.
Iss... - 14:32 Revision b228eaec (rudder-packages): Revert "Fixes #6396: Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)"
- This reverts commit 63987582ef2f32d40f455f0d624d9621572eda76.
This original patchs only applies on branch 2.11 - 14:20 Bug #6375 (Rejected): Missing node in Rules Manager
- Rejecting, can not be reproduced + read the previous comments
- 13:43 Bug #6375: Missing node in Rules Manager
- Ok no problem !
Thanks again :-) - 11:55 Bug #6375: Missing node in Rules Manager
- Oh, that's great, thanks!
I think we can build the following scenario:
- there was a DNS problem, making the no... - 10:24 Bug #6375: Missing node in Rules Manager
- After kill every process one more time and execute rudder agent update then inventory...
It's working :-)
Some we... - 14:18 Bug #6373: Rudder 3.0 ncf editor chrome, clickjacking alert
- @fanf: I didn't change the header. I'm not sure if the syntax is the same in Apache 2.4 and where to put it.
@Vinc... - 13:10 Revision f6ba01fe (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 12:32 User story #6398 (Rejected): "Cloning" generic methods
- Sometimes, we want to add a new action in an existing Technique, and this action would be very much like another one,...
- 12:19 Revision 0e7c05b9 (rudder-packages): Merge pull request #630 from peckpeck/bug_6396/using_parsestringarrayidx_on_aix_leads_to_agent_hanging_up_or_promises_validation_errors_only_on_2_11
- Fixes #6396: Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- 12:16 Revision 63987582 (rudder-packages): Fixes #6396: Using parsestringarrayidx on AIX leads to agent hanging up or promises validation errors (only on 2.11)
- 12:05 Bug #6389 (Pending technical review): Enforce file content Technique doesn't properly migrate lines from outside the zone to the zone
- Ok, everything was fine, it was an issue on the AIX ticket #6396
- 12:05 User story #1621 (Discussion): Generate documentation for std lib Techniques from their source code
- I am not ok with you Matthieu, The goal of this is to always have an up to date documentation of all available techni...
- 11:17 User story #1621 (Rejected): Generate documentation for std lib Techniques from their source code
- I feel that ncf and a much better presentation of Techniques in the current UI makes this issue obsolete. Feel free t...
- 11:54 Bug #6397 (Rejected): Moving generic method in ncf-builder is painful
- When we have large technique (30 generic method), adding a generic method and putting it into the right position is p...
- 11:47 Bug #6265 (Released): The Rudder Documentation fails to build due to extra "====" blocks
- This bug has been fixed in Rudder 3.0.1, which was released on 2015/02/23
* Announcement "3.0":http://www.rudder-... - 11:47 Bug #6265: The Rudder Documentation fails to build due to extra "====" blocks
- This was introduced by #6241 and is fixed in 3.0.1
- 11:47 Bug #3574: Using checkgenericfilecontent Technique with 16Ko content leads to error
- Updated title to express the current state of the limitation
- 11:37 Bug #3574 (New): Using checkgenericfilecontent Technique with 16Ko content leads to error
- This was reverted by commit:6f5cfeae and it's still open
- 11:21 Bug #3377: rudder-inventory-ldap package provides openldap libraries
- The revert commit was commit:ea0a625b
- 11:11 Bug #3377 (New): rudder-inventory-ldap package provides openldap libraries
- The fix was reverted, you can ignore my last comment, I will add the revert commit to that issue
- 11:09 Bug #3377 (Released): rudder-inventory-ldap package provides openldap libraries
- From commit date (27/04/2012) and branch (2.3) this was merged and released with versions 2.3.12, 2.4.5 2.5.3 and 2.6...
- 10:42 User story #2273 (New): Technique 'Name resolution': We should be able to prevent dhclient to modify /etc/resolv.conf
- 10:41 User story #2273 (Discussion): Technique 'Name resolution': We should be able to prevent dhclient to modify /etc/resolv.conf
- All the three commits linked to that issue are wrong they are for issue #2534.
This issue is not fixed and need to... - 10:05 Bug #6377: Hostname changed to localhost - DNS configuration problem
- It was 2.10 to 3.0.1.
Also available in: Atom