Custom Query (894 matches)
Results (58 - 60 of 894)
Ticket | Owner | Reporter | Resolution | Summary |
---|---|---|---|---|
#874 | solj | Jack Neely <[email protected]…> | fixed | Ignore tag doesn't verify |
Description |
I have a Bundle that looks like this: <Bundle name='rlbase' version='2.0'> <!-- Misc configuration settings for Realm Linux --> <!-- These packages have changed config files that I don't currently manage. --> <Package name="setup"> <Ignore name="/etc/printcap"/> <Ignore name="/etc/aliases"/> </Package> <Package name="initscripts"> <Ignore name="/etc/inittab"/> <Ignore name="/etc/sysconfig/init"/> </Package> </Bundle> The Bundle works. Even though I'm not managing the above files Bcfg2 ignores the fact that they have changed from what the RPM database says they should be. However the bcfg2-repo-validate tool reports that this is horridly wrong. /srv/bcfg2/root/Bundler/rlbase.xml ***FAILS*** to verify <---- /srv/bcfg2/root/Bundler/rlbase.xml:8: element Package: Schemas validity error : Element 'Package': Character content is not allowed, because the content type is empty. /srv/bcfg2/root/Bundler/rlbase.xml:8: element Package: Schemas validity error : Element 'Package': Element content is not allowed, because the content type is empty. /srv/bcfg2/root/Bundler/rlbase.xml:13: element Package: Schemas validity error : Element 'Package': Character content is not allowed, because the content type is empty. /srv/bcfg2/root/Bundler/rlbase.xml:13: element Package: Schemas validity error : Element 'Package': Element content is not allowed, because the content type is empty. /srv/bcfg2/root/Bundler/rlbase.xml fails to validate |
|||
#880 | desai | Jack Neely <[email protected]…> | fixed | GPG Keys with YUMng and Packages |
Description |
Being that I'm doing everything with the YUMng and Packages toolage I had to do the following to get GPG keys setup and installed: <BoundPackage name='gpg-pubkey' type='rpm'> <Instance simplefile='/etc/pki/rpm-gpg/RPM-GPG-KEY-RealmLinux-0' version='b274beb2' release='3cfe5d73'/> </BoundPackage> Normal <Package> tags got the type argument changed to 'yum' and Packages tried to yum install gog-pubkey-foo-bar which was unfun. |
|||
#883 | desai | Jack Neely <[email protected]…> | fixed | Package tag arguments fails repo verification |
Description |
I have the following inside a Bundle: <Bundle name='auth' version='2.0'> [SNIP] <Package name='pam' verify='false'/> [SNIP] </Bundle> That information gets past to the Bcfg2 client and works. Package verification is turned off properly. However, using bcfg2-repo-validate to check the XML I get: bcfg2-repo-validate -C /srv/bcfg2/itd-cls-test/bcfg2.conf /srv/bcfg2/itd-cls-test/Bundler/auth.xml ***FAILS*** to verify <---- /srv/bcfg2/itd-cls-test/Bundler/auth.xml:16: element Package: Schemas validity error : Element 'Package', attribute 'verify': The attribute 'verify' is not allowed. /srv/bcfg2/itd-cls-test/Bundler/auth.xml fails to validate This should validate. I imagine there might be other options that are not setup correctly as well. I'm running a patched version of Bcfg2 1.0.1 |