Bug 1131206
Summary: | hammer composite content view create ignores component-ids | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> |
Component: | Hammer | Assignee: | David Davis <daviddavis> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.3 | CC: | bbuckingham, daviddavis, jcallaha |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-12 05:14:28 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: | 1131249 | ||
Bug Blocks: |
Description
sthirugn@redhat.com
2014-08-18 16:54:41 UTC
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 |