Custom Query (894 matches)
Results (76 - 78 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#1015 | solj | https://profiles.google.com/holger.weiss | fixed | Interactive client repeatedly asks whether to modify 'important' files |
Description |
"bcfg2 -I" gets confused when 'important' files are modified: the diff/prompt pairs are shown repeatedly (all in all: four times), and the prompt must be confirmed twice. |
|||
#1028 | solj | https://www.google.com/accounts/o8/id?id=AItOawlJa6QJcUnwqaUiOAgop4U4wANp_y0hDu4 | fixed | Add support to LANG=es_ES in the chkconfig plugin |
Description |
If I run the chkconfig command in a es_ES locale environment the status output is different from what the plugin wants and the service checks always fail: ec4:~# chkconfig --list NetworkManager 0:desactivado 1:desactivado 2:desactivado 3:desactivado 4:desactivado 5:desactivado 6:desactivado acpid 0:desactivado 1:desactivado 2:activo 3:activo 4:activo 5:activo 6:desactivado "on" == "activo" "off" == "desactivado" Perhaps a solution could be unsetting the LANG environment variable before the chkconfig execution. |
|||
#1029 | solj | https://www.google.com/accounts/o8/id?id=AItOawkfHvWdYf7g8kSZA32s7dhK0Xig9JKo_CA | fixed | Action entries cannot be whitelisted/blacklisted |
Description |
<Action ...> configuration entries bypass the Decisions' whitelist/blacklist filtering by the client. A simple example: <Bundle name='a'> <BoundAction name='a1' command='/usr/bin/touch /tmp/a1_executed' when='always' status='check' timing='post' /> </Bundle> Then run bcfg2 -l whitelist. The Action's command will get executed, even though it's not whitelisted. This behaviour doesn't seem to be documented. IMHO, the promise of white/blacklist safety is not fulfilled here. (Eg. I use Actions for setting up static routing using just the 'route' command, so an Action is the sole element of the Bundle, and, obviously, I need to control which hosts actually execute it). I believe it happens in Client.Frame.Install(), where tool.BundleUpdated() and tool.BundleNotUpdated() are called unconditionally. Also, in Client.Frame.Decide() some Actions get run regardless of their white/blacklist status. (Perhaps there are some other places where Actions can get run, but my understanding of the code is not good enough to find them.) A partial workaround could be to add to the Bundle an artificial config file (crafted just to mirror the actual "volatile" configuration), and set the Action to when='modified'. This would still be fragile for some non-trivial Bundles and commands, though. /mkd |