Hide Forgot
This description generated by Andreas from an ABRT report architecture: x86_64 cmdline: component: yum executable: /usr/bin/yum kernel: 2.6.32-71.18.2.el6.x86_64 package: yum-3.2.27-14.el6_0.1 reason: keys.py:247:show_key:AttributeError: 'list' object has no attribute 'version' release: Red Hat Enterprise Linux Server release 6.0 (Santiago) reproduce: 1. yum install yum-plugin-keys 2. yum keys-info 3. time: 1300901775 uid: 500 backtrace: keys.py:247:show_key:AttributeError: 'list' object has no attribute 'version' Traceback (most recent call last): File "/usr/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 254, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 109, in main result, resultmsgs = base.doCommands() File "/usr/share/yum-cli/cli.py", line 357, in doCommands return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) File "/usr/lib/yum-plugins/keys.py", line 184, in doCommand self.show_key(base, key) File "/usr/lib/yum-plugins/keys.py", line 247, in show_key gpg_cert.version, gpg_cert.user_id, AttributeError: 'list' object has no attribute 'version' Local variables in innermost frame: gpg_cert: [<yum.pgpmsg.pgp_certificate object at 0x15da550>] self: <keys.KeysInfoCommand instance at 0x15c9ab8> rpmkeyid: '6b8d79e6-3f49313d' base: <cli.YumBaseCli object at 0x1296410> key: <keys.Key instance at 0x15dc248>
Created attachment 487097 [details] File: backtrace
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This bug might well be fixed when using the 6.1 yum and yum-utils, can someone in QA double check?
Still wondering about comment #5 ... but if not, it should be easy to fix.
Hi James, I can confirm this is already fixed in RHEL6.1 # rpm -q yum yum-plugin-keys yum-3.2.27-14.el6.noarch yum-plugin-keys-1.1.26-11.el6.noarch # yum keys-info Loaded plugins: keys, rhnplugin This system is not registered with RHN. RHN support will be disabled. Traceback (most recent call last): File "/usr/bin/yum", line 29, in <module> yummain.user_main(sys.argv[1:], exit_code=True) File "/usr/share/yum-cli/yummain.py", line 254, in user_main errcode = main(args) File "/usr/share/yum-cli/yummain.py", line 109, in main result, resultmsgs = base.doCommands() File "/usr/share/yum-cli/cli.py", line 357, in doCommands return self.yum_cli_commands[self.basecmd].doCommand(self, self.basecmd, self.extcmds) File "/usr/lib/yum-plugins/keys.py", line 184, in doCommand self.show_key(base, key) File "/usr/lib/yum-plugins/keys.py", line 247, in show_key gpg_cert.version, gpg_cert.user_id, AttributeError: 'list' object has no attribute 'version' # rpm -q yum yum-plugin-keys yum-3.2.29-17.el6.noarch yum-plugin-keys-1.1.30-6.el6.noarch # yum keys-info Loaded plugins: keys Type : GPG Rpm Key ID : 2fa658e0-45700c69 Key owner : Red Hat, Inc. (auxiliary key) Key email : security Repo : installed Created : Fri Dec 1 12:05:13 2006 Version : PGP Public Key Certificate v4 Primary ID : Red Hat, Inc. (auxiliary key) <security> Algorithm : DSA (Digital Signature Standard) Fingerprint: 43a6e49c4a38f4be9abf2a5345689c882fa658e0 Key ID : 45689c882fa658e0 Type : GPG Rpm Key ID : fd431d51-4ae0493b Key owner : Red Hat, Inc. (release key 2) Key email : security Repo : installed Created : Thu Oct 22 13:59:55 2009 Version : PGP Public Key Certificate v4 Primary ID : Red Hat, Inc. (release key 2) <security> Algorithm : RSA (Encrypt or Sign) Fingerprint: 567e347ad0044ade55ba8a5f199e2f91fd431d51 Key ID : 199e2f91fd431d51 keys-info done
Do we just close this then, or retest it for 6.2 and pretend we fixed it then?
I would keep it open, at least we can make sure there isn't a regression in RHEL6.2.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1703.html