Description of problem: It is not possible to clone channels from different organizations within WebUI, though it does clone from spacecmd. As an admin with generating trusts between organizations I want to be able (as with spacecmd since 2.3 as well) to clone channels I have access to. Version-Release number of selected component (if applicable): 2.3 How reproducible / Steps to Reproduce: 1. Have 2 org A and B 2. make them trust each other. 3. Create a channel in org A. 4. Try to clone a channel from org B. Result WebUI: List is empty = Cannot clone as not possible to select. Result spacecmd: softwarechannel_clone or softwarechannel_clonetree: works. Actual results: No list of channels visible to clone. Expected results: Show a list of channels from trusted orgs to clone, and make them clone when chosen. Additional info: -none-
https://github.com/spacewalkproject/spacewalk/blob/master/java/code/src/com/redhat/rhn/frontend/action/channel/manage/CloneChannelAction.java#L78-80 actually shows the problem in code (comment) ...
Committing to Spacewalk master: f1e0f9d0bb3748f2cb9869054d17cadc0a7ef47c
So the patch turned out to be larger than I was expecting. Given that and the fact that this is not a critical bug (it's not even a regression; this is how SW 2.2 and previous worked too) I'm not going to rebuild / rerelease SW 2.3 packages. I'd feel much more comfortable if the developers who are running Nightly use this code for a while and let it just get released in 2.4. BUT, I know you really want this now, so I'll build for you test packages that are 2.3 + this commit. They won't be signed, and they won't appear in the repos, but if you want to download them and 'rpm -Uvh spacewalk*.rpm' and rhn-satellite restart then you should be good to go.
You only need to get the packages that are upgrades to ones you currently have installed. So for example, you in particular don't need spacewalk-java-postgresql, spacewalk-java-tests, or the .src.rpm. These rpms will only stay in the system for two weeks since it's a test build, so you should save them off somewhere else if you want have them later. Fedora 20: http://koji.spacewalkproject.org/koji/taskinfo?taskID=185523 Fedora 21: http://koji.spacewalkproject.org/koji/taskinfo?taskID=185525 RHEL 6: http://koji.spacewalkproject.org/koji/taskinfo?taskID=185519 RHEL 7: http://koji.spacewalkproject.org/koji/taskinfo?taskID=185521
(In reply to Michael Kromer from comment #0) > Description of problem: > > It is not possible to clone channels from different organizations within > WebUI, though it does clone from spacecmd. As an admin with generating > trusts between organizations I want to be able (as with spacecmd since 2.3 > as well) to clone channels I have access to. > > Version-Release number of selected component (if applicable): > > 2.3 > > How reproducible / Steps to Reproduce: > > 1. Have 2 org A and B > 2. make them trust each other. > 3. Create a channel in org A. > 4. Try to clone a channel from org B. > > Result WebUI: List is empty = Cannot clone as not possible to select. > Result spacecmd: softwarechannel_clone or softwarechannel_clonetree: works. > Making a public statement here for any Satellite 5 customers. Please note that this bug report would be for Satellite 5 to fix the APIs so that API cloning of shared channels does not work. We have specifically fixed and addressed within the product a previous Internal Server Error (ISE) when attempting to clone shared channels within the WebUI. For that bug we chose to fix the ISE and prevent cloning in UI from happening - since we felt that Satellite customers who share content want to continue to remain owners of that content. In short, happy to make this change in Spacewalk, for future Spacewalk releases, that Stephen has done, but we will not approve any requests to port this enhancement back into the Satellite 5 product. Regards, Cliff. See Bug 584790 - [RFE] Shared Channels can not be cloned using WebUI - CLOSED WONTFIX
Spacewalk 2.4 has been released.