Custom Query (894 matches)

Using bcfg2 1.0.1 : 'bcfg2-repo-validate -v' reports that genshi bundles don't exist. The bundle 'awstats.genshi' does exist, but not as an xml file. The genshi bundle is functional, but the message is distracting. Very minor annoyance.

Sample error message: * Warning: Bundle /var/lib/bcfg2/Bundler/awstats.xml referenced, but does not exist.

Unexpected failure in BindStructure?: Package wgen-python26-cx_Oracle Traceback (most recent call last):

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Core.py", line 232, in BindStructure?

self.Bind(entry, metadata)

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Core.py", line 266, in Bind

metadata)

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Plugins/Pkgmgr.py", line 153, in BindEntry?

Bcfg2.Server.Plugin.PrioDir?.BindEntry?(self, entry, metadata)

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Plugin.py", line 786, in BindEntry?

attrs = self.get_attrs(entry, metadata)

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Plugin.py", line 793, in get_attrs

for src in list(self.entries.values())]:

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Plugin.py", line 743, in Cache

self.pnode.Match(metadata, cache[1])

File "/home/cpennington/.virtualenvs/py26-bcfg2/lib/python2.6/site-packages/Bcfg2/Server/Plugins/Pkgmgr.py", line 50, in Match

if self.predicate(metadata):

TypeError?: <lambda>() takes exactly 2 arguments (1 given)

Right now under Packages plugin in 1.0 if I update a package in my repo that new version will push out the next time my clients check in. This may not be a good thing depending on the environment. Under pre 1.0 versions this was mitigated by having to regen the PkgMGR xml to update the versions before bcfg2 would "patch" the box. Under 1.0 however unless you want to set a BoundPackage? statement for every package there is no way to stop bcfg2 from upgrading your system in the event your yum repo is updated.

Could a config variable be added to Packages/config.xml possibly

<Update>Yes|no</Update>

which would allow me to tell bcfg2 to verify the package but not update them if there is a newer version? then when the maintenance window happens, or the patchs are testing in staging I can just flip the config to <Update>Yes</Update> and let the boxes patch.

I think this will let me keep the awesome new functionality of the Packages plugin while also giving me some control over when/how my boxes get patched.