Bug 1174340

Summary: After installation proxy files is not pushed to configuration channel
Product: Red Hat Satellite Proxy 5 Reporter: Pavel Studeník <pstudeni>
Component: InstallerAssignee: Gennadii Altukhov <galtukho>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: galtukho
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-03 10:59:59 UTC Type: Bug
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: 1162131    

Description Pavel Studeník 2014-12-15 16:38:15 UTC
Description of problem:
During installation of proxy I confirmed upload files to configure channel, but channel is empty.

...
Create and populate configuration channel rhn_proxy_config_1000010110? [Y]: Y
RHN username: [admin]: admin
rhncfg-manager update --server-name <server> --channel=rhn_proxy_config_1000010110 /etc/httpd/conf.d/ssl.conf /etc/rhn/rhn.conf /etc/rhn/cluster.ini /etc/squid/squid.conf /etc/httpd/conf.d/cobbler-proxy.conf /etc/httpd/conf/httpd.conf /etc/jabberd/c2s.xml /etc/jabberd/sm.xml
Using server name elisha.usersys.redhat.com
No such file `/etc/rhn/cluster.ini'
..
exit code is 9


Version-Release number of selected component (if applicable):
spacewalk-proxy-installer-2.3.0-4.el6sat.noarch

How reproducible:
always

Steps to Reproduce:
1. configure-proxy.sh --force 
2. create and populate configuration channel rhn_proxy_config_1000010110? [Y]: Y
3. look at channel by webui

Actual results:
configure channel is empty

Expected results:
channel contains files

Comment 2 Gennadii Altukhov 2016-03-02 15:13:04 UTC
Taking...

Comment 3 Gennadii Altukhov 2016-03-03 10:59:59 UTC
spacewalk.git:
0dbd1ee5dd7164ef5b5a00969639d4a6b6e185eb

*** This bug has been marked as a duplicate of bug 647105 ***