Red Hat Bugzilla – Bug 1131206
hammer composite content view create ignores component-ids
Last modified: 2017-02-23 16:05:03 EST
Description of problem: hammer composite content view create ignores component-ids Version-Release number of selected component (if applicable): GA Snap 5 - Satellite-6.0.4-RHEL-6-20140813.2 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23-1.el6_5.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23-1.el6_5.noarch * candlepin-tomcat6-0.9.23-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.6.0.40-1.el6sat.noarch * foreman-compute-1.6.0.40-1.el6sat.noarch * foreman-gce-1.6.0.40-1.el6sat.noarch * foreman-libvirt-1.6.0.40-1.el6sat.noarch * foreman-ovirt-1.6.0.40-1.el6sat.noarch * foreman-postgresql-1.6.0.40-1.el6sat.noarch * foreman-proxy-1.6.0.27-1.el6sat.noarch * foreman-selinux-1.6.0.6-1.el6sat.noarch * foreman-vmware-1.6.0.40-1.el6sat.noarch * katello-1.5.0-28.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-installer-0.0.59-1.el6sat.noarch * openldap-2.4.23-34.el6_5.1.x86_64 * openldap-devel-2.4.23-34.el6_5.1.x86_64 * pulp-katello-0.3-3.el6sat.noarch * pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch * pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch * pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-selinux-2.4.0-0.30.beta.el6sat.noarch * pulp-server-2.4.0-0.30.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch How reproducible: Always Steps to Reproduce: 1. Create a content view and publish it hammer> content-view info --name=cv1 --organization-id=3 ID: 3 Name: cv1 Label: cv1 ... Organization: rhcorp Repositories: ... Puppet Modules: ... Environments: ... Versions: 1) ID: 3 Version: 1 Published: 2014/08/10 04:21:48 2) ID: 6 Version: 2 Published: 2014/08/11 14:59:21 2. Create a composite content view with the version id from above content view hammer> content-view create --name='testcomposite' --component-ids='3' --organization-id=3 --composite Content view created Actual results: Notice that the composite content view is created but componen-ids are not associated Expected results: composite content view should be created and component-ids should be associated with it. Additional info: Update doesnt work either: hammer> content-view update --name='testcomposite' --component-ids='3' --organization-id=3 Content view updated *But the component-id is not actually associated* But add-version works: hammer> content-view add-version --name='testcomposite' --content-view-version-id='3' --organization-id=3 The component version has been added *This worked fine*
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.
Also, it looks like this issue might also exist for "host-collection create" and "host-collection update" commands (which have --content-host-ids options).
This failed too as per Comment 3: hammer> host-collection create --name='testbughc' --organization-id=3 --content-host-ids='dbd5c88a-7ce6-45f5-bcdf-579564738ec4,87c7c1cd-b01f-479f-a3e2-558455272b7c' Host collection created hammer> host-collection update --name='testbughc' --organization-id=3 --content-host-ids='dbd5c88a-7ce6-45f5-bcdf-579564738ec4,87c7c1cd-b01f-479f-a3e2-558455272b7c' Host collection updated Both the commands above failed to associate the content-hosts to host-collections
Filed https://bugzilla.redhat.com/show_bug.cgi?id=1131238 for the issue mentioned in Comment 2. Note: Please do not close one of these bugs saying it is a dupe of another. QE need to validate both the scenarios.
Since the user has an alternative CLI to add/remove content view versions to/from a composite content view, going to move this one to 6.1. e.g. - content-view add-version - content-view remove-version
This was fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1131249. Not closing as a dupe per comment #5.
Note: There was no code needed for this bug.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: RHEL66 / RHEL7 qe-foreman-rhel7.usersys.redhat.com-puppet-client-1.0-1.noarch foreman-vmware-1.8.0-0.develop.201411201326giteaefbec.el7.noarch qe-foreman-rhel7.usersys.redhat.com-qpid-broker-1.0-1.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch foreman-postgresql-1.8.0-0.develop.201411201326giteaefbec.el7.noarch qe-foreman-rhel7.usersys.redhat.com-qpid-client-cert-1.0-1.noarch foreman-release-1.8.0-0.develop.201411201326giteaefbec.el7.noarch foreman-libvirt-1.8.0-0.develop.201411201326giteaefbec.el7.noarch foreman-compute-1.8.0-0.develop.201411201326giteaefbec.el7.noarch foreman-ovirt-1.8.0-0.develop.201411201326giteaefbec.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch qe-foreman-rhel7.usersys.redhat.com-foreman-client-1.0-1.noarch qe-foreman-rhel7.usersys.redhat.com-apache-1.0-1.noarch qe-foreman-rhel7.usersys.redhat.com-parent-cert-1.0-1.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch foreman-proxy-1.8.0-0.develop.201411201507gitfc67f91.el7.noarch foreman-1.8.0-0.develop.201411201326giteaefbec.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch qe-foreman-rhel7.usersys.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-gce-1.8.0-0.develop.201411201326giteaefbec.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.2-1.el7.noarch
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592