Activity
From 2015-01-22 to 2015-01-22
2015-01-22
- 20:12 Bug #6172: "Server cannot be contacted at this time" when tring to get Event Log details
- Applied in changeset commit:4fa399b1a57d1a8de692ae07dab0720acf1a4928.
- 20:12 Bug #6172 (Pending release): "Server cannot be contacted at this time" when tring to get Event Log details
- Applied in changeset commit:7caf7cf81d71f82647d99b86c167ff0acf319f44.
- 18:47 Bug #6172 (Pending technical review): "Server cannot be contacted at this time" when tring to get Event Log details
- https://github.com/Normation/rudder/pull/795
- 18:38 Bug #6172 (Released): "Server cannot be contacted at this time" when tring to get Event Log details
- We I click on a Event Log detail, I get the dreaded "Server cannot be contacted at this time"
The JS error is "Netwo... - 20:12 Revision 76a58407 (rudder): Merge pull request #795 from ncharles/bug_6172/server_cannot_be_contacted_at_this_time_when_tring_to_get_event_log_details
- Fixes #6172: "Server cannot be contacted at this time" when tring to get...
- 20:12 Revision 4fa399b1 (rudder): Merge pull request #795 from ncharles/bug_6172/server_cannot_be_contacted_at_this_time_when_tring_to_get_event_log_details
- Fixes #6172: "Server cannot be contacted at this time" when tring to get...
- 20:11 Bug #6021 (Pending technical review): Pending state is not managed as user could expect in changes only mode
- The last version on my branche is at last reviewable, so the PR: https://github.com/Normation/rudder/pull/796
I di... - 18:47 Revision f9dc07db (rudder): Fixes #6172: "Server cannot be contacted at this time" when tring to get Event Log details
- 18:47 Revision 7caf7cf8 (rudder): Fixes #6172: "Server cannot be contacted at this time" when tring to get Event Log details
- 17:41 Revision 854a82b4 (cf-clerk): Merge branch 'branches/rudder/2.11' into branches/rudder/3.0
- 17:36 Revision f1826dd7 (cf-clerk): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 16:59 Bug #6149: Update dependency between Rudder and ncf
- Applied in changeset packages:rudder-packages|commit:a629ccb745ec6619f984946efa984cf172f9e84c.
- 16:58 Bug #6149 (Pending release): Update dependency between Rudder and ncf
- Applied in changeset packages:rudder-packages|commit:e6f80e2ce8f447731156e9e00bc9810b69539086.
- 16:41 Bug #6149: Update dependency between Rudder and ncf
- Also, we need #6170 ! Updating to today, 16h40.
- 16:23 Bug #6149: Update dependency between Rudder and ncf
- Ok, after digging down into the bugs, after the merge of https://github.com/Normation/ncf/pull/168 should be ok !
- 15:30 Bug #6149: Update dependency between Rudder and ncf
- PR updated.
- 14:53 Bug #6149 (Pending technical review): Update dependency between Rudder and ncf
- PR is ready: https://github.com/Normation/rudder-packages/pull/595
- 14:48 Bug #6149: Update dependency between Rudder and ncf
- Since a new lil' bug has been found in the meantime ( #6168 ) , and merged today at 14:46, I'll update the dependency...
- 14:28 Bug #6149 (In progress): Update dependency between Rudder and ncf
- 16:58 Revision a629ccb7 (rudder-packages): Merge pull request #597 from Kegeruneku/bug_6149/int/6149_update_ncf_dependency
- Fixes #6149: Update ncf dependency to 201501221640
- 16:43 Bug #6171: There are no Not applicable reports anymore with ncf technique
- Applied in changeset clerk:commit:cc70469f1b3ba9e0182cee69afe7445df6654933.
- 16:43 Bug #6171 (Pending release): There are no Not applicable reports anymore with ncf technique
- Applied in changeset clerk:commit:b784b9b08e04083214e875d12deb7973e693f120.
- 16:25 Bug #6171 (Pending technical review): There are no Not applicable reports anymore with ncf technique
- https://github.com/Normation/cf-clerk/pull/69
- 16:01 Bug #6171: There are no Not applicable reports anymore with ncf technique
- The issue is that we define a wrong technique name before calling the bundle that make the reports for NA component
- 15:58 Bug #6171 (Released): There are no Not applicable reports anymore with ncf technique
- Following the change in the parent ticket, ncf doesn't report anymore Not Applicable because the bundlesequence is in...
- 16:43 Revision cc70469f (cf-clerk): Merge pull request #69 from ncharles/bug_6171/there_are_no_not_applicable_reports_anymore_with_ncf_technique
- Fixes #6171: There are no Not applicable reports anymore with ncf techni...
- 16:42 Revision e6f80e2c (rudder-packages): Fixes #6149: Update ncf dependency to 201501221640
- 16:24 Revision b784b9b0 (cf-clerk): Fixes #6171: There are no Not applicable reports anymore with ncf technique
- 16:16 Bug #6170: Rudder reports are made on ncf only if class "full_compliance" is set, but this class is defined only in Rudder 3.0
- Applied in changeset commit:0198c90531eb0a162d817fc96020371fd3333d1d.
- 16:16 Bug #6170 (Pending release): Rudder reports are made on ncf only if class "full_compliance" is set, but this class is defined only in Rudder 3.0
- Applied in changeset commit:1e951db0bf8dae1a0b0ce8c132b5a74efb275c07.
- 15:53 Bug #6170 (Pending technical review): Rudder reports are made on ncf only if class "full_compliance" is set, but this class is defined only in Rudder 3.0
- https://github.com/Normation/ncf/pull/168
- 15:49 Bug #6170 (Released): Rudder reports are made on ncf only if class "full_compliance" is set, but this class is defined only in Rudder 3.0
- With Rudder 2.10 or 2.11, ncf doesn't report anything, as it waits for class "full_compliance", that is never defined...
- 16:16 Revision 0198c905 (ncf): Merge pull request #168 from ncharles/bug_6170/dev/logger_rudder_dont_report
- Fixes #6170: change condition for reporting on logger_rudder
- 15:52 Revision 1e951db0 (ncf): Fixes #6170: change condition for reporting on logger_rudder
- 15:26 Bug #6169: Error management code is a bashism
- Applied in changeset packages:rudder-packages|commit:32d729ffecf15a1ca3091b1495f9ff8c762bd0ea.
- 15:26 Bug #6169 (Pending release): Error management code is a bashism
- Applied in changeset packages:rudder-packages|commit:34600fb109986b28793eb12ae5fc83edf4f073fb.
- 15:18 Bug #6169 (Pending technical review): Error management code is a bashism
- PR https://github.com/Normation/rudder-packages/pull/596
- 15:17 Bug #6169 (In progress): Error management code is a bashism
- 15:16 Bug #6169 (Released): Error management code is a bashism
- The error management code introduced in #5866 is a bashism.
Since we are on the server, we can require bash to be ... - 15:26 Revision 32d729ff (rudder-packages): Merge pull request #596 from peckpeck/bug_6169/error_management_code_is_a_bashism
- Fixes #6169: Error management code is a bashism
- 15:17 Revision 34600fb1 (rudder-packages): Fixes #6169: Error management code is a bashism
- 14:45 Bug #6168: ncf API hooks fails because it uses bashism but declares using shell
- Applied in changeset packages:rudder-packages|commit:f3d3b13c7cd906ddcf29bb7e689ee800600c477a.
- 14:45 Bug #6168 (Pending release): ncf API hooks fails because it uses bashism but declares using shell
- Applied in changeset packages:rudder-packages|commit:d9eb17e41f36919a18a60c40cd5a2c2eacb62a8c.
- 14:43 Bug #6168 (Pending technical review): ncf API hooks fails because it uses bashism but declares using shell
- https://github.com/Normation/rudder-packages/pull/594
- 14:40 Bug #6168 (Released): ncf API hooks fails because it uses bashism but declares using shell
- In http://www.rudder-project.org/redmine/issues/5866, we introduced error handling; however it relies on bashism, whi...
- 14:45 Revision f3d3b13c (rudder-packages): Merge pull request #594 from ncharles/bug_6168/ncf_api_hooks_fails_because_it_uses_bashism_but_declares_using_shell
- Fixes #6168: ncf API hooks fails because it uses bashism but declares us...
- 14:43 Revision d9eb17e4 (rudder-packages): Fixes #6168: ncf API hooks fails because it uses bashism but declares using shell
- 11:49 Bug #6167 (Rejected): When we reduce the run interval of nodes, "no data" may be wrongly reported
- Imagine you have nodes with a run interval of interval=60min.
The node agent run at t0.
At t1 = t0+a few minu...
Also available in: Atom