Description of problem: Getting "unhandled internal exception: Invalid type [normal] specified." when using client.configchannel.create() API Version-Release number of selected component (if applicable): spacewalk-java-2.0.2-34.el5sat How reproducible: once out of many Steps to Reproduce: I do not have a way how to reproduce, but seen this when calling client.configchannel.create() API call Actual results: xmlrpclib.Fault: <Fault -1: 'redstone.xmlrpc.XmlRpcFault: unhandled internal exception: Invalid type [normal] specified. Make sure you specify one of the following types in your expression [central, central, global, local, local_override, local, local, local_override, sandbox, server_import, server_import]'> Expected results: Should work
Well, one thing is I have no idea, how you managed to reproduce it. Second thing is the error message you're getting. Because if I simulate a non-existing config channel type, I'm getting: xmlrpclib.Fault: <Fault -1: 'redstone.xmlrpc.XmlRpcFault: unhandled internal exception: Invalid type [normalp] specified. Make sure you specify one of the following types in your expression [central, global, local, local_override, normal, sandbox, server_import]'> Note the difference in supported types. - you have duplicates there: central, local (3 times), local_override, server_import - and you miss : normal (what does not correspond with the source code at all) Note: I checked the affected machined and the content of the rhnConfigChannelType looks good: # echo "select id, label from rhnConfigChannelType" | spacewalk-sql -i id | label ----+---------------- 1 | normal 2 | local_override 3 | server_import (3 rows)
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.