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.

At this point in time you can run bcfg2 in a dry run mode which will show you what files will change and in a manual mode where you need to approve the changes before they happen, but to the best of my knowledge there is no easy way to get bcfg2 to tell you what it's going to change inside a config file. You can run paranoid mode and then diff the change against the backup but by that time you have already made the change and possibly made a mistake in your config file.

I think it would be very useful if bcfg2 client could be run in a mode that would:

1) Inform "we are going to change configfile X

2) provide an svn style diff of the old vs new config.

That way you can run in a dry-run + diff report mode and it will show you all the changes not just that it will change a config file. before you apply the changes live.

Right now this is a very manual process as far as I know.