Description of problem: Currently only UI supports cloning of config_templates. But we are not sure how do we check this or test cloning via the api's. Version-Release number of selected component (if applicable): 6.0.5 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Not clear as to how test cloning via the api's. Expected results: Need a way to test cloning via the api's. Additional info: As cloning already works with UI, I am assuming there could be some way to do this, but it's not clear who do we do it via api's.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/9030 from this bug
Upstream bug assigned to szadok
Moving to POST since upstream bug http://projects.theforeman.org/issues/9030 has been closed ------------- Shlomi Zadok Applied in changeset commit:fa941058eb5b6e3d21096548528a010fe34ca504.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch foreman-debug-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-ovirt-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch foreman-postgresql-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-vmware-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch foreman-gce-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-release-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch foreman-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch foreman-libvirt-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch dell-per300-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201512101420git81ec371.el7.noarch foreman-compute-1.11.0-0.develop.201512111432git98f6ca5.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch foreman-proxy-1.11.0-0.develop.201512101505git62c9e22.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1500