Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 951204

Summary: spacecmd activationkey_addchildchannel does not recognize child channels of other base channels after cloning
Product: [Community] Spacewalk Reporter: charles.v.carlson
Component: ServerAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED WORKSFORME QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.9CC: msuchy
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-28 15:07:12 UTC Type: Bug
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: 1484117    

Description charles.v.carlson 2013-04-11 16:16:01 UTC 
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.
Comment 1 Miroslav Suchý 2013-04-12 07:18:07 UTC 
Forwarded to upstream.
Comment 2 Milan Zázrivec 2014-02-28 15:07:12 UTC 
# 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}>
Comment 3 Eric Herget 2017-09-28 18:07:23 UTC 
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.