Description of problem: I have base channel A with child channel A1 and base channel B with child channel B1. I use spacewalk clone by date to create clone base channel C of A and child channel C1 from A1 and then use spacecmd to clone child channel C2 from child channel B1. So: BASE CHANNEL: A child A1 BASE CHANNEL: B child B1 Use spacewalk_clonebydate to create C from A and C1 from A1. Then spacecmd clone child channel C2 from B1(under C of course). Now if I use spacecmd activationkey_addchildchannel mykey C1 works, But if I do addchildchannel mykey C2, it does not recognize child channel C2. I can add child channel C2 to the activation key from the web interface. Version-Release number of selected component (if applicable): spacecmd-1.10.1-1.el6.noarch How reproducible: Steps to Reproduce: 1. spacewalk_clonebydate to clone a base channel and it's children 2. spacecmd softwarechannel_clone to clone child channels from a different base channel to the base channel cloned in step 1 3. spacecmd activationkey_addchildchannel to add the child channel clones in step 2 to the activation key. Actual results: ERROR: redstone.xmlrpc.XmlRpcFault: Invalid channel Expected results: Child channel should get added to activation key Additional info: spacecmd activationkey_addchildchannel properly adds cloned child channels that are child channels from step 1, but not step 2 above.
Forwarded to upstream.
# rpm -q spacecmd spacecmd-2.1.25-1.el6.noarch # spacecmd spacecmd {SSM:0}> softwarechannel_clone -s channel_b1 -n channel_c2 -l channel_c2 -p channel_c spacecmd {SSM:0}> activationkey_addchildchannels 1-key01 channel_c1 spacecmd {SSM:0}> activationkey_addchildchannels 1-key01 channel_c2 spacecmd {SSM:0}> activationkey_listchildchannels 1-key01 channel_c1 channel_c2 spacecmd {SSM:0}>
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.