Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1111254 - puppet-module --id vs --uuid inconsistency
puppet-module --id vs --uuid inconsistency
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Hammer (Show other bugs)
6.0.3
Unspecified Unspecified
unspecified Severity low (vote)
: Unspecified
: Unused
Assigned To: Mike McCune
Tazim Kolhar
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-19 10:57 EDT by Tomas Strachota
Modified: 2017-02-23 16:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-12 01:09:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 6291 None None None 2016-04-22 12:39 EDT
Red Hat Product Errata RHSA-2015:1592 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 05:04:35 EDT

  None (edit)
Description Tomas Strachota 2014-06-19 10:57:59 EDT
There are some identifier inconsistencies in commands around puppet-modules:

<pre>
hammer puppet-module list
# shows only UUIDs
</pre>

<pre>
hammer puppet-module info
# parameter --id actually requires UUID
</pre>

<pre>
hammer content-view puppet-module list
# shows both numeric (activerecord) id and UUID
</pre>

<pre>
hammer content-view puppet-module remove
# --id accepts numeric ids
</pre>

This is very confusing.
Comment 1 Tomas Strachota 2014-06-19 10:58:01 EDT
Created from redmine issue http://projects.theforeman.org/issues/6291
Comment 3 Brad Buckingham 2014-06-24 11:57:15 EDT
For this one, we can probably apply a solution similar to what is done for content-host uuid/id.
Comment 4 Bryan Kearney 2014-08-22 12:02:39 EDT
Moving to POST since upstream bug http://projects.theforeman.org/issues/6291 has been closed
-------------
dustin tsang
Applied in changeset commit:hammer-cli-katello|d93a8fb27c7381a9b20c120188cfe3ec3b0bae1b.
Comment 5 Tazim Kolhar 2014-10-10 08:53:11 EDT
VERIFIED:

*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***

# rpm -qa | grep foreman
foreman-gce-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
ruby193-rubygem-foreman_discovery-1.4.0-0.1.rc4.el7.noarch
hp-bl420cgen8-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch
foreman-compute-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch
foreman-release-1.7.0-0.develop.201410071158git54141ab.el7.noarch
foreman-proxy-1.7.0-0.develop.201410081229git52f0bac.el7.noarch
hp-bl420cgen8-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
foreman-ovirt-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch
foreman-selinux-1.7.0-0.develop.201409301113git2f345de.el7.noarch
foreman-postgresql-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
foreman-vmware-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch
foreman-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
foreman-libvirt-1.7.0-0.develop.201410081938git1cf31c6.el7.noarch
rubygem-hammer_cli_foreman-0.1.3-1.201409191432gitc38f9c8.el7.noarch


# hammer content-view puppet-module remove --help 
 --uuid UUID                             Puppet module's UUID to search by
 


# hammer content-view puppet-module list --help 
 --uuid UUID                             the uuid of the puppet module to associate
 
There identifiers know shows only UUIDs
Comment 7 Bryan Kearney 2015-08-11 09:36:59 EDT
This bug is slated to be released with Satellite 6.1.
Comment 8 errata-xmlrpc 2015-08-12 01:09:36 EDT
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

Note You need to log in before you can comment on or make changes to this bug.