Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1102284 - hammer content-view version promote should have friendlier options
Summary: hammer content-view version promote should have friendlier options
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Tomas Strachota
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2014-05-28 16:43 UTC by Justin Sherrill
Modified: 2017-02-23 21:16 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 05:08:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 6509 0 High Closed hammer content-view version promote should have friendlier options 2020-01-13 12:57:23 UTC
Red Hat Product Errata RHSA-2015:1592 0 normal SHIPPED_LIVE Important: Red Hat Satellite 6.1.1 on RHEL 6 2015-08-12 09:04:35 UTC

Description Justin Sherrill 2014-05-28 16:43:25 UTC 
Description of problem:

Right now content-view version promote requires:

    --environment-id ENVIRONMENT_ID  
    --id ID                       Content view version identifier

Ideally we should be able to identify a version by:

Content View Name & Version Number
Content view Name and An environment name (I.e. Promote from Library to Dev)

Ideally the to & from environment should be identifiable by name and label
Comment 2 Justin Sherrill 2014-06-17 18:43:20 UTC 
Moving this to a high priority since SOE doc depends on it.
Comment 3 Tomas Strachota 2014-07-07 13:33:29 UTC 
Created redmine issue http://projects.theforeman.org/issues/6509 from this bug
Comment 4 Bryan Kearney 2014-08-19 08:03:16 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/6509 has been closed
-------------
Anonymous
Applied in changeset commit:hammer-cli-katello|8958e24eb5486c978c6cbdf172c6a04376e2bf43.
Comment 5 Tazim Kolhar 2014-10-10 12:24:24 UTC 
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 version promote --help 
[Foreman] username: admin
[Foreman] password for admin: 
Usage:
    hammer content-view version promote [OPTIONS]

Options:
 --async                                             Do not wait for the task
 --content-view CONTENT_VIEW_NAME                    Content view name
 --content-view-id CONTENT_VIEW_ID                   content view numeric identifier
 --force                                             force content view promotion and bypass lifecycle environment restriction
 --from-lifecycle-environment FROM_ENVIRONMENT       Name of the source environment
 --from-lifecycle-environment-id FROM_ENVIRONMENT_ID Id of the source environment
 --id ID                                             Content view version identifier
 --organization ORGANIZATION_NAME                    Organization name to search by
 --organization-id ORGANIZATION_ID                   organization ID
 --organization-label ORGANIZATION_LABEL             Organization label to search by
 --to-lifecycle-environment TO_ENVIRONMENT           Name of the target environment
 --to-lifecycle-environment-id TO_ENVIRONMENT_ID     Id of the target environment
 --version VERSION                                   Content view version number
 -h, --help                                          print help
Comment 6 Bryan Kearney 2015-08-11 13:32:56 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 7 errata-xmlrpc 2015-08-12 05:08:53 UTC 
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.