Bcfg2 is saying packages have failed verification because their config's have changed.

[Chris Stankaitis <[email protected]…>]

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?

[solj]

Bcfg2 will take care of this situation for you. Basically what you want to do is group the files belonging to the package failing verification in the same Bundle. Bcfg2 will automatically mark these so that rpm verification failures won't affect bcfg2 verification for the package.