Bug 561553 - Package GPG reading broken
Summary: Package GPG reading broken
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 0.7
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space13
TreeView+ depends on / blocked
 
Reported: 2010-02-03 21:46 UTC by Justin Sherrill
Modified: 2011-02-08 08:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-08 08:40:50 UTC
Embargoed:

Attachments (Terms of Use)

Description Justin Sherrill 2010-02-03 21:46:19 UTC 
Pushing or syncing packages to spacewalk hasn't properly read the GPG keys since spacewalk 0.6 i believe.  I *think* that this commit broke it:

ef3bece2f536e2ea86456e872f53fa47b18dfc6d


(Where we read the rpm header in a different way that didnt' cause the rpmdatabase to be loaded within the apache process, causing a segfault).


I thought I had opened a bug on this, but apparently not.


To reproduce:

1.  rhnpush a redhat/centos/fedora package into a spacewalk channle
2.  view the package from within the channel packages list page

Expected results:
   Content Provider shows the proper value (Red Hat Inc., Fedora, etc...)

Actual Results
   Content provider shows "Unkown"
Comment 1 Michael Mráka 2010-03-18 12:50:56 UTC 
commit 0cc7559e9e7acf75414191e26a48229ffc9ea8ef
    561553 - commit what we've done
    
    there are pending inserts into rhnPackageKeyAssociation which were
    originally commited inside processPackageKeyAssociations()
    unfortunately this commit was removed in
    58f5b315e06d1057f306f7f258a1f3a3d3d1baf7 with a hope that thing are
    being commited in some upper function
Comment 2 Jan Pazdziora 2010-11-19 16:04:37 UTC 
Mass-moving to space13.
Comment 3 Michael Mráka 2011-01-28 13:46:14 UTC 
Fixed in bug 671464, bug 671465 and bug 671462.
Comment 4 Tomas Lestach 2011-02-03 12:21:08 UTC 
Moving ON_QA ...
Comment 5 Tomas Lestach 2011-02-08 08:40:50 UTC 
This bug has been fixed in Spacewalk 1.3.
Note You need to log in before you can comment on or make changes to this bug.