Modify

Ticket #980 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

Packages and gpg-pubkey on RHEL5

Reported by: https://www.google.com/accounts/o8/id?id=AItOawm53g_OvEixgi55cBdUXTHWrAwrQcK1PlU Owned by: solj
Priority: major Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-client Version: 1.0
Keywords: Cc: [email protected]

Description

Hello,

I've been trying to fix a problem using bcfg2 1.1.1. When I run the client on a RHEL5 system, I see this in the server logs:

Jan 18 12:37:55 cfgserver bcfg2-server[23783]: Got unknown entries Jan 18 12:37:55 cfgserver bcfg2-server[23783]: gpg-pubkey?

I tried to find some documentation on making gpg-pubkey work with the Packages plugin, but the documentation is not particularly good:

1.) http://docs.bcfg2.org/dev/appendix/guides/fedora.html mention BoundPackage? sections that won't even pass bcfg2-repo-validate

2.) http://docs.bcfg2.org/dev/appendix/guides/converging_rhel5.html also mention BoundPackage? sections that won't even pass bcfg2-repo-validate, and it says type="yum" (which should fail, gpg-pubkey isn't in yum)

3.) http://docs.bcfg2.org/dev/client/tools/yumng.html only mentions Pkgmgr settings

4.) http://docs.bcfg2.org/quickstart/centos.html actually mentions the version requirement (saying version="foo"), however, even with that set in a subscribed group, I still see in the Server logs the error about the unknown entry gpg-pubkey.

5.) Lastly, I'm not sure if it's related, but when I run the client, I alwas see this python trace: Unexpected failure of verification method for entry type Package Traceback (most recent call last):

File "/usr/lib/python2.4/site-packages/Bcfg2/Client/Tools/init.py", line 138, in Inventory

states[entry] = func(entry, mods)

File "/usr/lib/python2.4/site-packages/Bcfg2/Client/Tools/YUMng.py", line 451, in VerifyPackage?

_POs = [ p for p in POs if p.version == nevraversion? \

KeyError?: 'version'

Attachments

Change History

comment:1 Changed 12 years ago by https://www.google.com/accounts/o8/id?id=AItOawm53g_OvEixgi55cBdUXTHWrAwrQcK1PlU

I removed a separate group entry which tried to add the gpg-pubkey "package", and that eliminated the python stack trace, #5.

comment:2 Changed 12 years ago by solj

  • Owner changed from desai to solj
  • Status changed from new to accepted
  • Milestone set to Bcfg2 1.1.2 Release (Bugfix)

comment:3 in reply to: ↑ description Changed 11 years ago by solj

Replying to https://www.google.com/accounts/o8/id?id=AItOawm53g_OvEixgi55cBdUXTHWrAwrQcK1PlU:

Hello,

I've been trying to fix a problem using bcfg2 1.1.1. When I run the client on a RHEL5 system, I see this in the server logs:

Jan 18 12:37:55 cfgserver bcfg2-server[23783]: Got unknown entries Jan 18 12:37:55 cfgserver bcfg2-server[23783]: gpg-pubkey?

I tried to find some documentation on making gpg-pubkey work with the Packages plugin, but the documentation is not particularly good:

1.) http://docs.bcfg2.org/dev/appendix/guides/fedora.html mention BoundPackage? sections that won't even pass bcfg2-repo-validate

This documentation has been updated.

2.) http://docs.bcfg2.org/dev/appendix/guides/converging_rhel5.html also mention BoundPackage? sections that won't even pass bcfg2-repo-validate, and it says type="yum" (which should fail, gpg-pubkey isn't in yum)

This documentation has been updated.

3.) http://docs.bcfg2.org/dev/client/tools/yumng.html only mentions Pkgmgr settings

This documentation still needs to be updated for the newer YUMng client tool.

4.) http://docs.bcfg2.org/quickstart/centos.html actually mentions the version requirement (saying version="foo"), however, even with that set in a subscribed group, I still see in the Server logs the error about the unknown entry gpg-pubkey.

The reason it shows up as an unknown entry is because Packages has no knowledge of gpg-pubkey rpms. Since Packages doesn't handle these, it is safe to ignore this message. The documentation has been updated to reflect this.

comment:4 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.1.2 Release (Bugfix) to Bcfg2 1.2.0 Release

Moving to 1.2.0. It looks like the main thing left to do here is to fully document the new YUMng client tool.

comment:5 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.2.1 Release (Bugfix)

comment:6 Changed 11 years ago by https://www.google.com/accounts/o8/id?id=AItOawnSjgovXZr-_V3vGkvMSR0pc5LDykRc1Nc

  • Status changed from accepted to closed
  • Resolution set to fixed

gpg-pubkey handling is automatic in Bcfg2 1.2, so this is no longer an issue.

comment:7 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.1 Release (Bugfix) to Bcfg2 1.2.0 Release

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.