Bug 562891

Summary: Configuration file import broken
Product: [Community] Spacewalk Reporter: John Hodrien <johnh>
Component: ClientsAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: low    
Version: 0.7CC: jsherril, rcpowels, roysjosh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-11 16:16:09 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: 585232    

Description John Hodrien 2010-02-08 16:38:44 UTC
Description of problem:

Import of file into configuration channel fails.

Version-Release number of selected component (if applicable):
rhncfg-client-5.9.7.2-1.el5

How reproducible:
Entirely

Steps to Reproduce:
1.  Use webui to set a config file for import.
2.  Run rhn_check on the client.
  
Actual results:

XML-RPC error while talking to https://swserver/CONFIG-MANAGEMENT: cannot marshal None unless allow_none is enabled
Traceback (most recent call last):
  File "/usr/share/rhn/config_client/rpc_cli_repository.py", line 120, in put_files
    self.system_id, action_id, params)
  File "/usr/share/rhn/config_client/rpc_cli_repository.py", line 51, in rpc_call
    (self, method_name) + params)
  File "/usr/share/rhn/config_common/repository.py", line 365, in rpc_call
    sys.exit(2)
SystemExit: 2

File does not get imported.

Expected results:

File gets imported into sandbox, and no error is printed.

Additional info:

Both client and server are CentOS 5.4.

Comment 1 rcpowels 2010-02-24 22:22:54 UTC
I am experiencing an identical issue. Appears to also occur in Spacewalk 0.8. Any new information?

Comment 2 Joshua Roys 2010-05-11 16:16:09 UTC
This was fixed in master at 6777bc7b173974bef052b22d1107eca479fbda1c on March 4.  Re-open if you still have the issue with rhncfg 5.9.19 or later.

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