Bug 654998

Summary: Automatic Configuration File Deployment in activation key cannot handle binary files
Product: [Community] Spacewalk Reporter: ben.vanhaeren.external
Component: ClientsAssignee: Jan Pazdziora <jpazdziora>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.8CC: jpazdziora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-28 13:03:15 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: 723481    

Description ben.vanhaeren.external 2010-11-19 10:11:38 UTC
Description of problem:
When you thick the option "Configuration File Deployment" in an activation key and you have subscribed the activation key to configuration channel which contain binary files, rhnreg_ks or rhn_check will fail.

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

How reproducible:


Steps to Reproduce:
1.Thick the option "Configuration File Deployment" in an activation key 
2.Subscribed the activation key to configuration channel which contain binary files
3. Run rhn_check on a system using this activation key
  
Actual results:
Error log /var/log/up2date will contain the following error:

Traceback (most recent call last):
  File "/usr/sbin/rhn_check", line 323, in ?
    cli.run()
  File "/usr/share/rhn/up2date_client/rhncli.py", line 66, in run
    sys.exit(self.main() or 0)
  File "/usr/sbin/rhn_check", line 71, in main
    self.__run_remote_actions()
  File "/usr/sbin/rhn_check", line 128, in __run_remote_actions
    action = self.__get_action(status_report)
  File "/usr/sbin/rhn_check", line 79, in __get_action
    ACTION_VERSION, status_report)
  File "/usr/lib64/python2.4/xmlrpclib.py", line 1096, in __call__
    return self.__send(self.__name, args)
  File "/usr/share/rhn/up2date_client/rpcServer.py", line 39, in _request1
    ret = self._request(methodname, params)
  File "/usr/lib/python2.4/site-packages/rhn/rpclib.py", line 380, in _request
    self._handler, request, verbose=self._verbose)
  File "/usr/lib/python2.4/site-packages/rhn/transports.py", line 188, in request
    return self._process_response(fd, connection)
  File "/usr/lib/python2.4/site-packages/rhn/transports.py", line 216, in _process_response
    return self.parse_response(fd)
  File "/usr/lib/python2.4/site-packages/rhn/transports.py", line 236, in parse_response
    p.feed(response)
  File "/usr/lib64/python2.4/xmlrpclib.py", line 527, in feed
    self._parser.Parse(data, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 2985, column 31

Comment 1 Miroslav Suchý 2011-04-11 07:33:54 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 2 Miroslav Suchý 2011-04-11 07:37:21 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 3 Jan Pazdziora 2011-07-20 11:52:25 UTC
Aligning under space16.

Comment 4 Jan Pazdziora 2011-09-30 14:43:08 UTC
What are the versions of rhn-check and rhnlib on your client machines where this happens?

Comment 5 Jan Pazdziora 2011-11-28 13:03:15 UTC
We seem to have communication lost here. Closing, please reopen if you hit the
problem with the latest Spacewalk release. Thank you, Jan