the api lets you create this hierarchy rhel-as rhel-as-extras custom-channel for an example of this wonderful feature do this: cd svn/playpen/yum-sync/ perl create-channel.pl --server=rlx-2-24.rhndev.redhat.com --channel-parent=rhel-i386-as-4-extras custom-channel in the webui the channel doesn't show up in 'manage software channels' but does show up in the 'all' list of channels as this: (no access to parent channel) 0 custom-channel
TEST PLAN ------------ run script specified in original comment with the following input and expected results: 1) valid base channel label -> expect: success 2) an invalid channel label -> expect: fault code, 1200 invalid channel name 3) a valid channel label that is NOT a base channel -> expect: fault code: 1202 invalid parent channel
Moving to ON_QA
Fails QA. Test plans 1 and 3 are fine. Number two has a problem. Giving an invalid channel name '0dd' in the web interface fails as expected as it is both under six characters and does not start with a letter. However, the api allows it to be created (and displayed in the web UI): $ perl create-channel.pl --server=rlx-3-14.rhndev.redhat.com --channel-parent=rh-i386-desktop-4 0dd
Repeat test plans from comment #2 and comment #3.
Verified. 1) valid base channel label results in success. 2) an invalid channel label results in Fault returned from XML RPC Server, fault code 1200: Invalid channel name 3) a valid channel label that is NOT a base channel results in Fault returned from XML RPC Server, fault code 1202: Invalid parent channel 4) an invalid parent channel label results in Fault returned from XML RPC Server, fault code -1: unhandled internal exception: Invalid Parent Channel label
moving to closed - currentrelease