Activity
From 2014-06-11 to 2014-06-11
2014-06-11
- 23:30 User story #4961 (Pending release): Clean-up js/css ressources links
- commit:f605e2e22fa78870d0acaf9d143f310d99ff7792.
- 23:29 User story #4961: Clean-up js/css ressources links
- oh, this has been merged, but due to bad ticket number, it does not appear
commit is : rudder:f605e2e22fa78870d0ac... - 23:25 Bug #5002: Package upgrade can fail if /etc/{cron.d,init.d,default}/rudder-agent are missing
- Applied in changeset commit:b18b45b5a8ecf9e1ffe3867a3e1f6d9d2dea91eb.
- 23:25 Bug #5002 (Pending release): Package upgrade can fail if /etc/{cron.d,init.d,default}/rudder-agent are missing
- Applied in changeset commit:d377ea1631a6e1f2e640c15ae71fcfdc96e9a634.
- 22:39 Bug #5002 (Pending technical review): Package upgrade can fail if /etc/{cron.d,init.d,default}/rudder-agent are missing
- 22:32 Bug #5002 (Released): Package upgrade can fail if /etc/{cron.d,init.d,default}/rudder-agent are missing
- When rudder-agent package gets upgraded, it tries to backup somes files (/etc/{cron.d,init.d,default}/rudder-agent) "...
- 23:25 Revision b18b45b5 (rudder-packages): Merge pull request #359 from jooooooon/bug_5002/package_upgrade_can_fail_if_etc_cron_d_init_d_default_rudder_agent_are_missing
- Fixes #5002: Package upgrade can fail if /etc/{cron.d,init.d,default}/ru...
- 23:15 Revision d377ea16 (rudder-packages): Fixes #5002: Package upgrade can fail if /etc/{cron.d,init.d,default}/rudder-agent are missing
- 23:13 Bug #5003: Initial promises on server cause an error to be logged due to duplicate "empty_file_before_editing" setting
- Applied in changeset policy-templates:commit:463c2c46c92d4a7054a1377940c61649fc429e41.
- 23:13 Bug #5003 (Pending release): Initial promises on server cause an error to be logged due to duplicate "empty_file_before_editing" setting
- Applied in changeset policy-templates:commit:534577dfd6fa26fc58e48deb830cc9f78f1ce48d.
- 23:08 Bug #5003 (Pending technical review): Initial promises on server cause an error to be logged due to duplicate "empty_file_before_editing" setting
- 23:05 Bug #5003 (Released): Initial promises on server cause an error to be logged due to duplicate "empty_file_before_editing" setting
- Running initial promises on a server, I see this message in verbose output:...
- 23:13 Revision 463c2c46 (rudder-techniques): Merge pull request #410 from jooooooon/bug_5003/initial_promises_on_server_cause_an_error_to_be_logged_due_to_duplicate_empty_file_before_editing_setting
- Fixes #5003: initial promises on server cause an error to be logged due ...
- 23:07 Revision 534577df (rudder-techniques): Fixes #5003: initial promises on server cause an error to be logged due to duplicate "empty_file_before_editing" setting
- 22:13 Revision 9b04c8d8 (rudder-techniques): Merge branch 'branches/rudder/2.11'
- 22:13 Revision 8e8a26c4 (rudder-techniques): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 22:13 Revision 2d89d45c (rudder-techniques): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- 22:13 Revision 57429e01 (rudder-techniques): Merge branch 'branches/rudder/2.6' into branches/rudder/2.9
- 22:12 Bug #5001: Technique groupManagement: Members of group are enforced at group creation even if option is not set
- Applied in changeset commit:7b0737554be1fee70867966f09abc6de2304b9cb.
- 22:12 Bug #5001 (Pending release): Technique groupManagement: Members of group are enforced at group creation even if option is not set
- Applied in changeset commit:004694a2b8a560a77de1231a77e7e912c295da1d.
- 22:12 Bug #5001 (Pending technical review): Technique groupManagement: Members of group are enforced at group creation even if option is not set
- 22:11 Bug #5001 (Released): Technique groupManagement: Members of group are enforced at group creation even if option is not set
- Since it's version 3.1, the groupManagement technique has an option to force or not the members of a group. By defaul...
- 22:12 Revision 7b073755 (rudder-techniques): Merge pull request #409 from jooooooon/bug_5001/technique_groupmanagement_members_of_group_are_enforced_at_group_creation_even_if_option_is_not_set
- Fixes #5001: Technique groupManagement: members of group are enforced at...
- 22:11 Revision 004694a2 (rudder-techniques): Fixes #5001: Technique groupManagement: members of group are enforced at group creation even if option is not set
- 21:02 Revision 5ee42692 (rudder-techniques): Merge branch 'branches/rudder/2.11'
- 21:02 Revision 21557001 (rudder-techniques): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 21:02 Revision 01f9e844 (rudder-techniques): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- Conflicts:
techniques/systemSettings/userManagement/userManagement/3.0/userManagement.st - 21:01 Revision 0cbd8a45 (rudder-techniques): Merge branch 'branches/rudder/2.6' into branches/rudder/2.9
- 21:00 Bug #5000: No report for password section if group definition error occurs in userManagement 3.0 Technique
- Applied in changeset commit:6aefb6ba8a4a2d7a8b4b09338f4a1420a7585d04.
- 21:00 Bug #5000 (Pending release): No report for password section if group definition error occurs in userManagement 3.0 Technique
- Applied in changeset commit:c89741aa52c8a11260e1e23888a8873109f4a86b.
- 20:59 Bug #5000 (Pending technical review): No report for password section if group definition error occurs in userManagement 3.0 Technique
- 20:55 Bug #5000 (Released): No report for password section if group definition error occurs in userManagement 3.0 Technique
- As a result of the very recent change in #4270, a "No report" condition can occur for the Password component in this ...
- 21:00 Revision 6aefb6ba (rudder-techniques): Merge pull request #408 from jooooooon/bug_5000/no_report_for_password_section_if_group_definition_error_occurs_in_usermanagement_3_0_technique
- Fixes #5000: No report for password section if group definition error oc...
- 20:59 Revision c89741aa (rudder-techniques): Fixes #5000: No report for password section if group definition error occurs in userManagement 3.0 Technique
- 20:25 User story #4994 (Pending technical review): Make rudder-init.sh and rudder-upgrade remote server aware (integration)
- PR is ready ! (good luck for the review)
- 11:04 User story #4994 (Released): Make rudder-init.sh and rudder-upgrade remote server aware (integration)
- Please see upper ticket for details
- 20:21 Revision 81241c36 (rudder-packages): Fixes #4994: Update rudder-init, rudder-upgrade, rudder-upgrade-database to be able to handle remote connexions
- 19:48 Revision 8b6a464d (rudder-techniques): Merge branch 'branches/rudder/2.11'
- 19:48 Revision 39623ce3 (rudder-techniques): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 19:48 Revision f23dcc53 (rudder-techniques): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- Conflicts:
techniques/systemSettings/userManagement/userManagement/3.0/metadata.xml
techniques/systemSettings/userM... - 19:15 Revision a53f43a7 (rudder-techniques): Merge branch 'branches/rudder/2.6' into branches/rudder/2.9
- 19:15 Bug #4270: Technique User management: cannot create an user if a group using the same name laready exists
- Applied in changeset commit:daa7455a4a3bb64e387239a8222ab1b74fbec2b2.
- 19:15 Bug #4270 (Pending release): Technique User management: cannot create an user if a group using the same name laready exists
- Applied in changeset commit:8572e048dfdc711a352890194b954875735b5123.
- 18:29 Bug #4270: Technique User management: cannot create an user if a group using the same name laready exists
- It would be cool to be able to specify the group in with the user should be in (facultative)
Two possiblities:
# if... - 19:15 Revision daa7455a (rudder-techniques): Merge pull request #259 from Kegeruneku/bug_4270/dev/4270_add_option_to_users_technique_to_handle_custom_groups
- Fixes #4270: Added an option to userManagement to handle the primary gro...
- 19:12 Revision 8572e048 (rudder-techniques): Fixes #4270: Added an option to userManagement to handle the primary groups of new users
- 18:54 Revision 94362dd8 (rudder-doc): Merge branch 'branches/rudder/2.11'
- 18:54 Revision 3e06aac7 (rudder-doc): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- Conflicts:
10_install_server/11_install_root_server_debian.txt
10_install_server/12_install_root_server_sles.txt
1... - 18:53 Revision 7e8660b8 (rudder-techniques): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- 18:52 Revision b0ba90f7 (rudder-doc): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- Conflicts:
10_install_server/11_install_root_server_debian.txt
10_install_server/12_install_root_server_sles.txt
1... - 18:50 Revision 29b2283a (rudder-doc): Merge branch 'branches/rudder/2.6' into branches/rudder/2.9
- Conflicts:
10_install_server/11_install_root_server_debian.txt
10_install_server/12_install_root_server_sles.txt
1... - 18:29 Bug #4999: Technique rpmPackageInstallation: Specified version is not taken into account
- Applied in changeset policy-templates:commit:59b1df4a19b7031bb1d0a41f211d0540b0470c72.
- 18:29 Bug #4999 (Pending release): Technique rpmPackageInstallation: Specified version is not taken into account
- Applied in changeset policy-templates:commit:9be3a55fe2bfca72b8f4b688b469d320ba473a29.
- 17:23 Bug #4999 (Pending technical review): Technique rpmPackageInstallation: Specified version is not taken into account
- PR is there
https://github.com/Normation/rudder-techniques/pull/407/files - 17:01 Bug #4999 (Released): Technique rpmPackageInstallation: Specified version is not taken into account
- In the Technique rpmPackageInstallation, the version is not taken into account when we want to install a specific ver...
- 18:28 Revision 59b1df4a (rudder-techniques): Merge pull request #407 from ncharles/bug_4999/dev/rpm_package_installation
- Fixes #4999: allow to install specific version of package with RPM
- 18:25 Bug #4998: Installation section is too hard to follow
- Applied in changeset commit:681b3269caa3b6113a4290c7c5a7a2c6b8628fe6.
- 18:25 Bug #4998 (Pending release): Installation section is too hard to follow
- Applied in changeset commit:4560fbc6f17f6d5979b45c4545e44d4604deb974.
- 16:59 Bug #4998 (Pending technical review): Installation section is too hard to follow
- 16:57 Bug #4998 (Released): Installation section is too hard to follow
- There are several issues with the installation section of the doc:
# Each section for Debian/SLES/RHEL is too long a... - 18:25 Revision 681b3269 (rudder-doc): Merge pull request #63 from jooooooon/bug_4998/installation_section_is_too_hard_to_follow
- Fixes #4998: Installation section is too hard to follow
- 18:21 Revision 9be3a55f (rudder-techniques): Fixes #4999: allow to install specific version of package with RPM
- 18:19 Bug #4722: Documented procedure for Relay Server is invalid
- Applied in changeset commit:b014a6c8843a127395a170f008d361dab5f19796.
- 18:19 Bug #4722 (Pending release): Documented procedure for Relay Server is invalid
- Applied in changeset commit:e5c33db46c5183878ba6000081479bd7ae39fa4c.
- 17:41 Bug #4722 (Pending technical review): Documented procedure for Relay Server is invalid
- 17:24 Bug #4722 (In progress): Documented procedure for Relay Server is invalid
- 17:24 Bug #4722: Documented procedure for Relay Server is invalid
- Nicolas CHARLES wrote:
> Finally, the apache configuration doesn't permit to access /uuid on debian squeeze, with er... - 18:19 Revision b014a6c8 (rudder-doc): Merge pull request #65 from jooooooon/bug_4722/documented_procedure_for_relay_server_is_invalid
- Fixes #4722: Documented procedure for Relay Server is invalid
- 18:18 Bug #4822: Procedure on how to update the Technique Librairy is invalid
- Applied in changeset commit:724e6811219488ec937d594d8ce67e415daa079a.
- 18:18 Bug #4822 (Pending release): Procedure on how to update the Technique Librairy is invalid
- Applied in changeset commit:43f7ff100c1ed86e78e3480c0e009186d414f1bd.
- 17:02 Bug #4822 (Pending technical review): Procedure on how to update the Technique Librairy is invalid
- 18:18 Revision 724e6811 (rudder-doc): Merge pull request #64 from jooooooon/bug_4822/procedure_on_how_to_update_the_technique_librairy_is_invalid
- Fixes #4822: Procedure on how to update the Technique Librairy is invali...
- 17:40 Revision e5c33db4 (rudder-doc): Fixes #4722: Documented procedure for Relay Server is invalid
- 17:09 Revision 185061db (rudder-packages): Merge branch 'branches/rudder/2.11'
- 17:09 Revision 5e51596f (rudder-packages): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 17:08 Revision 83ec57d4 (rudder-techniques): Merge branch 'branches/rudder/2.11'
- 17:07 Revision 74028b6a (rudder-techniques): Merge branch 'branches/rudder/2.10' into branches/rudder/2.11
- 17:07 Revision 90c9e9ba (rudder-techniques): Merge branch 'branches/rudder/2.9' into branches/rudder/2.10
- 17:07 Revision 063d91cd (rudder-techniques): Merge branch 'branches/rudder/2.6' into branches/rudder/2.9
- 17:05 Bug #4996: Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5)
- Applied in changeset policy-templates:commit:ef9686e678662301165abc09279a4c057e37c93d.
- 17:05 Bug #4996 (Pending release): Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5)
- Applied in changeset policy-templates:commit:5d59c2632b39bf74191fe04e170a8fc657d88dd8.
- 16:55 Bug #4996 (Pending technical review): Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5)
- PR here: https://github.com/Normation/rudder-techniques/pull/406
- 16:46 Bug #4996: Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5)
- This only happen with initial promises still present on root server, If I regenerate promises once, I don't have any ...
- 11:38 Bug #4996 (Released): Initial promises for Rudder 2.6 (CFEngine 3.4) cannot be used when upgrading to 2.10 (CFEngine 3.5)
- I have a freshly installed rudder Server 2.6 that I upgraded directly in 2.10 and when rudder-agent is restarted I go...
- 17:05 Revision ef9686e6 (rudder-techniques): Merge pull request #406 from VinceMacBuche/bug_4996/cfengine_stdlib_is_not_correct_initial_promise
- Fixes #4996: fixed cfengine_stdlib in intiial promises
- 17:01 Revision 43f7ff10 (rudder-doc): Fixes #4822: Procedure on how to update the Technique Librairy is invalid
- 16:59 Revision 4560fbc6 (rudder-doc): Fixes #4998: Installation section is too hard to follow
- 16:54 Revision 5d59c263 (rudder-techniques): Fixes #4996: Add fixed in cfengine_stdlib in intiial promises
- 13:43 Bug #4997: check-rudder-agent script fails if run_interval file does not exist
- Applied in changeset packages:commit:af697f52f7afca882e0724308954922802213299.
- 13:43 Bug #4997 (Pending release): check-rudder-agent script fails if run_interval file does not exist
- Applied in changeset packages:commit:36f82edab17f5c1cb2a75d11ac55092f3954a52d.
- 12:23 Bug #4997 (Pending technical review): check-rudder-agent script fails if run_interval file does not exist
- PR here: https://github.com/Normation/rudder-packages/pull/357
- 11:43 Bug #4997 (Released): check-rudder-agent script fails if run_interval file does not exist
- File defining agent run interval was not created before the update to 2.10
At the end of the upgrade process it tr... - 13:43 Revision af697f52 (rudder-packages): Merge pull request #357 from VinceMacBuche/bug_4997/run_interval_does_not_exists
- Fixes #4997: check-rudder-agent can now handle missing run_interval file
- 13:41 Revision 36f82eda (rudder-packages): Fixes #4997: check-rudder-agent can now handle missing run_interval file
- 12:28 Bug #4995 (Rejected): Server with no nodes can't update its promises
- It was a DNS issue ... cf-promises (and cf-agent) could not resolve my server hostname ...
- 12:04 Bug #4995: Server with no nodes can't update its promises
- I tried on a new install still with no nodes (One was pending though ... ) And there was no problem...
- 11:13 Bug #4995 (Rejected): Server with no nodes can't update its promises
- I have installed a fresh server with no nodes and directly updated my policies
The promise generation should have ... - 11:52 Architecture #4980: Remove HOSTLICENCESPAID system variable from metadata.xml in common Technique
- This one is the first to merge, as we can have unused but defined system variables, nit the other way around
- 11:35 Revision bf21c401 (rudder-packages): Refs #4994: Re-indent rudder-init, rudder-upgrade and rudder-upgrade-database (vim magic, gg=G command <3)
- 11:13 Revision 06097751 (rudder-packages): Refs #4994: Rename rudder-init.sh to rudder-init and create compatibility symlinks
- 11:04 User story #4993 (Released): Make rudder-init.sh and rudder-upgrade remote server aware
- We should, in those applications, stop relying on slap* utilities and localhost psql connexions and use remote connex...
- 00:48 Bug #4984: Some test fails on CFEngine 3.6 as the execresult and returnszero functions are cached at the begining of execution
- Applied in changeset commit:42c6b2e0bade3b0a5415024b48614e73aac84bce.
- 00:48 Bug #4984 (Pending release): Some test fails on CFEngine 3.6 as the execresult and returnszero functions are cached at the begining of execution
- Applied in changeset commit:26c593ca037e97fcbc5a78b3e38199b01263f7ee.
- 00:48 Revision 42c6b2e0 (ncf): Merge pull request #61 from ncharles/bug_4984/dev/correct_tests_with_cfengine_3_6
- Fixes #4984: Rewrite tests to uses classes conditions for execresults an.d returnszero, for CFEngine 3.6 compatibility
Also available in: Atom