Activity
From 2015-01-30 to 2015-01-30
2015-01-30
- 23:19 Bug #6214: Event log table cannot be opened on other pages than first one
- Applied in changeset commit:cd62e1806fc443e6c4654c5451c57ee5139e53ac.
- 23:19 Bug #6214 (Pending release): Event log table cannot be opened on other pages than first one
- Applied in changeset commit:b95ad9e7797e5d53945efdde7592f1c219c631b6.
- 22:58 Bug #6214 (Pending technical review): Event log table cannot be opened on other pages than first one
- PR https://github.com/Normation/rudder/pull/814
- 22:57 Bug #6214 (Released): Event log table cannot be opened on other pages than first one
- Since #5960 was merged in rc1, you cannot open details of event logs on a different page than the first one.
This ... - 23:19 Revision 0f4f8c42 (rudder): Merge pull request #814 from VinceMacBuche/bug_6214/event_log_table_cannot_be_opened_on_other_pages_than_first_one
- Fixes #6214: Event log table cannot be opened on other pages than first one
- 23:19 Revision cd62e180 (rudder): Merge pull request #814 from VinceMacBuche/bug_6214/event_log_table_cannot_be_opened_on_other_pages_than_first_one
- Fixes #6214: Event log table cannot be opened on other pages than first one
- 22:58 Revision 81e196e3 (rudder): Fixes #6214: Event log table cannot be opened on other pages than first one
- 22:58 Revision b95ad9e7 (rudder): Fixes #6214: Event log table cannot be opened on other pages than first one
- 20:03 Bug #6203: If I create a rule, the Rules table is not correctly refreshed, and I get a neverending "loading"
- So more information: it seems to happen with firefox 31, but not firefox 35.
- 19:58 Bug #6203: If I create a rule, the Rules table is not correctly refreshed, and I get a neverending "loading"
- I can't reproduce this one nor #6198.
So either were corrected at some point by something else (but nothing obviou... - 11:53 Bug #6203 (Released): If I create a rule, the Rules table is not correctly refreshed, and I get a neverending "loading"
- See screenshot
Step to reproduce:
Create a rule in the rule page.
Reloading the grid solves the issue - 19:58 Bug #6198: Server cannot be contacted at this time when deleting a Directive
- I can't reproduce this one nor #6203.
So either were corrected at some point by something else (but nothing obvio... - 19:52 Bug #6213: Bug in the LDAP query for getting Directive info
- Applied in changeset commit:b0fa6c02b51d35d24cebc243a4f84293206efd92.
- 19:52 Bug #6213 (Pending release): Bug in the LDAP query for getting Directive info
- Applied in changeset commit:7a3244955dc1fc7f6e9577652d0088a80aacb561.
- 19:42 Bug #6213 (Pending technical review): Bug in the LDAP query for getting Directive info
- https://github.com/Normation/rudder/pull/813
- 19:41 Bug #6213: Bug in the LDAP query for getting Directive info
- OK, so it's "JUST" a merge problem in 3.0, neither 2.10 nor 2.11 is affected by that one.
- 19:34 Bug #6213 (Released): Bug in the LDAP query for getting Directive info
- The parent commit introduced a bug in the way attributes for directive are retrieve in LDAP.
- 19:52 Revision 53dafc7a (rudder): Merge pull request #813 from fanf/bug_6213/bug_in_the_ldap_query_for_getting_directive_info
- Fixes #6213: Bug in the LDAP query for getting Directive info
- 19:52 Revision b0fa6c02 (rudder): Merge pull request #813 from fanf/bug_6213/bug_in_the_ldap_query_for_getting_directive_info
- Fixes #6213: Bug in the LDAP query for getting Directive info
- 19:41 Revision 9c1c34e5 (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 19:41 Revision ec8ec002 (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 19:40 Revision b59c6ed2 (rudder): Fixes #6213: Bug in the LDAP query for getting Directive info
- 19:40 Revision 7a324495 (rudder): Fixes #6213: Bug in the LDAP query for getting Directive info
- 19:39 Revision c4d6426d (rudder-packages): Refs #6212: mkdir the manpages directory on Debian during rudder-agent build, and use LD_LIBRARY_PATH to find LMDB (add -p to mkdir)
- 19:29 Bug #6211: If a run is not completed, compliance computation goes mad
- Applied in changeset commit:d9c114e79a4f1ae90f22ec18041b5b581d021e0f.
- 19:29 Bug #6211 (Pending release): If a run is not completed, compliance computation goes mad
- Applied in changeset commit:5b0e40ee257fd6727b77f031beb35dbcf7f09c62.
- 19:26 Bug #6211 (Pending technical review): If a run is not completed, compliance computation goes mad
- https://github.com/Normation/rudder/pull/812
- 18:31 Bug #6211 (Released): If a run is not completed, compliance computation goes mad
- If a run is not complete (i.e, we don't have the "end run" report), then the compliance computation for the node goes...
- 19:28 Revision 9bb4a03f (rudder): Merge pull request #812 from fanf/bug_6211/if_a_run_is_not_completed_compliance_computation_goes_mad
- Fixes #6211: If a run is not completed, compliance computation goes mad
- 19:28 Revision d9c114e7 (rudder): Merge pull request #812 from fanf/bug_6211/if_a_run_is_not_completed_compliance_computation_goes_mad
- Fixes #6211: If a run is not completed, compliance computation goes mad
- 19:23 Revision 27d5055c (rudder): Fixes #6211: If a run is not completed, compliance computation goes mad
- 19:23 Revision 5b0e40ee (rudder): Fixes #6211: If a run is not completed, compliance computation goes mad
- 19:11 Bug #6212: Manpage packaging should use LD_LIBRARY_PATH to prevent lmdb absence
- Applied in changeset packages:rudder-packages|commit:311a7d7a518b8c9b47bd590533d1dfaf81ea5854.
- 19:11 Bug #6212 (Pending release): Manpage packaging should use LD_LIBRARY_PATH to prevent lmdb absence
- Applied in changeset packages:rudder-packages|commit:5f44b7f1158d5e5024bebe5da42f4fc1030557e2.
- 19:08 Bug #6212 (Pending technical review): Manpage packaging should use LD_LIBRARY_PATH to prevent lmdb absence
- PR ready: https://github.com/Normation/rudder-packages/pull/611
- 19:03 Bug #6212 (Released): Manpage packaging should use LD_LIBRARY_PATH to prevent lmdb absence
- We should use LD_LIBRARY_PATH to tell CFEngine binaries where they can find LMDB and also on Debian create the manpag...
- 19:10 Revision d3e28858 (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 19:10 Revision 3ce8e85f (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 19:10 Revision 311a7d7a (rudder-packages): Merge pull request #611 from Kegeruneku/bug_6092/int/6212_mkdir_for_manpages_and_ld_library_path_during_generation
- Fixes #6212: mkdir the manpages directory on Debian during rudder-agent ...
- 19:06 Revision 5f44b7f1 (rudder-packages): Fixes #6212: mkdir the manpages directory on Debian during rudder-agent build, and use LD_LIBRARY_PATH to find LMDB
- 18:37 Bug #6205: Compliance computation on home page dashboard charts is incoherent regarding pending nodes
- There is a proposed version for the solution 3/ in pull request: https://github.com/Normation/rudder/pull/811
- 15:44 Bug #6205: Compliance computation on home page dashboard charts is incoherent regarding pending nodes
- I see no good way of doing it:
- if we count them as "error" (like now), then we see poor compliance, even if ever... - 12:03 Bug #6205 (Released): Compliance computation on home page dashboard charts is incoherent regarding pending nodes
- I updated my rules on my system, and most of my node are in "pending" state
However, the compliance is "poor", which... - 18:26 Bug #6162: Sorting Rule tables on "Compliance" and "Recent Changes" sort by name
- Yes, we have to create a specific sorting.
- 18:25 Bug #6167 (Discussion): When we reduce the run interval of nodes, "no data" may be wrongly reported
- Jon, what do you think about that ? Solution 3/ seems the only reasonnable, no ?
- 18:23 User story #2738: Handle big files payloads in the Enforce a file content Technique
- Could someone test it in Rudder 3.0 so that we know if it works (or update the bug on CFEngine side ?) Nicolas ?
- 18:22 Bug #5970: Rudder agent should have a no-color mode
- Can wait for one more relase.
- 18:21 Bug #5976: Rename meta techniques in the technique tree
- That's harder than it seems, especially for migration. Some thought have to be to not broke everything. Next version.
- 17:55 Revision 91790a22 (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 17:52 Revision 231652ee (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 17:44 Bug #6210: Debian build fails due to the fact debhelper cleans necessary files and tries to run wrong tests on generated shared libraries
- Applied in changeset packages:rudder-packages|commit:6f33858501fb1820035ea7f339fd0fb7b20a89cf.
- 17:44 Bug #6210 (Pending release): Debian build fails due to the fact debhelper cleans necessary files and tries to run wrong tests on generated shared libraries
- Applied in changeset packages:rudder-packages|commit:21e4de4a19798f80f670ecee05bea0a232553cdb.
- 17:42 Bug #6210 (Pending technical review): Debian build fails due to the fact debhelper cleans necessary files and tries to run wrong tests on generated shared libraries
- 17:40 Bug #6210 (Released): Debian build fails due to the fact debhelper cleans necessary files and tries to run wrong tests on generated shared libraries
- Since we added a BDB bundling procedure in rudder-inventory-ldap ( #5741 ), we need to do the same thing we did for r...
- 17:44 Revision 6f338585 (rudder-packages): Merge pull request #610 from Kegeruneku/bug_5741/int/6210_remove_dh_shlibdeps_and_prep_from_ldap_compilation
- Fixes #6210: Do not run dh_shlibdeps and dh_prep during rudder-inventory...
- 17:41 Revision 21e4de4a (rudder-packages): Fixes #6210: Do not run dh_shlibdeps and dh_prep during rudder-inventory-ldap build
- 17:39 Revision 51ae54d8 (rudder): Merge branch 'branches/rudder/3.0'
- 17:39 Revision 206a4271 (rudder): Merge branch 'branches/rudder/3.0'
- 17:38 Revision 01036d01 (rudder): Merge branch 'branches/rudder/3.0' of github.com:Normation/rudder into branches/rudder/3.0
- 17:38 Revision c0fa8eb5 (rudder): Merge branch 'branches/rudder/3.0' of github.com:Normation/rudder into branches/rudder/3.0
- 17:37 Revision 7c6147e9 (rudder): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- Conflicts:
rudder-core/src/main/scala/com/normation/rudder/repository/ldap/LDAPDirectiveRepository.scala
rudder-web... - 17:37 Revision 7c6c9d5a (rudder): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- Conflicts:
rudder-core/src/main/scala/com/normation/rudder/repository/ldap/LDAPDirectiveRepository.scala
rudder-web... - 17:00 Bug #6209: Some heartbeat are skipped in change only mode
- Applied in changeset commit:7b469a1bf67c3a94cad8618e45c576b453ef24d9.
- 17:00 Bug #6209 (Pending release): Some heartbeat are skipped in change only mode
- Applied in changeset commit:039c8a2a481e17c609633e7a3c6f7e60e3a2bf0d.
- 16:32 Bug #6209 (Pending technical review): Some heartbeat are skipped in change only mode
- https://github.com/Normation/rudder/pull/810
- 15:19 Bug #6209 (Released): Some heartbeat are skipped in change only mode
- We define the heartbeat as a number of minute, as run length * interval
So, if we have a run every 5 minutes, and wa... - 17:00 Revision 97b41c29 (rudder): Merge pull request #810 from ncharles/bug_6209/some_heartbeat_are_skipped_in_change_only_mode
- Fixes #6209: Some heartbeat are skipped in change only mode
- 17:00 Revision 7b469a1b (rudder): Merge pull request #810 from ncharles/bug_6209/some_heartbeat_are_skipped_in_change_only_mode
- Fixes #6209: Some heartbeat are skipped in change only mode
- 16:48 Revision 007df3db (rudder): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- Conflicts:
rudder-web/src/main/scala/com/normation/rudder/web/services/ReportDisplayer.scala - 16:48 Revision 4f3115b3 (rudder): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- Conflicts:
rudder-web/src/main/scala/com/normation/rudder/web/services/ReportDisplayer.scala - 16:31 Revision acc9b3a5 (rudder): Fixes #6209: Some heartbeat are skipped in change only mode
- 16:31 Revision 039c8a2a (rudder): Fixes #6209: Some heartbeat are skipped in change only mode
- 15:40 Bug #6207: Deleting a directive is VERY slow
- Applied in changeset commit:6e56daa7af62a4245b8e99d028a8dd1d4b863293.
- 15:40 Bug #6207 (Pending release): Deleting a directive is VERY slow
- Applied in changeset commit:1bf661c12d00e5b09701ecf002093133ef38ccb4.
- 15:00 Bug #6207 (Pending technical review): Deleting a directive is VERY slow
- https://github.com/Normation/rudder/pull/808
- 14:33 Bug #6207 (Released): Deleting a directive is VERY slow
- Even in the most simple case (a directive not used anywhere, on a fresh Rudder install), deleting a directive takes s...
- 15:40 Revision 3c34a495 (rudder): Merge pull request #808 from fanf/bug_6207/deleting_a_directive_is_very_slow
- Fixes #6207: Deleting a directive is VERY slow
- 15:40 Revision 6e56daa7 (rudder): Merge pull request #808 from fanf/bug_6207/deleting_a_directive_is_very_slow
- Fixes #6207: Deleting a directive is VERY slow
- 15:24 Revision f926e6ba (rudder): Merge branch 'branches/rudder/3.0'
- 15:24 Revision 0b37264f (rudder): Merge branch 'branches/rudder/3.0'
- 15:24 Revision 9ee3b181 (rudder): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 15:24 Revision 7ca6cf53 (rudder): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 15:24 Revision 4f60d123 (rudder): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 15:24 Revision 25d83781 (rudder): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 15:21 Bug #6208: Technique verison is still badly parsed (on one other decision path)
- Applied in changeset commit:04d920580c16e9a69c79b5ec1448c6ef397638a2.
- 15:21 Bug #6208 (Pending release): Technique verison is still badly parsed (on one other decision path)
- Applied in changeset commit:8f727687d841f12d3222b727fe3e11d2a09a6d51.
- 15:20 Bug #6208 (Pending technical review): Technique verison is still badly parsed (on one other decision path)
- https://github.com/Normation/rudder/pull/809
- 15:19 Bug #6208 (Released): Technique verison is still badly parsed (on one other decision path)
- Same as the parent, but from an other validation path.
- 15:20 Revision 75cae6b3 (rudder): Merge pull request #809 from fanf/bug_6208/technique_verison_is_still_badly_parsed_on_one_other_decision_path
- Fixes #6208: Technique verison is still badly parsed (on one other decision path)
- 15:20 Revision 04d92058 (rudder): Merge pull request #809 from fanf/bug_6208/technique_verison_is_still_badly_parsed_on_one_other_decision_path
- Fixes #6208: Technique verison is still badly parsed (on one other decision path)
- 15:19 Revision 744fac03 (rudder): Fixes #6208: Technique verison is still badly parsed (on one other decision path)
- 15:19 Revision 8f727687 (rudder): Fixes #6208: Technique verison is still badly parsed (on one other decision path)
- 15:12 Revision 9abd40d5 (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 15:12 Revision 2845e2da (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- Conflicts:
rudder-agent/SPECS/rudder-agent.spec - 15:09 Bug #6204 (Pending release): Debian builds fails due to a BDB bundling optimization
- Applied in changeset packages:rudder-packages|commit:1cb49ca368af3c11f736284093689adc4421658a.
- 15:03 Bug #6204 (Pending technical review): Debian builds fails due to a BDB bundling optimization
- PR is ready: https://github.com/Normation/rudder-packages/pull/609
- 14:07 Bug #6204 (In progress): Debian builds fails due to a BDB bundling optimization
- Hmmm, nope, it's not enough ! :(
Let's try again. - 12:04 Bug #6204: Debian builds fails due to a BDB bundling optimization
- Applied in changeset rudder-packages|commit:a5cf157ee4589dc783480c0245191fbbd692d6d6.
- 12:04 Bug #6204 (Pending release): Debian builds fails due to a BDB bundling optimization
- Applied in changeset rudder-packages|commit:a1d631ff31335338bbda67240980ecba5a46ea46.
- 12:00 Bug #6204 (Pending technical review): Debian builds fails due to a BDB bundling optimization
- PR is ready: https://github.com/Normation/rudder-packages/pull/607
- 11:53 Bug #6204 (Released): Debian builds fails due to a BDB bundling optimization
- We used to have on 3.0:...
- 15:09 Revision c9b9980d (rudder-packages): Merge pull request #609 from Kegeruneku/bug_6204/int/6204_revert_bdb_optimization
- Bug 6204/int/6204 revert bdb optimization
- 15:08 Bug #6092: rudder-agent-thin: missing /var/rudder/share/man
- Applied in changeset packages:rudder-packages|commit:fe7a9163d125ae5529944f773ba9a26b79ac8eee.
- 15:08 Bug #6092 (Pending release): rudder-agent-thin: missing /var/rudder/share/man
- Applied in changeset packages:rudder-packages|commit:c1e7bc635b602d1a0cc486a88da2099950a1e073.
- 15:08 Revision fe7a9163 (rudder-packages): Merge pull request #591 from Kegeruneku/bug_6092/int/6092_package_manpages_properly
- Fixes #6092: Package manpages properly
- 15:07 Revision c1e7bc63 (rudder-packages): Fixes #6092: Package manpages properly
- 15:00 Revision 1cb49ca3 (rudder-packages): Fixes #6204: Do not try to be too smart during BDB/OpenLDAP configure step (attempt #2)
- 14:51 User story #5622: Let the user choose between udp and tcp for syslog messages
- Here is a workaroudn for this issue, for rsyslog
On the rudder policy server, in /var/rudder/configuration-reposit... - 14:13 User story #5622: Let the user choose between udp and tcp for syslog messages
- Hey
Any update on this? The problem is still active and can cause lots of headaches if it is not fixed. - 14:45 Bug #6206: On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- Applied in changeset commit:9c8a951ae4377224be6c70f5fc61558c676a47de.
- 14:45 Bug #6206 (Pending release): On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- Applied in changeset commit:b720e5e222dd725f8e0b7217d171d310c54f32e0.
- 14:35 Bug #6206 (Pending technical review): On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- https://github.com/Normation/rudder/pull/807
- 14:20 Bug #6206 (Released): On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- Rudder component run every 5 minutes, and their reports are expected every 5 minutes
However, we do not overrride th... - 14:45 Revision 9ccc5cc8 (rudder): Merge pull request #807 from ncharles/bug_6206/on_policy_server_we_do_override_the_run_interval_and_the_expected_frequency_for_reports_but_the_generated_promises_don_t_override_the_heartbeat_frequency_causing_non_answer_in_the_webapp
- Fixes #6206: On policy server, we do override the run interval, and the ...
- 14:45 Revision 9c8a951a (rudder): Merge pull request #807 from ncharles/bug_6206/on_policy_server_we_do_override_the_run_interval_and_the_expected_frequency_for_reports_but_the_generated_promises_don_t_override_the_heartbeat_frequency_causing_non_answer_in_the_webapp
- Fixes #6206: On policy server, we do override the run interval, and the ...
- 14:40 Revision 668c2848 (rudder): Fixes #6207: Deleting a directive is VERY slow
- 14:40 Revision 1bf661c1 (rudder): Fixes #6207: Deleting a directive is VERY slow
- 14:33 Revision 28bcdb3c (rudder): Fixes #6206: On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- 14:33 Revision b720e5e2 (rudder): Fixes #6206: On policy server, we do override the run interval, and the expected frequency for reports, but the generated promises don't override the heartbeat frequency, causing non answer in the webapp
- 14:13 Bug #6202: If killall is not installed, cf-serverd can not reloaded during promise generation
- Applied in changeset rudder-packages|commit:91af739302c26ba55879f8380eb70df3ebb9d095.
- 14:13 Bug #6202 (Pending release): If killall is not installed, cf-serverd can not reloaded during promise generation
- Applied in changeset rudder-packages|commit:4e81068134843f3bd67d56375a2ed1be5ecbe7ae.
- 14:03 Bug #6202 (Pending technical review): If killall is not installed, cf-serverd can not reloaded during promise generation
- PR is ready: https://github.com/Normation/rudder-packages/pull/608
- 12:00 Bug #6202: If killall is not installed, cf-serverd can not reloaded during promise generation
- Oopps, wrong ticket !
- 11:59 Bug #6202 (Pending technical review): If killall is not installed, cf-serverd can not reloaded during promise generation
- PR is ready: https://github.com/Normation/rudder-packages/pull/607
- 11:51 Bug #6202 (Released): If killall is not installed, cf-serverd can not reloaded during promise generation
- When I regenerate promises, I get the following message on Debian...
- 14:13 Revision 91af7393 (rudder-packages): Merge pull request #608 from Kegeruneku/bug_6202/int/6202_change_serverd_reload_method
- Fixes #6202: Change the shell logic to choose between killall and kill/p...
- 14:10 Revision 8f405ac9 (rudder-packages): Revert "Fixes #6204: Do not try to be too smart during BDB/OpenLDAP configure step"
- This reverts commit a1d631ff31335338bbda67240980ecba5a46ea46.
- 14:00 Revision 4e810681 (rudder-packages): Fixes #6202: Change the shell logic to choose between killall and kill/pidof during cf-serverd reload
- 13:30 Revision 62381dfa (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 13:30 Revision e07abca6 (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 12:03 Revision a5cf157e (rudder-packages): Merge pull request #607 from Kegeruneku/bug_6204/int/6204_revert_bdb_optimization
- Fixes #6204: Do not try to be too smart during BDB/OpenLDAP configure st...
- 12:03 Revision a1d631ff (rudder-packages): Fixes #6204: Do not try to be too smart during BDB/OpenLDAP configure step
- 11:47 Bug #6103 (Rejected): Rhel7 build error, does not find LMDB
- Unable to reproduce, rejecting.
- 08:48 Revision 1919b7f4 (rudder-packages): Merge branch 'branches/rudder/3.0' of github.com:Normation/rudder-packages into branches/rudder/3.0
- 08:48 Revision dab536c1 (rudder-packages): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- Conflicts:
rudder-inventory-ldap/SOURCES/.dependencies
rudder-inventory-ldap/SPECS/rudder-inventory-ldap.spec
rudd... - 08:40 Revision 82167e7d (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- Conflicts:
rudder-inventory-ldap/SOURCES/Makefile
rudder-inventory-ldap/SPECS/rudder-inventory-ldap.spec
rudder-in...
Also available in: Atom