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 1108779 - hammer content-host create does not work with lifecycle-env name
Summary: hammer content-host create does not work with lifecycle-env name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Dustin Tsang
QA Contact: Tazim Kolhar
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-12 14:34 UTC by Kedar Bidarkar
Modified: 2019-09-26 18:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-02 14:07:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
the bedug info for the above command (6.21 KB, text/plain)
2014-06-12 14:36 UTC, Kedar Bidarkar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 5697 0 None None None 2016-04-22 16:20:18 UTC

Description Kedar Bidarkar 2014-06-12 14:34:31 UTC
Description of problem:
similar to bug https://bugzilla.redhat.com/show_bug.cgi?id=1107319

the above bug was fixed but the bug update on comment#3 still exists.

Version-Release number of selected component (if applicable):
any

How reproducible:
always

Steps to Reproduce:
1.  hammer -v -d content-host create --name="test_host" --environment='Library' --content-view-id=2 --organization-id 1 
2.
3.

Actual results:
unable to create a content-host and we get a message 

# hammer content-host create --name="test_host" --environment='Library' --content-view-id=2 --organization-id 1 
Could not create content host:
  Error: environment found more than once


Expected results:

content-host needs to get create successfull with the lifecycle-env as name.

Additional info:

Comment 1 Kedar Bidarkar 2014-06-12 14:36:23 UTC
Created attachment 908176 [details]
the bedug info for the above command

Comment 3 Dustin Tsang 2014-06-17 16:08:34 UTC
dupe of redmine issue http://projects.theforeman.org/issues/5697

Comment 4 Dustin Tsang 2014-06-17 17:51:44 UTC
The pull requests that fix this issue are:
https://github.com/Katello/katello/pull/4244
https://github.com/Katello/hammer-cli-katello/pull/189

Comment 7 Tazim Kolhar 2014-06-19 07:19:48 UTC
# hammer content-host create --name test_host --environment Library --content-view-id 50 --organization-id 1
Name:                  test_host
ID:                    07a1dad1-0a19-454a-b335-2df6620c3f0b
Description:           Initial Registration Params
Location:              None
Lifecycle Environment: Library
Content View:          cv1
Entitlement Status:    valid
Release Version:       
Autoheal:              true

Content host created

Comment 8 Bryan Kearney 2014-07-02 14:07:21 UTC
This was delivered with 6.0.3, which is the Satellite 6 Beta.


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