Activity - Rudder - Issue Tracker

Activity

From 2014-07-10 to 2014-07-10

2014-07-10

20:22 Architecture #5255 (Pending technical review): Update rudder version to 2.12.0~alpha1: François ARMAND
10:29 Architecture #5255 (Released): Update rudder version to 2.12.0~alpha1: François ARMAND
20:21 Architecture #5254 (Pending technical review): Update cfclerk version to 2.12.0~alpha1: François ARMAND
10:29 Architecture #5254 (Released): Update cfclerk version to 2.12.0~alpha1: François ARMAND
20:17 Architecture #5253 (Pending technical review): Update ldap-inventory version to 2.12.0~alpha1: François ARMAND
10:28 Architecture #5253 (Released): Update ldap-inventory version to 2.12.0~alpha1: François ARMAND
20:16 Architecture #5252 (Pending technical review): Update scala-ldap version to 2.12.0~alpha1: François ARMAND
10:27 Architecture #5252 (Released): Update scala-ldap version to 2.12.0~alpha1: François ARMAND
20:15 Architecture #5251 (Pending technical review): Update commons version to 2.12.0~alpha1: François ARMAND
10:26 Architecture #5251 (Released): Update commons version to 2.12.0~alpha1: François ARMAND
20:08 Revision 339afdda (cf-clerk): Fixes #5254: update cfclerk version to 2.12.0: François ARMAND
19:40 Bug #5258 (Released): On Rudder 2.11, the distributed mode rudder-db and rudder-ldap are not considered as "server" then are in the list of "accepted nodes": The distributed mode can split Rudder server into 4 components. Two of these compenents are "rudder-db" and "rudder-l... Nicolas PERRON
19:17 Bug #5241: In compliance popup, report status displayed for each node is not correct: Applied in changeset commit:661d847e16479c2a79be3a7b59be5381c6cef3b1. François ARMAND
19:17 Bug #5241 (Pending release): In compliance popup, report status displayed for each node is not correct: Applied in changeset commit:39e1f89ce70c8c1594c1191ba2e4999d50c0f752. Vincent MEMBRÉ
19:09 Bug #5241 (Pending technical review): In compliance popup, report status displayed for each node is not correct: Vincent MEMBRÉ
19:08 Bug #5241: In compliance popup, report status displayed for each node is not correct: PR here: https://github.com/Normation/rudder/pull/575 Vincent MEMBRÉ
19:17 Revision 34e1a6f7 (rudder): Merge pull request #576 from VinceMacBuche/bug_5241/fix_reporting_detail: Fixes #5241: Fix reporting details, and clean reporting structures François ARMAND
19:17 Revision 661d847e (rudder): Merge pull request #576 from VinceMacBuche/bug_5241/fix_reporting_detail: Fixes #5241: Fix reporting details, and clean reporting structures François ARMAND
19:03 Revision 4b21300e (rudder): Fixes #5241: Fix reporting details, and clean reporting structures: Vincent MEMBRÉ
19:03 Revision 39e1f89c (rudder): Fixes #5241: Fix reporting details, and clean reporting structures: Vincent MEMBRÉ
18:24 Architecture #5250 (Pending technical review): Upgrade master-pom to 2.12.0: François ARMAND
10:25 Architecture #5250 (Released): Upgrade master-pom to 2.12.0: Also, upgrade trivial, compatible dependencies, like Scala to the next minor. François ARMAND
18:20 Revision e55931ae (rudder): Fixes #5255: update rudder version to 2.12.0: François ARMAND
18:20 Revision b9ef91b9 (rudder): Fixes #5255: update rudder version to 2.12.0: François ARMAND
18:03 Revision 823ffa37 (rudder): Fixes #5253: update ldap-inventory version to 2.12.0: François ARMAND
18:03 Revision 823ffa37 (ldap-inventory): Fixes #5253: update ldap-inventory version to 2.12.0: François ARMAND
18:02 Revision 6f4901b0 (rudder): Fixes #5252: update scala-version version to 2.12.0: François ARMAND
18:02 Revision 6f4901b0 (scala-ldap): Fixes #5252: update scala-version version to 2.12.0: François ARMAND
18:00 Revision 78b6b95e (rudder): Fixes #5251: update commons version to 2.12.0: François ARMAND
18:00 Revision 78b6b95e (rudder-commons): Fixes #5251: update commons version to 2.12.0: François ARMAND
17:59 Revision a945ad05 (rudder): Fixes #5250: update parent pom to 2.12 and other dependencies to newer, non breaking version: François ARMAND
17:59 Revision a945ad05 (parent-pom): Fixes #5250: update parent pom to 2.12 and other dependencies to newer, non breaking version: François ARMAND
17:28 Bug #5071: Debian package management: can't specify a repository (ex: "-t wheezy-backports"): Yes, it was OK.
I used the following manual procedure to upgrade rsyslog on a freshly installed Debian 7.5:... Olivier Chédru
17:23 Bug #5071: Debian package management: can't specify a repository (ex: "-t wheezy-backports"): The repository you added seems to have rsyslog 7.6.3 but still not having all required dependencies:... Nicolas PERRON
16:55 Bug #5071: Debian package management: can't specify a repository (ex: "-t wheezy-backports"): As far I can see, your repaired status could be due to CFEngine trying to compare a version not matched. The installe... Nicolas PERRON
12:55 Bug #5246 (Released): Remove group permission on promises after they have been generated: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
12:55 Bug #5238 (Released): CFEngine is unable to run automatically on Rudder Server 2.11.0.rc1 since its generated promises have group writable permissions: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
12:33 Bug #5238: CFEngine is unable to run automatically on Rudder Server 2.11.0.rc1 since its generated promises have group writable permissions: This was reverted and now fixed by #5246 Vincent MEMBRÉ
12:55 Bug #5237 (Released): Reports cannot be stored in local postgresql on a server Rudder in stand alone configuration: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
12:55 Bug #5235 (Released): An error occurs during upgrade because variable OPT_RUDDER is missing in rudder-upgrade-database script: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
12:55 Bug #5223 (Released): After upgrade to 2.11 on rpm systems, web interface isn't started by jetty as rudder.xml is deleted during upgrade: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
12:55 Bug #5200 (Released): Nodes which are not part of distributed architecture displays an error log on agent execution about missing '/opt/rudder/etc/server-roles.d/' directory: This bug has been fixed in Rudder 2.11.0~rc2 ("announcement":http://www.rudder-project.org/pipermail/rudder-announce/... Vincent MEMBRÉ
11:25 Bug #5244: Technique 'Package management for RHEL / CentOS / SuSE / RPM systems' v5.1: Unable to update a package without version set but still report a success: I've linked to 3 related issues, that seem closely related, and could be fixed at the same time (if not already fixed) Nicolas CHARLES
11:16 Bug #4513: Technical reports timeout when no reports are available: We do have an index on (nodeId, executionTimestamp) so it should not be that big an issue. I'm still trying to figure... Nicolas CHARLES
11:12 User story #4395: How difficult would be to implement support for system manufacturer/model?: You may not have noted, but we implemented this support for 2.11
However we have not yet implemented the RAID suppor... Nicolas CHARLES
11:06 Bug #5191: Inventories generated on Windows are not accepted by the endpoint: Francois, I've made a remark on this PR
We need to use OSVERSION, so that it shows in the Web Interface Nicolas CHARLES
10:30 User story #5256 (New): Accepted nodes and techniques shared among relays: Hi,
In the distributed setup, it appears that each relay receives the techniques and allows connections only from ... Lionel Le Folgoc
10:22 Architecture #5249 (Released): Update dependencies and version to 3.0.0: The new master is 2.12.0 ! François ARMAND

Also available in: Atom