Bug 556761 - Content Provider Unknown if satellite-sync runs on NFS mounted /var/satellite
Summary: Content Provider Unknown if satellite-sync runs on NFS mounted /var/satellite
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 530
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Šimon Lukašík
URL:
Whiteboard:
: 509567 (view as bug list)
Depends On:
Blocks: sat531-blockers
TreeView+ depends on / blocked
 
Reported: 2010-01-19 10:47 UTC by Tomas Lestach
Modified: 2010-03-22 12:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-22 12:05:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2010:0160 0 normal SHIPPED_LIVE Red Hat Network Satellite bug fix update 2010-03-22 12:04:28 UTC

Description Tomas Lestach 2010-01-19 10:47:59 UTC
Description of problem:
For packages, where rpm is found on the disc, "Content Provider" won't be set.

Version-Release number of selected component (if applicable):
Satellite 5.3.1

How reproducible:
always

Steps to Reproduce:
1. take two fresh installed satellites (no sync run before):
SatA: local /var/satellite
SatB: NFS mounted /var/satellite
2. sync any whole channel using satellite-sync -c <channel> on both satellites
3. naviate to WebUI/rhn/channels/ChannelPackages.do?cid=<channel_id> and check the Content Provider column

Actual results:
SatA: Content Provider column is set to "Red Hat Inc." for all package entries
SatB: Content Provider column is set to "Unknown"/unset for all package entries

Expected results:
if running same satellite-sync command, expecting same result

Additional info:
It seems, Content Provider will be set only if appropriate RPM will be downloaded in the same satellite-sync. In case RPM is already found on the file system, Content Provider won't be set.
Another possible reproducer: Running satellite-sync on a fresh installed satellite (local /var/satellite/) and after "Downloading rpm packages" phase is finished, break satellite-sync by pressing <CTRL>-C and re-run same satellite-sync again. "Content Provider won't be set" after it finishes.

Comment 1 Clifford Perry 2010-01-29 14:07:29 UTC
*** Bug 509567 has been marked as a duplicate of this bug. ***

Comment 2 Justin Sherrill 2010-02-01 22:48:52 UTC
fixed in master:


ca6130006bb62917ae56b33ada26b529e2ce3d09

Fix for satellite 5.3 is in a private branch to be added to an errata.  (it's basically the same fix slightly re-factored to use checksum's instead of md5sum)

Comment 3 Tomas Lestach 2010-03-11 16:26:28 UTC
satellite.git: 2b0113bec95bf7730bcda51f2d719151cbff7f23

Comment 6 Milan Zázrivec 2010-03-16 12:56:49 UTC
satellite.git, SATELLITE-5.3: 05e906341be44aa9701a5f79bbaf1c040ed2713d

Comment 7 Milan Zázrivec 2010-03-16 14:30:19 UTC
spacewalk-backend-0.5.28-48

Comment 8 Justin Sherrill 2010-03-16 15:08:39 UTC
Note this will also create a tool called "updateSignatures.py" in /usr/share/rhn/satellite_tools which can be run to update any missing signatures.

Comment 9 Justin Sherrill 2010-03-16 15:09:03 UTC
satellite.git commits:

dfefcbaacaaeaf59287c612cb95f79673f1d4da2
0e831fc4da2f73b4384b835340eba9cec0a3b2d9
fc2f1afaf6d9212aaee7f2038392a6bad994193f

Comment 10 Justin Sherrill 2010-03-16 15:19:47 UTC
satellite.git spec file update:

9a0cbc5f161d624229796917d927117e52937469

Comment 11 Milan Zázrivec 2010-03-16 16:23:01 UTC
spacewalk-backend-0.5.28-49

Comment 12 Šimon Lukašík 2010-03-17 11:13:03 UTC
Taking QA contact for the bug verification.

Comment 15 errata-xmlrpc 2010-03-22 12:05:00 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2010-0160.html


Note You need to log in before you can comment on or make changes to this bug.