Bug 1166045 - if systemIdPath is changed then proxy doesn't work
Summary: if systemIdPath is changed then proxy doesn't work
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite Proxy 5
Classification: Red Hat
Component: Server
Version: 570
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Pavel Studeník
URL:
Whiteboard:
Depends On:
Blocks: sat570-proxy
TreeView+ depends on / blocked
 
Reported: 2014-11-20 10:45 UTC by Pavel Studeník
Modified: 2015-01-13 10:26 UTC (History)
1 user (show)

Fixed In Version: spacewalk-proxy-2.3.0-4-sat spacewalk-proxy-installer-2.3.0-4-sat
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-13 10:26:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Studeník 2014-11-20 10:45:01 UTC
Description of problem:
Proxy doesn't work when systemIdPath is different that the default value /etc/sysconfig/rhn/systemid.

# grep systemIdPath /etc/sysconfig/rhn/up2date 
systemIdPath[comment]=Location of system id
systemIdPath=/etc/sysconfig/rhn/systemid.new

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

How reproducible:
always

Steps to Reproduce:
1. Move the systemid file to different location or rename it
2. Update the systemIdPath in /etc/sysconfig/rhn/up2date file 
3. Register system through proxy

Actual results:
proxy doesn't work

Expected results:
work correct

Additional info:

:: proxy ::
>> tail /var/log/rhn/rhn_proxy_broker.log 
2014/11/20 11:38:08 +02:00 32434 0.0.0.0: proxy/apacheServer.__call__('New request, component proxy.broker',)
2014/11/20 11:38:08 +02:00 32434 10.34.37.88: proxy/rhnProxyAuth.__processSystemid('ERROR', 'unable to access /etc/sysconfig/rhn/systemid')
2014/11/20 11:38:16 +02:00 32440 0.0.0.0: proxy/apacheServer.__call__('New request, component proxy.broker',)
2014/11/20 11:38:16 +02:00 32440 10.34.37.88: proxy/rhnProxyAuth.__processSystemid('ERROR', 'unable to access /etc/sysconfig/rhn/systemid')

:: client ::
[Thu Nov 20 11:43:06 2014] up2date A protocol error occurred: Internal Server Error , attempt #1,
[Thu Nov 20 11:43:06 2014] up2date 
Traceback (most recent call last):
  File "/usr/sbin/rhnreg_ks", line 219, in <module>
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 84, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhnreg_ks", line 89, in main
    rhnreg.getCaps()
  File "/usr/share/rhn/up2date_client/rhnreg.py", line 249, in getCaps
    s.capabilities.validate()
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 161, in __get_capabilities
    self.registration.welcome_message()
  File "/usr/share/rhn/up2date_client/rhnserver.py", line 51, in __call__
    return rpcServer.doCall(method, *args, **kwargs)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 279, in doCall
    raise up2dateErrors.CommunicationError(e.errmsg)
<class 'up2date_client.up2dateErrors.CommunicationError'>: Error communicating with server. The message was:
Internal Server Error

Comment 1 Michael Mráka 2014-11-21 13:10:45 UTC
Fixed in spacewalk master by
commit 5b3ec4d1224bf9ce45db2c28574946620ec6f3d1
    1166045 - read systemid path from configuration

Comment 2 Michael Mráka 2014-11-21 13:19:25 UTC
Backported to SATELLITE-5.7 as
commit 1828b8dcda0674525cefb168961dcd74947a4a48
    1166045 - read systemid path from configuration

Comment 4 Pavel Studeník 2014-12-02 11:03:48 UTC
Verified with spacewalk-proxy-common-2.3.0-4.el6sat.noarch

Comment 5 Clifford Perry 2015-01-13 10:26:41 UTC
With the release of Red Hat Satellite 5.7 on January 12th 2015 this bug is
being moved to a Closed Current Release state. 

The Satellite 5.7 GA Errata:
 - https://rhn.redhat.com/errata/RHSA-2015-0033.html 

Satellite 5.7 Release Notes:
 -
https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/5.7/html-single/Release_Notes/index.html

Satellite Customer Portal Blog announcement for release:
 - https://access.redhat.com/blogs/1169563/posts/1315743 

Cliff

NOTE: This bug has not been re-verified (moved to RELEASE_PENDING) prior to release. We assume that the bug has indeed been fixed and not regressed since we initially verified it. Please re-open in the future if needed.


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