Activity
From 2012-12-04 to 2012-12-04
2012-12-04
- 19:06 Bug #2642 (Pending technical review): Error message in initial promises about non-existant share for node should be clearer
- The pull request is here : https://github.com/Normation/rudder-techniques/pull/7
- 18:37 Bug #2642: Error message in initial promises about non-existant share for node should be clearer
- Nicolas CHARLES wrote:
> Originally, this ticket targets only the initial promises, but the message seems to state t... - 17:49 Bug #2642: Error message in initial promises about non-existant share for node should be clearer
- Originally, this ticket targets only the initial promises, but the message seems to state that an existing configurat...
- 17:41 Bug #2642 (In progress): Error message in initial promises about non-existant share for node should be clearer
- 17:32 Bug #2642: Error message in initial promises about non-existant share for node should be clearer
- Nicolas CHARLES wrote:
> There is no easy way to distinguish between a Server not repsonding (down, or wrong IP), an... - 12:37 Bug #2642: Error message in initial promises about non-existant share for node should be clearer
- There is no easy way to distinguish between a Server not repsonding (down, or wrong IP), and the path not existing (n...
- 09:57 Bug #2642: Error message in initial promises about non-existant share for node should be clearer
- NCH, could you take a look to that one ?
- 19:03 Revision 02ba2e8e (rudder-techniques): Fixes #2642 : add a warning message if the node cannot connect to the server
- 18:39 Bug #3037: After an upgrade from 2.4.0~beta4 to 2.4.0~rc1, the file logback.xml is not updated
- Nicolas PERRON wrote:
> I'm not sure to know how to deal with this. sed seems to not be adapted to this work.
>
>... - 15:14 Bug #3037 (Discussion): After an upgrade from 2.4.0~beta4 to 2.4.0~rc1, the file logback.xml is not updated
- I'm not sure to know how to deal with this. sed seems to not be adapted to this work.
I have the feeling that the ... - 15:03 Bug #3037 (In progress): After an upgrade from 2.4.0~beta4 to 2.4.0~rc1, the file logback.xml is not updated
- This is a case a little more touchy.
It happens because of #2857 (consider logback.xml as a configuration file [no a... - 17:28 Bug #2168: List of Policy Instances is not a link in popup of applicable policies when accepting a new node
- François ARMAND wrote:
> That was not corrected in 2.4, so we still have the bug.
>
> I propose to move the last... - 11:49 Bug #2168: List of Policy Instances is not a link in popup of applicable policies when accepting a new node
- That was not corrected in 2.4, so we still have the bug.
I propose to move the last comment as a new feature requ... - 14:49 Bug #2805: After a migration from 2.3 to 2.4.0~beta3, if a migration has been made with a wrong git branch on /var/rudder/configuration-repository it is impossible to return in a normal state
- A workaround has been made here: #2802
This is a situation which should not be able to reproduce since like the desc... - 09:52 Bug #2805 (Discussion): After a migration from 2.3 to 2.4.0~beta3, if a migration has been made with a wrong git branch on /var/rudder/configuration-repository it is impossible to return in a normal state
- NPE, it seems that there is a workaround for that bug? Could you please give some more information and close it if it...
- 11:34 Bug #2919 (Rejected): cf-agent seems to keep running for a long time sometimes
- 11:33 Bug #2919 (Discussion): cf-agent seems to keep running for a long time sometimes
- This seems like a duplicate of #3013
- 11:33 User story #3013: Create a new cron entry that checks if cf-execd AND cf-agent are running, and if not launches cf-agent
- I update this ticket to clearly state that it checks if more than 5/8 cf-agent are running, and if so, TERMs/KILLs them
- 10:07 Architecture #1545: Fix hack for rudder-reports SuSE RPM
- Nicolas PERRON wrote:
> I suppose we should "fix" the package rudder-reports with using the same implementation with... - 10:06 Architecture #1545: Fix hack for rudder-reports SuSE RPM
- This is clearly not a bug, and will be added in some next version.
- 10:02 User story #2221 (New): Check which packages are installed frequency
- 10:01 Bug #2401 (Discussion): rudder-server Installation : chrome://net-internals/#httpThrottling
- 09:54 Bug #2804 (Rejected): In rudder upgrade, the Rudder Technique Reference Library attribute in rudder-wbe.properties should be checked with a more flexbile way
- This is far away from Rudder standard use, and we just don't support it.
- 09:29 Revision 55b4340f (rudder-techniques): Merge branch 'branches/rudder/2.3' into branches/rudder/2.4
Also available in: Atom