Custom Query (894 matches)

Under 1.0 Using the Packages Plugin. Bcfg2 is saying that packages are failing verification because their configs have changed. The ironic thing of course is that bcfg2 itself made the config changes in question:

Package pam failed verification. Package sendmail failed verification.

From what I have been told of the process bcfg2 does a rpm -V on the package name:

[[email protected]… conf.d]# rpm -V pam ....L... c /etc/pam.d/system-auth [[email protected]… conf.d]# rpm -V sendmail S.5....T c /etc/mail/sendmail.cf S.5....T c /etc/mail/sendmail.mc S.5....T c /var/log/mail/statistics

I think bcfg2 needs to have some logic put into it so that it doesn't fail the package because of a config it changed.

RPM is not bcfg2 aware so this has to be done on the bcfg2 level. Bcfg2 knows it manages the config, and if so then it can skip the complaint from the RPM verify.

I would prefer a smarter solution then getting into the Packages plugin equivalent of the verify_flags issue with the older versions of bcfg2 if possible.

Not sure what do you think bcfg2 guru?

I upgraded my Bcfg2 install to SVN revision 5481 and my client will no longer install packages which are missing on a server.

I am using YUMng and the Packages plugin.

a few weeks ago you gave me a patch for YUMng.py since I was having the same issue. the patch did the following.

[[email protected]… conf.d]# diff -u -w ~chris/YUMng.py /usr/lib/python2.4/site-packages/Bcfg2/Client/Tools/YUMng.py --- /home/chris/YUMng.py 2009-10-19 09:39:08.000000000 -0400 +++ /usr/lib/python2.4/site-packages/Bcfg2/Client/Tools/YUMng.py 2009-10-14 10:00:26.000000000 -0400 @@ -227,7 +227,7 @@

cmdrc, output = self.cmd.run(pkgtool % " ".join(install_args)) if cmdrc == 0:

# The yum command succeeded. All packages installed.

• self.logger.info("Single Pass for Install Succeded")

+ self.logger.info("Single Pass for Install Succeeded")

self.RefreshPackages?()

else:

# The yum command failed. No packages installed.

@@ -263,7 +263,7 @@

cmdrc, output = self.cmd.run(pkgtool % " ".join(upgrade_args)) if cmdrc == 0:

# The yum command succeeded. All packages installed.

• self.logger.info("Single Pass for Install Succeded")

+ self.logger.info("Single Pass for Install Succeeded")

self.RefreshPackages?()

else:

# The yum command failed. No packages installed.

@@ -338,7 +338,7 @@

for inst in pkg:

if pkg.get('name') != 'gpg-pubkey':

pkg_arg = pkg.get('name') + '-'

• if inst.haskey('epoch'):

+ if inst.attrib.has_key('epoch'):

pkg_arg = pkg_arg + inst.get('epoch') + ':'

pkg_arg = pkg_arg + inst.get('version') + '-' + inst.get('release') if 'arch' in inst.attrib:

Note. I used this new YUMng.py and it is still unable to install packages so it appears to be something new. Please let me know how I can help track this down and fix it.

Hi,

There are are number of problems with the Makefile provided in solaris/ that prevents bcfg2 building on Solaris 10:

• setup.py expects lib/<python-version>/site-packages/ to exist

No such file or directory: '/export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/test-easy-install-9272.pth'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/

This directory does not currently exist.  Please create it and try again, or
choose a different installation directory (using the -d or --install-dir
option).

• setup.py expects lib/<python-version>/site-packages/ to be in $PYTHON_PATH

/usr/local/bin/python -E -c pass
TEST FAILED: /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/ does NOT support .pth files
error: bad install directory or PYTHONPATH

You are attempting to install a package to a directory that is not
on PYTHONPATH and which Python does not read ".pth" files from.  The
installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /export/home/df3804/bcfg2-1.2.1/solaris/lib/python2.6/site-packages/

and your PYTHONPATH environment variable currently contains:

    ''

Here are some of your options for correcting the problem:

* You can choose a different installation directory, i.e., one that is
  on PYTHONPATH or supports .pth files

* You can add the installation directory to the PYTHONPATH environment
  variable.  (It must then also be on PYTHONPATH whenever you run
  Python and want to use the package(s) you are installing.)

* You can set up the installation directory to support ".pth" files by
  using one of the approaches described here:

  http://peak.telecommunity.com/EasyInstall.html#custom-installation-locations

Please make the appropriate changes for your system and try again.

• setup.py generates an "extracted egg". i.e. lib/python2.6/site-packages/Bcfg2-1.2.1-py2.6.egg/{Bcfg2,share} instead of the more traditional lib/python2.6/site-packages/Bcfg2/ & share/
• prototype.* contains an out-of-date list files to include in the package (e.g. lib/python2.6/site-packages/Bcfg2/Server/Plugins/Packages.py does not exist anymore).

It is unclear to me if an updated prototype.bcfg2 and prototype.bcfg2-server should be provided or if these should be generated dynamically. As a first attempt, I have produced gen-prototypes.sh that produces these dynamically. Although, this could be considered more dirty than updating the prototypes manually every release.

Attached to this ticket is the following:

• Makefile - A replacement solaris/Makefile that solves the issues above and also changes the build prefix from $(PWD) to $(PWD)/build.
• gen-prototypes.sh - A script to generate suitable prototype.* files.