Activity
From 2012-06-15 to 2012-06-15
2012-06-15
- 23:09 Bug #2589 (Rejected): Clicking on a Technique in Reference library that is not in Active library causes "Cannot contact server at this time error"
- I just created a new Technique, reloaded the Technique library, and went to the Configuraiton Management > Techniques...
- 18:23 Revision 64e8f70a (rudder-techniques): Fixes #2587 : add webdav info as variables
- 18:22 Revision 3ea8338c (rudder): Refs #2587 : add webdav info as variables
- 18:22 Revision 6bb09324 (rudder): Refs #2587 : add webdav info as variables
- 18:21 Revision fdb3ee6f (cf-clerk): Refs #2587 : add webdav info as variables
- 17:37 Bug #2471 (Discussion): PT filePermissions has Owner and Group values mandatory even if our choice is to not modify them
- I'm sorry, but when I try to create a Policy Instance with this PT without ticking the "Should the owner of the file ...
- 17:30 Bug #2488 (Pending technical review): processManagement should allow restart command without arguments
- Applied in changeset commit:4e87f7d79bf3d33dd22fac1e7d7251941d2c7660.
- 17:30 Revision 4e87f7d7 (rudder-techniques): Fixes #2488: Enabled the user to use processManagement without specifying an argument to the command used
- 17:23 Bug #2457 (Pending technical review): (ex PT/Technique) fileManagement delete files without matching age if deletion operation has been set to "this file or directory only"
- Applied in changeset commit:0de91bcf428a74e20fcf16a5ca1fbb8fb5e5a505.
- 17:23 Revision 0de91bcf (rudder-techniques): Fixes #2457: Fixed the fileManagement PT: Delete files matching the desired age when the operation is 'this file or directory only'
- 16:39 Architecture #2587: Make the webdav password available as a StringTemplate system variable
- Hum. Do we have some updates on this ?
- 16:04 Bug #2560 (Pending technical review): Cpu speed search is not working
- Applied in changeset commit:03570f37d355005b6d12cd374678dc6d80937a07.
- 13:57 Bug #2560: Cpu speed search is not working
- Vincent MEMBRÉ wrote:
> What if we truncated speed ? a speed of xxxx.yy mhz would became xxxx mhz ?
>
> whith xxx... - 13:12 Bug #2560: Cpu speed search is not working
- What if we truncated speed ? a speed of xxxx.yy mhz would became xxxx mhz ?
whith xxxx we could use ldap integer a... - 12:54 Bug #2560 (Discussion): Cpu speed search is not working
- I found the origin of that problem.
It came from the inventory ldap schema. cpu speed has no Ordering Value, it ca... - 16:01 Revision 03570f37 (rudder): fixes #2560 Cpu speed is now an Integer in ldap, search on that field are now working
- 16:01 Revision 03570f37 (ldap-inventory): fixes #2560 Cpu speed is now an Integer in ldap, search on that field are now working
- 14:46 Bug #2565 (Pending technical review): When we receive an inventory from a deleted node, the inventory stays deleted
- Applied in changeset commit:1be8a0d219258df6022d7879bed8de14937b3a7e.
- 14:46 Revision 1be8a0d2 (rudder): Fixes #2565 : when a node has been removed, and a new inventory arrives for it, it comes back into pending
- 14:46 Revision 1be8a0d2 (ldap-inventory): Fixes #2565 : when a node has been removed, and a new inventory arrives for it, it comes back into pending
- 14:02 Bug #2375: The generated rules permissions are not correct
- Matthieu, can you please add a configuration in 2.4 to force Jetty's umask to 027 (in it's init script I presume). Th...
- 12:21 Bug #2375: The generated rules permissions are not correct
- OK, let's go for the UMASK, we will see if anything breaks - I didn't come to think to anything that should, but who ...
- 11:03 User story #2574 (Released): Always display Node information (node name, last update date) in inventory view
- 11:03 User story #2574: Always display Node information (node name, last update date) in inventory view
- This looks much better, thanks Vincent. I'm not entirely convinced about the dark background for the title, but I'm n...
- 10:28 User story #2574: Always display Node information (node name, last update date) in inventory view
- I made it bigger and in white font, and it looks better like this! Thanks Jon!
I add a screenshot of what it looks... - 10:24 Revision ae7d4370 (rudder): Ref #2574 make title bar easiez too read (white text and bigger font)
- 10:24 Revision 4a20d924 (rudder): Ref #2574 make title bar easiez too read (white text and bigger font)
- 09:19 Bug #2303 (Pending technical review): The modification of the Distribute Policy PT have not been integrated in the rootServerInitialPromises
- This task has been completed => http://www.rudder-project.org/redmine/projects/policy-templates/repository/revisions/...
- 08:46 User story #860: Manage the passwords during the installation
- Matthieu CERDA wrote:
> Well, I am sorry but using "=" is kind of difficult for one simple reason: "RUDDER_OPENLDAP_... - 08:21 User story #860 (In progress): Manage the passwords during the installation
- Well, I am sorry but using "=" is kind of difficult for one simple reason: "RUDDER_OPENLDAP_BIND_DN=cn=Manager,dc..."...
- 00:29 User story #860: Manage the passwords during the installation
- Another comment: please use "=" as the key/value separator in /opt/rudder/etc/rudder-passwords.conf as specified in t...
- 00:15 User story #860: Manage the passwords during the installation
- I noticed this commit, https://github.com/Normation/rudder-techniques/commit/581fb61d56e544bae540d348b5ed20ed265b7ac8...
- 08:21 Bug #2584: Technique "User Management": Does not work if group already exist
- Jonathan CLARKE wrote:
> I'm not sure I understand what the problem here is exactly. Is is that the useradd command ... - 00:32 Bug #2584: Technique "User Management": Does not work if group already exist
- I'm not sure I understand what the problem here is exactly. Is is that the useradd command tries to create the group ...
Also available in: Atom