Activity
From 2013-04-02 to 2013-04-02
2013-04-02
- 18:00 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- So, this is a confirmed bug, and the workaround has been tested successfully (thanks Dennis), I'm on it.
I will do... - 17:55 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- I think you can safely build this into the base Rudder Techniques. I see no reason for using a proxy to communicate w...
- 17:47 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- I'm glad this is working for you. I think we should build this into the base Rudder Techniques, and use curl's "--no-...
- 17:24 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- Now it works! The proxy was in the way:
root@winzts021:/tmp# unset http_proxy
root@winzts021:/tmp# unset https_proxy... - 17:05 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- Can you retry the exact same command, but with a:...
- 17:01 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- When running cf-agent on the server I see this:...
- 16:44 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- Also from /var/log/rudder/apache2/error.log:
[Tue Apr 02 16:04:34 2013] [error] [client 10.122.245.14] client deni... - 16:43 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- What do you mean with context name?
root@winzts021:/tmp# curl -s http://localhost:8080/endpoint/api/status
<HTML>... - 16:26 Bug #3383: Rudder status check fails if a proxy is defined in the environment
- Hi Dennis,
Did you change the context name of the application within Jetty ?
What is the output of the followin... - 16:19 Bug #3383 (Released): Rudder status check fails if a proxy is defined in the environment
- I see the following error in /var/log/rudder/webapp/XXXX_XX_XX.stderrout.log and Jetty restarts all the time (so the ...
- 17:51 User story #3384 (Rejected): We should allow the user to specify a proxy to be used with the Rudder cURL calls
- We should allow the user to specify a proxy to be used with the Rudder cURL calls
(Currently, we want to disable p... - 16:25 User story #3165: Technique "Zypper package manager configuration": implement option to specify repos per OS
- BUMP-ing the ticket.
What is the status of this ? - 15:42 User story #3290 (Pending release): Be able to have hideable sections in the Directive display
- Merge complete !
- 15:41 User story #3290: Be able to have hideable sections in the Directive display
- Merge has begun.
- 15:41 User story #3291 (Pending release): Implement sections that can be hidden/displayed in the directive form
- Applied in changeset commit:5588dbb21780060dc161edc938d4eec1a7edef88.
- 15:41 User story #3327 (Pending release): Implement sections that can be hidden/displayed in the directive form (rudder part)
- Applied in changeset commit:2653da1debbea4ad15aefadfdc25838339e9bbdb.
- 15:41 Revision 70a9e203 (rudder): Merge pull request #124 from ncharles/ust_3290/dev/3291_implement_hiddable_sections
- Fixes #3291 : add a 'foldable' attribute, with true or false value, that...
- 15:41 Revision 5588dbb2 (rudder): Merge pull request #124 from ncharles/ust_3290/dev/3291_implement_hiddable_sections
- Fixes #3291 : add a 'foldable' attribute, with true or false value, that...
- 15:38 Revision 097fd239 (rudder): Fixes #3327 : add a 'displayPriority' attribute, with high or low
- value,that determines if a section should be displayed by default or not
- 15:38 Revision 2653da1d (rudder): Fixes #3327 : add a 'displayPriority' attribute, with high or low
- value,that determines if a section should be displayed by default or not
- 15:06 Bug #3382: A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory
- Applied in changeset commit:fa1d96bec51820951976e26af4d37af648367924.
- 15:06 Bug #3382: A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory
- Applied in changeset commit:ca342087b8437ea53d647cb39559b66e4854763d.
- 15:05 Bug #3382 (Pending release): A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory
- This looks valid, thank you !
- 14:49 Bug #3382 (Pending technical review): A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory
- Pull requests here :
LDAP Inventory : https://github.com/Normation/ldap-inventory/pull/16
Rudder : https://git... - 14:41 Bug #3382 (In progress): A pristine Rudder 2.6 nightly installation fails any deployment as long as the root server did not register its own inventory
- In fact Rudder server inventory is correctly handled.
At Rudder initialisation, The node inventory is considered a... - 15:06 Revision 4fb1c30b (rudder): Merge pull request #151 from VinceMacBuche/bug_3382/Machine_Inventory_on_rudder_installation
- Fixes #3382 : Handle Missing machine inventory in NodeInfoService
- 15:06 Revision fa1d96be (rudder): Merge pull request #151 from VinceMacBuche/bug_3382/Machine_Inventory_on_rudder_installation
- Fixes #3382 : Handle Missing machine inventory in NodeInfoService
- 15:06 Revision c97df55e (rudder): Merge pull request #16 from VinceMacBuche/bug_3382/Machine_Inventory_on_rudder_installation
- Ref #3382 : When Machine Inventory moved from Pending, change the node ...
- 15:06 Revision c97df55e (ldap-inventory): Merge pull request #16 from VinceMacBuche/bug_3382/Machine_Inventory_on_rudder_installation
- Ref #3382 : When Machine Inventory moved from Pending, change the node ...
- 14:46 Revision 150286a0 (cf-clerk): Fixes #3291 : add a 'displayPriority' attribute, with high or low value,
- that determines if a section should be displayed by default or not
Fixes #3291 : fixing remarks - 14:45 Architecture #3347: Store the unexpanded version of variable in the expected reports
- 12:04 Architecture #3347 (Pending technical review): Store the unexpanded version of variable in the expected reports
- Modification taken into account
- 14:44 Revision c3351368 (rudder): Fixes #3382 : Handle Missing machine inventory in NodeInfoService
- 14:44 Revision ca342087 (rudder): Fixes #3382 : Handle Missing machine inventory in NodeInfoService
- 14:41 Revision 3f72f7dd (rudder): Ref #3382 : When Machine Inventory moved from Pending, change the node Inventory container change too
- 14:41 Revision 3f72f7dd (ldap-inventory): Ref #3382 : When Machine Inventory moved from Pending, change the node Inventory container change too
- 12:00 Revision 73125a1d (rudder): Fixes #3347 : store unexpanded and expanded version of variables for
- more robust reporting
- 12:00 Revision bbe41c21 (rudder): Fixes #3347 : store unexpanded and expanded version of variables for
- more robust reporting
Also available in: Atom