Bug 521802

Summary: Fault 1046: 'redstone.xmlrpc.XmlRpcFault: proxy_channel_not_found'
Product: Red Hat Satellite 5 Reporter: Jan Pazdziora (Red Hat) <jpazdziora>
Component: ServerAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED ERRATA QA Contact: Petr Sklenar <psklenar>
Severity: high Docs Contact:
Priority: urgent    
Version: 530CC: akarlsso, cperry, ghacker, msuchy, mzazrivec, psklenar, tpapaioa, xdmoon
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 608677 (view as bug list) Environment:
Last Closed: 2010-10-05 13:16:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 531600, 608677    

Comment 1 Jan Pazdziora (Red Hat) 2009-09-08 12:00:31 UTC
WebUI installation / activation worked OK on the same Satellite + client.

Comment 2 Miroslav Suchý 2009-09-08 13:11:51 UTC
[14:45] <mirek> adelton: it seems that channel dump do not containt that information about product name and version.  I'm going to check code now if it should contain or not.
[15:06] <mirek> adelton: I checked sputnik-prod and its dumps and it seem that neither there nor in 5.3 dumps is product version (which mean you are unable to install proxy even using those dumps), the strange part is that there is some parts code, which probably want to dump that, but it is somewhere in code later discarded.

The satellite was populated using channel dumps available on partners.r.c. I will bet that using propper sync it will work. But channel dump do not have record for table RHNCHANNELPRODUCT, which is required for RHN Proxy activation.
So this is probably bug of rhn-satellite-exporter.

Comment 4 Miroslav Suchý 2009-09-08 16:56:24 UTC
yes, indeed, now the table is corectly populated:
SQL> select * from RHNCHANNELPRODUCT;

        ID
----------
PRODUCT   
--------------------------------------------------------------------------------
VERSION                                                          B CREATED      
---------------------------------------------------------------- - ---------    
MODIFIED                                                                        
---------                                                                       
        21                                                                      
proxy                                                                           
5.3                                                              N 08-SEP-09    
08-SEP-09    


So conclusion is that live (and most probably ISS) sync will populate RHNCHANNELPRODUCT, but channel dumps not. We need to enhance rhn-satellite-exporter to export this table as well...

Comment 6 Milan Zázrivec 2010-06-28 13:12:41 UTC
Spacewalk clone: https://bugzilla.redhat.com/show_bug.cgi?id=608677

Comment 7 Milan Zázrivec 2010-06-28 13:15:58 UTC
satellite.git SATELLITE-5.3: 7074f9cc51b130e9e42a91a2db1b387c6282e6fd

Comment 10 Milan Zázrivec 2010-08-19 08:25:12 UTC
Spacewalk 1.1 has been released.

Comment 13 Miroslav Suchý 2010-10-01 12:13:24 UTC
for my notes:
cherrypicked to master as commit c8ddf6887e1efd21a9dca90df8e381d30a10b77c

Comment 16 Petr Sklenar 2010-10-01 12:51:54 UTC
test procedure:

1. the first  SAT530: sync + export redhat-rhn-proxy-5.3-server-x86_64-5
channel, used spacewalk-backend-0.5.28-59.1

2. the second SAT530: sync from export^ , used spacewalk-backend-0.5.28-59.1

3. rhel55 (with provisioning entitlement) connected to the second SAT530: /usr/sbin/configure-proxy.sh
--
proxy was activated
tried on sat530+spacewalk-backend-0.5.28-59.1 on rhel4@x8664 and rhel5@x8664

Comment 17 errata-xmlrpc 2010-10-05 13:16:56 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-0740.html