Activity
From 2018-06-12 to 2018-06-12
2018-06-12
- 17:32 Revision 036edcc3 (ncf): Fixes #12777: Broken logger_rudder test in 4.3
-
15:36 User story #7688 (Rejected): Add a getting started section in the manual
- This will be a separated guide.
-
- PR https://github.com/Normation/ncf/pull/774
-
-
- ...
-
-
- This has been fixed internally in packaging scripts by using openssl 1.0 for now.
-
14:47 Bug #12535: Variable expansion in cron technique
- Hello, sorry I missed the first notification.
I am certain I double checked the variable name and prefix. -
08:31 Bug #12535: Variable expansion in cron technique
- Hello jean, any news on that ?
-
- It was only server-side, closing.
-
- Since 4.3 it is possible with most techniques in latest version. See #11851 to track this migration, closing this tic...
-
- It has been done for 4.1, closing.
-
14:31 User story #12614: Add scripts to help migrate techniques to rudder server command
- 2 bash scripts where added to automate the technique migration:
* rudder directive replace [-iIvdq] [-c] -o <old-dir... -
- such classes are valid since CFEngine 3.8.0, so it won't break any supported Rudder version.
-
- Closing as old package method/technique are deprecated.
-
- Fixed since CFEngine 3.7.0 (Rudder 3.2+), see upstream issue for reference, closing.
-
- "latest" version specification works well with the new package technique, closing.
-
14:12 Bug #12694: In Rudder 4.1, we cannot do reporting using a variable defined in a generic method
- Actually, the generic_variable_definition are the only variables (with node properties) that works in reporting in t...
-
14:01 Bug #12694: In Rudder 4.1, we cannot do reporting using a variable defined in a generic method
- All variables defined using generic_variable_definition will also be ignored (in fact using variable that are only de...
-
- Ok, Node properties work. It's "simply" all variables defined in technique editor that cannot be used
-
- In 4.1 this is a cfengine problem
This has been solved in 4.3 by changing hos reports work. -
-
-
- It is possible in the new Packages technique, closing.
-
- Old package methods are now deprecated, closing.
-
- Technique upgrade has been implemented too, and backup is done automatically at package upgrade/remove.
-
- Possible in the (not so) new "Packages" technique, closing.
-
-
- This is not relevant any more, we use the new new package method
-
- This bug has been fixed in Rudder 4.1.9 and 4.2.3 which were released today.
* 4.1.9: "Announce":http://www.rudder... -
- 12:14 Revision 1a9522fd (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 12:14 Revision 2595193e (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 12:14 Revision 9c42264e (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 12:14 Revision af4a36db (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 12:14 Revision c412976e (rudder): Change version of pom.xml to 4.3.2
- 12:14 Revision cd25bf82 (rudder): Change version of pom.xml to 4.3.2
- 12:14 Revision afa5fece (rudder): Change version of pom.xml to 4.3.2
- 12:14 Revision df121f5e (rudder): Change version of pom.xml to 4.3.2
-
-
11:38 Revision a07ea64f (rudder): Fixes #12760: cannot add two node properties at the same time from inventory
- 10:16 Revision 42251a6c (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:16 Revision 30eaf10a (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:16 Revision 8f83e278 (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:16 Revision 6817b4c4 (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:16 Revision 24b11000 (rudder): Change version of pom.xml to 4.3.2
- 10:16 Revision 36057a90 (rudder): Change version of pom.xml to 4.3.2
- 10:16 Revision a4174db0 (rudder): Change version of pom.xml to 4.3.2
- 10:16 Revision 710b7672 (rudder): Change version of pom.xml to 4.3.2
- 10:14 Revision 1a9522fd (scala-ldap): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:14 Revision c412976e (scala-ldap): Change version of pom.xml to 4.3.2
- 10:14 Revision 9c42264e (parent-pom): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:14 Revision afa5fece (parent-pom): Change version of pom.xml to 4.3.2
- 10:14 Revision af4a36db (ldap-inventory): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:14 Revision df121f5e (ldap-inventory): Change version of pom.xml to 4.3.2
- 10:14 Revision 2595193e (rudder-commons): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:14 Revision cd25bf82 (rudder-commons): Change version of pom.xml to 4.3.2
- 10:14 Revision 35ebfd8c (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 10:14 Revision cef7725a (rudder): Change version of pom.xml to 4.3.2
-
- Applied in changeset commit:ldap-inventory|a07ea64ff538fc5c7c267b4640d81278019f7903.
-
- PR https://github.com/Normation/ldap-inventory/pull/134
-
-
-
-
- Did you try with changing localhost definition in /etc/hosts
For example using 127.0.0.1 instead of ::1
-
- This was due to a failed merge, this has been fixed.
-
- Hello Pierrick, any news ?
-
- Hello Pierrick, any news ?
-
- And if you try to update a category with a depth over 5 you get a 500 too
- 08:16 Revision 42251a6c (scala-ldap): Change version of pom.xml to 4.3.3-SNAPSHOT
- 08:16 Revision 24b11000 (scala-ldap): Change version of pom.xml to 4.3.2
- 08:16 Revision 8f83e278 (parent-pom): Change version of pom.xml to 4.3.3-SNAPSHOT
- 08:16 Revision a4174db0 (parent-pom): Change version of pom.xml to 4.3.2
- 08:16 Revision 6817b4c4 (ldap-inventory): Change version of pom.xml to 4.3.3-SNAPSHOT
- 08:16 Revision 710b7672 (ldap-inventory): Change version of pom.xml to 4.3.2
- 08:16 Revision 30eaf10a (rudder-commons): Change version of pom.xml to 4.3.3-SNAPSHOT
- 08:16 Revision 36057a90 (rudder-commons): Change version of pom.xml to 4.3.2
- 08:16 Revision 16ed3d49 (rudder): Change version of pom.xml to 4.3.3-SNAPSHOT
- 08:16 Revision e0a33da7 (rudder): Change version of pom.xml to 4.3.2
Also available in: Atom