Activity
From 2015-06-10 to 2015-06-10
2015-06-10
- 19:08 Architecture #6710: Allow rudder-users.xml based local users to change password
- Thank you folks !
Assigning this ticket to FAR for dispatching. - 19:07 Bug #6660: A report is missing on system techniques when cron needs to be restartd
- I know for sure that Alexis is working on at least this cron part on systemd-using OSes, assigning to him just in case.
- 18:28 User story #6739 (Pending technical review): Sign inventories on Windows
- PR https://github.com/Normation/rudder-techniques/pull/683
- 18:19 User story #6739 (Released): Sign inventories on Windows
- We should also sign inventories on Windows, following the addition of the script created in #6480 :)
- 18:28 Revision 98ecb456 (rudder-techniques): Fixes #6739: Sign inventories on Windows
- 18:28 Bug #6711: Hostname in inventory may sometimes be wrongfully in lowercase
- this change is too big to go to 2.11, but it would go in 3.1: it is safer to use reliable hostname from fusion inventory
- 18:23 User story #6731: Add an option to run cf-agent with -v to rudder agent run
- -v can be added to all rudder agent commands
debug would be specific to run
-> I prefer -v - 14:52 User story #6731: Add an option to run cf-agent with -v to rudder agent run
- Or maybe...
- 11:49 User story #6731 (Released): Add an option to run cf-agent with -v to rudder agent run
- ...
- 17:57 User story #6738 (Released): Add migration script to add default property for RUDDER_SYSLOG_PROTOCOL
- We should add an entry in the ldap containing the propery rudder_syslog_protocol with value tcp
- 17:37 Architecture #6480 (Rejected): Create a script to sign files using openssl on windows
- The work on this part is finished, and will be included as part of the Windows packaging.
For future reference, th... - 17:26 Architecture #6480 (In progress): Create a script to sign files using openssl on windows
- 17:23 Bug #6737 (Rejected): Make all techniques compatible with systemd changes
- Check compatibility of Rudder 3.0 techniques with systemd.
* process name may have changed
* /etc/init.d/ does no... - 17:20 Bug #6736 (Released): The cron_bin in system's promises.st is not compatible with RHEL7
- ...
- 17:15 Bug #6735 (Released): cronConfiguration is not compatible with RHEL 7 and SLES 12
- In the latest version of the cronConfiguration technique (3.0):...
- 17:01 Bug #6734: HashcodeCaching.scala typo error WRNING => WARNING
- Applied in changeset commit:rudder-commons|b7632a19597b94e7f9288ec6109cbede4dbf7f38.
- 17:01 Bug #6734 (Pending release): HashcodeCaching.scala typo error WRNING => WARNING
- Applied in changeset commit:rudder-commons|1ee107838585d781d404b1665ef6c8669ca2564c.
- 16:29 Bug #6734: HashcodeCaching.scala typo error WRNING => WARNING
- PR https://github.com/Normation/rudder-commons/pull/15
- 16:19 Bug #6734 (Released): HashcodeCaching.scala typo error WRNING => WARNING
- typo error in utils/src/main/scala/com/normation/utils/HashcodeCaching.scala WRNING => WARNING
- 16:45 Revision b7632a19 (rudder): Merge pull request #15 from frbayart/bug_6734/hashcodecaching_scala_typo_error_wrning_warning
- Fixes #6734: HashcodeCaching.scala typo error WRNING => WARNING
- 16:45 Revision b7632a19 (rudder-commons): Merge pull request #15 from frbayart/bug_6734/hashcodecaching_scala_typo_error_wrning_warning
- Fixes #6734: HashcodeCaching.scala typo error WRNING => WARNING
- 16:29 Revision 1ee10783 (rudder): Fixes #6734: HashcodeCaching.scala typo error WRNING => WARNING
- 16:29 Revision 1ee10783 (rudder-commons): Fixes #6734: HashcodeCaching.scala typo error WRNING => WARNING
- 16:12 Bug #6721 (Pending technical review): When a node is promoted to relay, the old rsyslog conf is never replaced
- https://github.com/Normation/rudder-techniques/pull/682
- 16:08 Bug #6566: promises.cf's "bundle agent check_cron_daemon" is not systemd aware
- Targeting 3.0 as it affects Fedora 18, SLES 12 and Red Hat 7.
- 15:18 Bug #6566 (In progress): promises.cf's "bundle agent check_cron_daemon" is not systemd aware
- 16:08 Revision bf619146 (rudder): Merge pull request #868 from fanf/ust_6137/create_compliance_api
- Issue #6137: add an API for compliance by node or rule
- 16:08 Revision dcf99727 (rudder): Merge pull request #868 from fanf/ust_6137/create_compliance_api
- Issue #6137: add an API for compliance by node or rule
- 13:46 Revision be6d5c27 (rudder): Issue #6137: add an API for compliance by node or rule
- 13:46 Revision c5087b49 (rudder): Issue #6137: add an API for compliance by node or rule
- 12:52 User story #6733 (Released): Allow Node properties to be used in directives and ncf techniques
- We added the possibliity to tag nodes with key=value pairs. But for now, these pair can only be used for group. We wa...
- 12:51 User story #5506: Customize Nodes by adding attribute on them
- There is a known limitation today (3.0): these properties can't be used in directives ! Only for creating groups.
- 12:02 User story #6705: Upgrade CFEngine to 3.6.5
- Applied in changeset commit:rudder-packages|5e251075c4f00e54226928bcd36596732a50211f.
- 12:02 User story #6705 (Pending release): Upgrade CFEngine to 3.6.5
- Applied in changeset commit:rudder-packages|2459c1adf468c0fec5c733be4fb25e72d321c872.
- 11:51 User story #6705 (Pending technical review): Upgrade CFEngine to 3.6.5
- PR https://github.com/Normation/rudder-packages/pull/681
- 11:38 User story #6705 (In progress): Upgrade CFEngine to 3.6.5
- 12:02 User story #6732: Rename variable "REPORT_PROTOCOL"
- Applied in changeset commit:cf-clerk|ca93a660b5e6f256b087365e59405fbbebfe02bf.
- 12:02 User story #6732 (Pending release): Rename variable "REPORT_PROTOCOL"
- Applied in changeset commit:cf-clerk|19561952d329981aa04012dcba60c446fccfc9b2.
- 11:52 User story #6732 (Pending technical review): Rename variable "REPORT_PROTOCOL"
- PR https://github.com/Normation/cf-clerk/pull/74
- 11:51 User story #6732 (In progress): Rename variable "REPORT_PROTOCOL"
- 11:49 User story #6732 (Released): Rename variable "REPORT_PROTOCOL"
- New variable introduced in #6726 should be renamed to "RUDDER_SYSLOG_PROTOCOL"
- 12:02 User story #6726: Add a system variable to manage how reports are sent
- Applied in changeset commit:cf-clerk|9c98f9a191692dbe27109e72a3a93c62df8ebaf8.
- 12:02 User story #6726 (Pending release): Add a system variable to manage how reports are sent
- Applied in changeset commit:cf-clerk|fc2f0007f4c6a0a3f66978f32d9554712638002d.
- 11:57 Revision 5e251075 (rudder-packages): Merge pull request #681 from Kegeruneku/ust_6705/upgrade_cfengine_to_3_6_5
- Fixes #6705: Upgrade CFEngine to 3.6.5
- 11:57 Revision ca93a660 (cf-clerk): Merge pull request #74 from VinceMacBuche/ust_6732/rename_variable_report_protocol
- Fixes #6732: Rename variable \"REPORT_PROTOCOL\"
- 11:52 Revision 19561952 (cf-clerk): Fixes #6732: Rename variable "REPORT_PROTOCOL"
- 11:50 Revision 2459c1ad (rudder-packages): Fixes #6705: Upgrade CFEngine to 3.6.5
- 11:40 Bug #6730 (Rejected): After modifying an ncf technique, the expected reports are not updated
- This is a weird one: after modifying an ncf technique (with generated code correctly updated), the web interface does...
- 11:38 Bug #6729 (Released): After a partial promise generation, some nodes being a relay may have their promises stored in a non reachable location
- If we do a partial promise regeneration, some node may have their new promises in the folder
/path/to/relay.new/path... - 11:33 Revision 9c98f9a1 (cf-clerk): Merge pull request #73 from VinceMacBuche/ust_6726/add_a_system_variable_to_manage_how_reports_are_sent
- Fixes #6726: Add a system variable to manage how reports are sent
- 11:10 Bug #6728 (Rejected): Acceptation timestamp of Technique are not updated what breaks change detection
- So, the behavior is in fact correct. On the first test, an side problem prevented the technique library to be reloade...
- 10:26 Bug #6728 (Rejected): Acceptation timestamp of Technique are not updated what breaks change detection
- When a Technique is updated, for ex. when one modifies a Techniques with the Technique Editor, its acceptation timest...
- 10:02 Bug #6727: No reports on Rudder, since rsyslog only accept the last node reports
- Applied in changeset commit:rudder-techniques|1044966a0fad3ef9bf6a797729bbe6208364013d.
- 10:02 Bug #6727 (Pending release): No reports on Rudder, since rsyslog only accept the last node reports
- Applied in changeset commit:rudder-techniques|02b4ff9671e2f969dd1cf7d37602c3e2a90e88ab.
- 09:13 Revision 1044966a (rudder-techniques): Merge pull request #681 from VinceMacBuche/bug_6727/almost_no_reports_on_rudder_webapp_since_rsyslong_configuration_accet_only_the_last_node
- Fixes #6727: Almost no reports on rudder webapp, since rsyslong configuration accet only the last node
Also available in: Atom