Activity
From 2017-06-28 to 2017-06-28
2017-06-28
- 21:24 Bug #10580: Cannot mix audit/enforce mode on directives based on the same technique
- After some more testing I determined that if I remove the Audit version of the technique from git, commit it, delete ...
- 20:54 Bug #10580: Cannot mix audit/enforce mode on directives based on the same technique
- I believe this was actually working okay with 4.1.3 (making a copy of the technique as described above). When I upgr...
- 18:51 Bug #11055 (Released): Rudder can't start anymore because does not find configuration-repository techniques category in git
- If you happen to be in a state where you have a commit without /var/rudder/configuration-repository/techniques/catego...
- 17:38 Bug #11052 (Resolved): Missing documentation about how to use an external postgres server (but no multi-server rudder install)
- We have a documentation that explain how to use only the [rudder-db / everything else] for multi-server install: http...
- 17:21 Revision 2b618d0b (rudder-techniques): Merge branch 'branches/rudder/4.1' into branches/rudder/4.2
- 17:21 Revision 8df0e0a6 (rudder-techniques): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
- 17:21 Revision bd79d422 (rudder-techniques): Merge branch 'branches/rudder/3.1' into branches/rudder/4.0
- 17:21 Bug #8752 (Pending release): Directive: Services Management doesn't support AIX
- Applied in changeset commit:rudder-techniques|18a0c01c270b7484e35ab4376ce0b42c674d301a.
- 16:58 Bug #8752 (Pending technical review): Directive: Services Management doesn't support AIX
- PR https://github.com/Normation/rudder-techniques/pull/1168
- 16:56 Bug #8752 (In progress): Directive: Services Management doesn't support AIX
- 17:14 Question #11040: Is it okay to have multiple ethernet interfaces on the Rudder server with different IP addresses on different networks?
- OK, so this should work.
- 17:12 Question #11040: Is it okay to have multiple ethernet interfaces on the Rudder server with different IP addresses on different networks?
- Sorry, I think I misread the question. For a specific target node, it would only contact the Rudder server on a singl...
- 17:09 Question #11040: Is it okay to have multiple ethernet interfaces on the Rudder server with different IP addresses on different networks?
- Since the server would be have ethernet interfaces on different networks, the server would have multiple IP addresses.
- 16:38 Question #11040: Is it okay to have multiple ethernet interfaces on the Rudder server with different IP addresses on different networks?
- The nodes contact the server from the address they have in the policy_server.dat file.
It is possible to specify a d... - 17:03 Bug #10504 (Rejected): Zypper complains too late about missing jdk 1.8 when installing rudder 4.1
- Closing since what happens is what was asked for.
- 17:01 Bug #9746 (Rejected): Multilevel technique version numbers not working
- Technique versions of the form x.y.z are not supported.
Only versions of the form x.y are supported. - 16:58 Revision 18a0c01c (rudder-techniques): Fixes #8752: Directive: Services Management doesn't support AIX
- 16:56 Bug #11051 (Rejected): rudder-relay-server install broken due to apache not restarting
- On rudder 4.2.0~beta1, the installation of root server fails with:...
- 16:54 Bug #6322 (Rejected): "unknow status" for migrated change request in Rudder 3.0
- Rudder 3.0 is not supported anymore
- 16:50 Bug #7850 (Rejected): Upgrading from 2.11 to 3.1.6, with a distributed setup ( external DB ), on SLES, leads to invalid config file for LDAP
- Upgrading from 2.11 is not supported anymore
- 16:41 Bug #7597 (Rejected): When upgrading from 2.11 to 3.1.5, the root server gets components in No Reports
- We do not support upgrade from 2.11 anymore.
- 15:36 User story #10984: Rudder server as rudder repository mirror
- Thanks for proposing that, it seems to be a very useful case. We are going to assess what must be done to do that in ...
- 13:48 Bug #10859 (Pending technical review): Do not show instructions for rudder-node-to-relay on root setup
- PR https://github.com/Normation/rudder-packages/pull/1366
- 13:23 Bug #10859 (In progress): Do not show instructions for rudder-node-to-relay on root setup
- 13:48 Revision af832398 (rudder-packages): Fixes #10859: Do not show instructions for rudder-node-to-relay on root setup
- 12:29 Architecture #11033 (Pending release): Use uuid to authenticate windows agents
- Applied in changeset commit:rudder-packages|ec8558b120cba3aa75731bbf90efd21778843f2d.
- 12:26 Architecture #11046 (Pending release): Use uuid to authenticate windows agents in system techniques
- Applied in changeset commit:rudder-techniques|c8d7d269fe5d2e0f44d4455b8aeae53e5ba9cb55.
- 12:25 Bug #11050 (Rejected): Rudder-agent package for debian can't be installed on Debian 9 (stretch) due to libssl1.0.0 dependency
The rudder-agent package for Debian jessie can't be installed on Debian stretch due to a libssl1.0.0 dependency.
D...- 11:29 User story #11049: Create a command to display system classes
- (that could be easy to make it part of the inventory, and make them available to the webapp, probably easier for poli...
- 11:27 User story #11049: Create a command to display system classes
- ...
- 11:06 User story #11049 (Released): Create a command to display system classes
- We can easily display system classes currently defined on a node, this could be useful to help building policies.
- 09:48 Bug #10773: Rounding error in compliance bar can hide error with very small percent
- Proposed algo:
* Sort values from small to big
* Have a counter for the rounding error (= displayed value - real va... - 09:40 Revision 20552eb3 (rudder-agent): Merge branch 'branches/rudder/4.1' into branches/rudder/4.2
- 09:40 Bug #11047 (Pending release): rudder agent update -q bad exit code
- Applied in changeset commit:rudder-agent|0d98103fb02322a5a08016c38cda1694aa14e515.
- 09:40 Revision 835edd18 (rudder-agent): Merge branch 'branches/rudder/4.0' into branches/rudder/4.1
Also available in: Atom