Custom Query (894 matches)
Results (46 - 48 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#1070 | solj | J davis <[email protected]…> | fixed | Packages tb and dep resolution broken in rc2 |
Description |
I'm getting a Packages trace back on the server and yum dependancy resolution problems with the latest rc. bcfg2-server 1.2.0rc2 ubuntu 11.04 x86_64 bcfg2 1.2.0rc2 on CentOS 5.7 x86_64 On the server I see Plugin Packages: unexpected structure validation failure Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Core.py", line 189, in validate_structures plugin.validate_structures(metadata, data) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/__init__.py", line 115, in validate_structures collection=collection) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/__init__.py", line 149, in _build_packages packages, unknown = collection.complete(base) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/Yum.py", line 454, in complete return Collection.complete(self, packagelist) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/Collection.py", line 150, in complete self.virt_pkgs[pgrps] = self.get_vpkgs() File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/Collection.py", line 109, in get_vpkgs s_vpkgs = source.get_vpkgs(self.metadata) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/Yum.py", line 751, in get_vpkgs rv = Source.get_vpkgs(self, metadata) File "/usr/lib/pymodules/python2.7/Bcfg2/Server/Plugins/Packages/Source.py", line 170, in get_vpkgs for key, value in list(self.provides[agrp].items()): KeyError: 'x86_64' There is no error on the client side. sources.xml is comprised of several entries like this: <Source type="yum" rawurl="http://repo/centos5.7-x86_64/RPMS.os"> <Arch>x86_64</Arch> <Arch>i386</Arch> </Source> I'm seeing many more unmanaged/extra entries on the yum clients than I did with rc1. For instance, the package bcfg2 is part of the clients config. # rpm -qR bcfg2 /bin/sh /usr/bin/python2.4 config(bcfg2) = 1.2.0rc2-0.1 python(abi) = 2.4 python-lxml >= 0.9 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 # rpm -q --whatprovides python python-2.4.3-44.el5_7.1.x86_64 # rpm -q --whatprovides /bin/sh bash-3.2-32.el5.x86_64 The bcfg2 package itself shows up as managed/correct, however, both python and bash show up as unmanaged/extra. |
|||
#1125 | desai | J. Davis <[email protected]…> | fixed | implicitly created directories getting bad permissions |
Description |
Given entries like this: <BoundPath? name='/path/to/some/dir' type='directory' perms='755'/> bcfg2 happily creates the folder and all intermediate paths that don't yet exist. Problem is those intermediates are all created according to the shell's umask rather than the permissions defined in the entry. Bcfg2 version is 1.2.1. |
|||
#1130 | desai | J. Davis <[email protected]…> | fixed | Apt sources no longer contain "components" |
Description |
After upgrading from 1.2.1 to 1.2.3 the following template code ceased to function: {% for s in metadata.Packages.sources %}\ deb ${s.url}${s.version} {% for comp in s.components %}$comp {% end %} {% end %}\ The "components" list attribute now appears to be a "component" string. Not sure if the docs just need updating: http://docs.bcfg2.org/server/plugins/generators/packages.html#generating-client-apt-yum-configurations or if there is also a code change required. Also not sure if the use of the "groups" attribute in the example is accurate. I don't see it in my environment. |