Activity
From 2014-03-12 to 2014-03-12
2014-03-12
- 23:25 Bug #4582: Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
- Bug #4604 has been created to track this
- 23:22 Bug #4582: Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
- good catch Alex !
- 23:15 Bug #4582: Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
- To be clear - the above typos are not in the policies but in the check-rudder-agent script.
- 23:09 Bug #4582: Last update detection is broken, causing cron remove cf_lock database and flood with emails every 5 minutes
- In addition it tries to delete the wrong file: ${CFE_DIR}/state/cf_lock.tdcb.lock (typo in the extension).
I would a... - 23:25 Bug #4604 (Released): Typo in the deletion of lock file if the promises are not updated
- There is a nasty typo in the file extension for the lock removed (introduced in #4494)
${CFE_DIR}/state/cf_lock.tdc... - 21:55 Bug #4442: cf-serverd looks up reverse DNS for ALL nodes at start up
- Applied in changeset policy-templates:commit:d1333e2fbe07559383f4bef85062ea5a7eda9afc.
- 21:55 Bug #4442 (Pending release): cf-serverd looks up reverse DNS for ALL nodes at start up
- Applied in changeset policy-templates:commit:e1f24ddb642344abe0d04da599ff01d98cea1b7b.
- 21:54 Revision d1333e2f (rudder-techniques): Merge pull request #303 from ncharles/bug_4442/dev/don_t_reverse_dns
- Fixes #4442: don't reverse lookup when skip identify is defined
- 21:50 User story #4603: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)
- Applied in changeset policy-templates:commit:d52203768d5810b612186d37bd08aaa972d875a2.
- 21:50 User story #4603 (Pending release): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)
- Applied in changeset policy-templates:commit:1554549b804c78f4910ea5b710dd2ad2d20b1aba.
- 20:43 User story #4603 (Pending technical review): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)
- PR available for review: https://github.com/Normation/rudder-techniques/pull/320/files
- 20:42 User story #4603 (Released): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)
- See #4602 - this is the same change but for relay servers.
- 21:50 Revision d5220376 (rudder-techniques): Merge pull request #320 from jooooooon/bug_4603/don_t_write_reports_to_linuxlog_log_winlog_log_and_extlinuxreport_log_since_they_are_already_all_in_all_log_for_relay_servers
- Fixes #4603: Don't write reports to linuxlog.log, winlog.log and extLinu...
- 20:42 Revision 1554549b (rudder-techniques): Fixes #4603: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log (for relay servers)
- 20:28 Revision d22d5963 (rudder): Merge pull request #471 from VinceMacBuche/arch_4600/imp_4601/refactor_api_building
- Refs #4601: Add comments and header
- 20:28 Revision 680e0c4e (rudder): Merge pull request #471 from VinceMacBuche/arch_4600/imp_4601/refactor_api_building
- Refs #4601: Add comments and header
- 20:24 Bug #4598: The inventory Techniques fail to insert the CFEngine public key with FusionInventory 2.3+
- Applied in changeset commit:3ae4075e4c300312a1a0f056e2468347663a054f.
- 20:24 Bug #4598 (Pending release): The inventory Techniques fail to insert the CFEngine public key with FusionInventory 2.3+
- Applied in changeset commit:df39cc60c1bb90793c41b46b823e255b6c2ea329.
- 20:19 Bug #4598 (Pending technical review): The inventory Techniques fail to insert the CFEngine public key with FusionInventory 2.3+
- PR is ready :)
- 18:22 Bug #4598 (Released): The inventory Techniques fail to insert the CFEngine public key with FusionInventory 2.3+
- The inventory Techniques fail to insert the CFEngine public key with a recent enough fusion inventory, as the key hav...
- 20:24 Revision 3ae4075e (rudder-techniques): Merge pull request #319 from Kegeruneku/bug_4598/dev/4598_correct_inventory_with_preserve_block
- Fixes #4598: Correct FusionInventory insertions using preserve_block
- 20:17 Revision df39cc60 (rudder-techniques): Fixes #4598: Correct FusionInventory insertions using preserve_block
- 20:14 Revision 3b65acd7 (rudder): Ref #4601: add comments and header
- 20:14 Revision c4e45176 (rudder): Ref #4601: add comments and header
- 20:11 User story #4460 (Pending release): UNIX support - implementation for other Techniques - general cases
- 20:11 User story #4460: UNIX support - implementation for other Techniques - general cases
- 20:02 Revision d51b0211 (rudder): Fixes #4552: add reports for nothing is to be done
- 20:02 Revision 28498e32 (rudder): Fixes #4552: add reports for nothing is to be done
- 19:58 User story #4520 (Pending release): Don't write execution report in several log files
- 19:58 User story #4520: Don't write execution report in several log files
- 11:39 User story #4520: Don't write execution report in several log files
- More info:
- we are keeping /var/log/rudder/compliance/non-compliant-reports.log: it's a post-proccessed file, wit... - 19:56 User story #4602: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log
- Applied in changeset policy-templates:commit:a0ae89f906412eb3c883b882af44d7e44711312a.
- 19:56 User story #4602 (Pending release): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log
- Applied in changeset policy-templates:commit:4f8bba55d24ce3c66afa3d0cc1d5d1246cadf112.
- 19:53 User story #4602 (Pending technical review): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log
- PR available for review: https://github.com/Normation/rudder-techniques/pull/318/files
- 19:52 User story #4602 (Released): Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log
- See #4520
- 19:56 Revision a0ae89f9 (rudder-techniques): Merge pull request #318 from jooooooon/bug_4602/don_t_write_reports_to_linuxlog_log_winlog_log_and_extlinuxreport_log_since_they_are_already_all_in_all_log
- Fixes #4602: Don't write reports to linuxlog.log, winlog.log and extLinu...
- 19:53 Architecture #4600 (Pending release): Ease new REST APIs creation
- 19:53 Architecture #4600: Ease new REST APIs creation
- 19:53 Architecture #4600: Ease new REST APIs creation
- 19:27 Architecture #4600 (Released): Ease new REST APIs creation
- Adding a new API or new api version can be complicated, it needs a lot of boilerplate code and allow multiple errors....
- 19:52 Revision 4f8bba55 (rudder-techniques): Fixes #4602: Don't write reports to linuxlog.log, winlog.log and extLinuxReport.log since they are already all in all.log
- 19:51 Architecture #4601: Generate API (url and header kind) from same request dispatch code
- Applied in changeset commit:01b9c7dfd4d2cc85166437041d9191f4a50c4e53.
- 19:51 Architecture #4601 (Pending release): Generate API (url and header kind) from same request dispatch code
- Applied in changeset commit:f7af7b7521933caedde65246cf5a0db778ee86e4.
- 19:34 Architecture #4601 (Pending technical review): Generate API (url and header kind) from same request dispatch code
- PR here: https://github.com/Normation/rudder/pull/470
- 19:29 Architecture #4601 (Released): Generate API (url and header kind) from same request dispatch code
- The most problem is that we duplicate code between API versions and kind of API.
We need to reduce that amount of ... - 19:51 Revision 4088fa5d (rudder): Merge pull request #470 from VinceMacBuche/arch_4600/imp_4601/refactor_api_building
- Fixes #4601: Refactor whole API generation
- 19:51 Revision 01b9c7df (rudder): Merge pull request #470 from VinceMacBuche/arch_4600/imp_4601/refactor_api_building
- Fixes #4601: Refactor whole API generation
- 19:46 Bug #4575: Remove unused datas from the LDAP tree initialisation
- Applied in changeset commit:b761285412d44dba25684dcf4340a899d140f6ca.
- 19:46 Bug #4575 (Pending release): Remove unused datas from the LDAP tree initialisation
- Applied in changeset commit:85803b5907f961de8f10122f6d555e9cbde38a5b.
- 19:26 Bug #4575: Remove unused datas from the LDAP tree initialisation
- retargeted
https://github.com/Normation/rudder/pull/468 - 19:45 Revision b652be9f (rudder): Merge pull request #468 from ncharles/bug_4575/dev/remove_POLICYCHILDREN_AND_CHILDRENID_from_ldap
- Fixes #4575: remove the POLICYCHILDREN and CHILDRENID from the ldap init...
- 19:45 Revision b7612854 (rudder): Merge pull request #468 from ncharles/bug_4575/dev/remove_POLICYCHILDREN_AND_CHILDRENID_from_ldap
- Fixes #4575: remove the POLICYCHILDREN and CHILDRENID from the ldap init...
- 19:42 Revision 6b63f9e5 (rudder): Fixes #4575: remove the POLICYCHILDREN and CHILDRENID from the ldap initialisation
- 19:42 Revision 85803b59 (rudder): Fixes #4575: remove the POLICYCHILDREN and CHILDRENID from the ldap initialisation
- 19:34 Bug #4573: Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from "common" system technique metadata
- Applied in changeset policy-templates:commit:cec1a3bd22ad95414386b2b935fdf1a8dc37eb16.
- 19:34 Bug #4573 (Pending release): Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from "common" system technique metadata
- Applied in changeset policy-templates:commit:6f23559579946857d0bda5fd6c252e926f4c264d.
- 19:30 Bug #4573: Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from "common" system technique metadata
- Clarifying the title to make it actually sound like a bug!
- 19:24 Bug #4573: Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from "common" system technique metadata
- retargetted to master:
https://github.com/Normation/rudder-techniques/pull/317 - 19:10 Bug #4573 (In progress): Remove unused variables ADMIN, POLICYCHILDREN and CHILDRENID from "common" system technique metadata
- Nico, could you retarget the associated PR (and other for the children) to 2.10 (given all the discussion above ?)
... - 19:34 Revision cec1a3bd (rudder-techniques): Merge pull request #317 from ncharles/bug_4573/dev/remove_policychildren_and_childrenid
- Fixes #4573: remove POLICYCHILDREN and CHILDRENID from system techniques
- 19:33 Bug #4576: Remove ADMIN from the LDAP tree
- Applied in changeset commit:91cd161334ec0f9a4b16d3150900ef2571904e7b.
- 19:33 Bug #4576 (Pending release): Remove ADMIN from the LDAP tree
- Applied in changeset commit:58558225b6c87e583379ca4b0eeabed9a8794972.
- 19:28 Bug #4576: Remove ADMIN from the LDAP tree
- retargeted https://github.com/Normation/rudder/pull/469
- 19:33 Revision 380f4162 (rudder): Merge pull request #469 from ncharles/bug_4576/dev/remove_admin_from_ldap_tree
- Fixes #4576: Remove ADMIN fomr ldap tree initialisation
- 19:33 Revision 91cd1613 (rudder): Merge pull request #469 from ncharles/bug_4576/dev/remove_admin_from_ldap_tree
- Fixes #4576: Remove ADMIN fomr ldap tree initialisation
- 19:32 Revision 32ffd803 (rudder): Fixes #4601: Refactor whole API generation
- 19:32 Revision f7af7b75 (rudder): Fixes #4601: Refactor whole API generation
- 19:23 Revision 6f235595 (rudder-techniques): Fixes #4573: remove POLICYCHILDREN and CHILDRENID from system techniques
- 19:06 Bug #4559: A rare race condition can lead to an error when looking at compliance while a deployment is in progress
- Applied in changeset commit:a284544fd1f5a9371c92ee648d1ee4e71006d4e0.
- 19:06 Bug #4559 (Pending release): A rare race condition can lead to an error when looking at compliance while a deployment is in progress
- Applied in changeset commit:4f1739e8f524f0a93cbbade0d143fcc8a84e8945.
- 19:06 Revision 8490e659 (rudder): Merge pull request #459 from ncharles/bug_4559/dev/race_condition
- Fixes #4559: create expected reports as a transaction
- 19:06 Revision a284544f (rudder): Merge pull request #459 from ncharles/bug_4559/dev/race_condition
- Fixes #4559: create expected reports as a transaction
- 18:59 Bug #4492 (Pending technical review): When accepting several nodes, one policy generation is triggered for each of them
- 18:57 Bug #4492 (In progress): When accepting several nodes, one policy generation is triggered for each of them
- 18:57 Bug #4492: When accepting several nodes, one policy generation is triggered for each of them
- In fact, the correction is trivial and also correct the fact that policies are regenerated when refusing nodes, so co...
- 11:33 Bug #4492: When accepting several nodes, one policy generation is triggered for each of them
- I believe it is more than a bug for 2.6, so if it's more than 2 lines, it should bo to 2.10.
- 18:56 Bug #4429: duplicated IP addresses across nodes are not accepted, preventing to handle NAT
- Applied in changeset commit:0141500bf2ca9b26e74e9a2206d3c0ac6d6261df.
- 18:56 Bug #4429 (Pending release): duplicated IP addresses across nodes are not accepted, preventing to handle NAT
- Applied in changeset commit:8e90babce7b1f4a08feeaf75048c6c61a142b38d.
- 11:42 Bug #4429: duplicated IP addresses across nodes are not accepted, preventing to handle NAT
- 11:42 Bug #4429: duplicated IP addresses across nodes are not accepted, preventing to handle NAT
- 18:56 Revision 98f1af98 (rudder): Merge pull request #452 from ncharles/bug_4429/dev/accept_duplicate_ip
- Fixes #4429: accepts duplicate ip in Rudder
- 18:56 Revision 0141500b (rudder): Merge pull request #452 from ncharles/bug_4429/dev/accept_duplicate_ip
- Fixes #4429: accepts duplicate ip in Rudder
- 18:29 User story #4560 (Pending technical review): Keep only the LDIF dump of the inventory when we accept/refuse it, not every time we receive a new inventory
- 18:13 User story #4560 (In progress): Keep only the LDIF dump of the inventory when we accept/refuse it, not every time we receive a new inventory
- We decided that the feature, implemented as it is, is just a dead weight for a future working implementation. So for ...
- 18:21 Revision 8831d1b6 (rudder): Fixes #4560: remove LDIF dump of inventories when received
- 18:21 Revision 8831d1b6 (ldap-inventory): Fixes #4560: remove LDIF dump of inventories when received
- 18:15 User story #4477 (Pending release): Upgrade version of jetty (7.6.14) in Rudder packages
- 18:15 User story #4586: Upgrade version of jetty in Rudder packages to 7.6.14
- Applied in changeset packages:commit:dea2651bed2273b1770f4488396b7908b28ceda4.
- 18:15 User story #4586 (Pending release): Upgrade version of jetty in Rudder packages to 7.6.14
- Applied in changeset packages:commit:6e8d2ae4973fbb7da889569648da916faff06b74.
- 18:13 User story #4586 (Pending technical review): Upgrade version of jetty in Rudder packages to 7.6.14
- 18:15 Revision dea2651b (rudder-packages): Merge pull request #254 from jooooooon/dev_4586/upgrade_version_of_jetty_in_rudder_packages_to_7_6_14
- Fixes #4586: Upgrade version of jetty in Rudder packages to 7.6.14
- 18:12 Revision 6e8d2ae4 (rudder-packages): Fixes #4586: Upgrade version of jetty in Rudder packages to 7.6.14
- 18:04 User story #4597 (Released): Replace init script for rudder-agent by a AIX-native approach
- AIX doesn't support sysV init scripts. We need something to launch the cf-execd daemon.
- 18:03 User story #4596: Avoid using "cp -a" on AIX systems in packages
- Applied in changeset commit:584d0bc66991696bc1d6cffbcc384abd5ee2d4ae.
- 18:03 User story #4596 (Pending release): Avoid using "cp -a" on AIX systems in packages
- Applied in changeset commit:35ac6ed712f491cc1863211883103a2c5f0f39d0.
- 17:55 User story #4596 (Pending technical review): Avoid using "cp -a" on AIX systems in packages
- PR available for review: https://github.com/Normation/rudder-packages/pull/256/files
- 17:53 User story #4596 (Released): Avoid using "cp -a" on AIX systems in packages
- "cp -a" is not supported on AIX. We need to replace it by "cp -hpPr".
- 18:03 Revision 584d0bc6 (rudder-packages): Merge pull request #256 from jooooooon/int_4596/avoid_using_cp_a_on_aix_systems
- Fixes #4596: Avoid using "cp -a" on AIX systems
- 17:55 Revision 35ac6ed7 (rudder-packages): Fixes #4596: Avoid using "cp -a" on AIX systems
- 17:47 User story #4595 (Released): Support for AIX (agent only)
- We want to support running the rudder-agent on AIX 5.3 and 6.1 (at least, 7.* would be nice too).
- 16:41 User story #4594: Upgrade FusionInventory to version 2.3.6 (AIX only)
- Note: http://www.fusioninventory.org/news/2013/11/08/06/FusionInventory-Agent-2.3.3/
- 16:19 User story #4594 (Released): Upgrade FusionInventory to version 2.3.6 (AIX only)
- Upgrade FusionInventory to version 2.3.6 (latest), so we can finally take advantage of the informations added by fusi...
- 15:36 User story #4593: Use Rudder specific inventory data from FusionInventory 2.3
- Note: the test was done on a Fedora machine using FusionInventory 2.3.3
- 15:36 User story #4593 (Released): Use Rudder specific inventory data from FusionInventory 2.3
- I tried to send Rudder a new-style Fusion Inventory (which uses the fusion module to gather Rudder information instea...
- 15:34 User story #4552 (Pending technical review): Have a new type of report, when nothing is to be done
- 14:05 User story #4592: When a report was not received, call it "No report" instead of "No Answer" in compliance details
- What about "No status" or "Not available"? Or maybe even better "No report". Would also be nice to disable a status i...
- 11:00 User story #4592 (Released): When a report was not received, call it "No report" instead of "No Answer" in compliance details
- Status "No answer" is kind of misleading, we are not asking quesiton, but rather have a "state" for a Directive
So w... - 11:39 Architecture #4528: Change the query made to check the database status in the system Technique
Also available in: Atom