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 1162717 - Document use of "hammer import all"
Summary: Document use of "hammer import all"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Transition Guide
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: David O'Brien
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-11-11 14:33 UTC by David O'Brien
Modified: 2019-09-26 16:28 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: "hammer import all" imports all objects from an export file in one operation. Currently not documented, in favour of importing object groups in required order. Reason: Result: Need concept, prerequisites, justification, process, and troubleshooting for this command. Info page is seriously lacking.
Clone Of:
Environment:
Last Closed: 2016-04-28 00:05:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1306853 0 unspecified CLOSED Inconsistent use of dashes and underscores in command parameters 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1311794 0 unspecified CLOSED Update defaults for 'hammer import all' 2021-02-22 00:41:40 UTC

Internal Links: 1306853 1311794

Description David O'Brien 2014-11-11 14:33:53 UTC 
Description of problem:


Transition Guide covers the use of hammer to import entities individually. Need to cover "import all" which imports all entities.

Expected results:


Additional info:
Comment 1 RHEL Program Management 2014-11-11 14:53:20 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.
Comment 3 RHEL Program Management 2015-04-21 16:08:37 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.
Comment 5 David O'Brien 2015-12-14 03:32:51 UTC 
Grant,

Can we set up a time to review this? If you're not the best contact can you recommend someone?

ta
Comment 6 Grant Gainey 2015-12-14 19:01:12 UTC 
I'm not a *great* contact, because I don't think I have a Sat6 instance to test against - but yeah, I'm probably the "best" contact. Ping me if/when/as you have questions.
Comment 7 David O'Brien 2015-12-15 02:00:18 UTC 
Hi Grant

First stop would be this (see Doc Text field of BZ):

Need concept, prerequisites, justification, process, and troubleshooting for this command. Info page is seriously lacking.

Concept is not hard (import everything. Finished)

The others might need more elaboration, and perhaps comparison with importing by object type ("safety"/reliability vs ease vs speed etc).

sat-perf-* seems to be still broken, but my test machine in the office here is running 6.1.3. Not sure if there are beakers or other VMs we can test this on. I'll investigate and update here.
Comment 10 David O'Brien 2016-01-15 03:48:29 UTC 
Bumped the list to help keep this moving.
Comment 12 David O'Brien 2016-01-19 02:39:31 UTC 
Peter,
Is this another candidate for the Hammer Ref Guide? Can you have a look and let me know?

thanks
Comment 14 David O'Brien 2016-02-02 23:10:05 UTC 
(In reply to Peter Ondrejka from comment #13)
> David,
> 
> I think this fits best in the Transition guide, see
> https://bugzilla.redhat.com/show_bug.cgi?id=1139510#c10

In the scramble last night adahms said he'd have a look at these "need-info" bugs in the etherpad and make a decision.

Andrew?
Comment 15 Andrew Dahms 2016-02-03 03:24:41 UTC 
I agree that this content is a good candidate for the Transition Guide, where users will be most likely to use these commands.
Comment 16 David O'Brien 2016-02-11 05:09:14 UTC 
Grant,

wrt this: --macro_mapping FILE          Mapping of Satellite-5 config-file-macros to puppet facts

Any particular reason this uses and underscore where most (all?) of the others use dashes? Is the info page wrong or is that the actual parameter? The first I can fix; the second I can't (not easily).

See # hammer import all --help

thanks
Comment 17 Andrew Dahms 2016-02-11 05:15:02 UTC 
Setting release flags, and assigning Peter as the QA contact.
Comment 18 Grant Gainey 2016-02-11 13:16:50 UTC 
It is (alas) the actual parameter, and clearly a typo - doesn't even match the parameter it's passing through to, "config-file --macro-mapping.
Comment 19 David O'Brien 2016-02-11 22:37:53 UTC 
(In reply to Grant Gainey from comment #18)
> It is (alas) the actual parameter, and clearly a typo - doesn't even match
> the parameter it's passing through to, "config-file --macro-mapping.

Raised the following for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1306853
Comment 23 David O'Brien 2016-02-16 01:17:24 UTC 
Setting back to assigned to implement tech review updates.
Comment 25 David O'Brien 2016-02-18 02:18:44 UTC 
I'm curious to know about the repeated use of "fresh install" and "new install" of Sat6 when talking about hammer import. Is this a prerequisite? Is importing to a semi-configured Sat6 supported, e.g., if it already has some orgs, users, etc? Are the conditions, best practices, or similar that we should be including?

thanks
Comment 29 Grant Gainey 2016-02-18 13:16:05 UTC 
(In reply to David O'Brien from comment #25)
> I'm curious to know about the repeated use of "fresh install" and "new
> install" of Sat6 when talking about hammer import. Is this a prerequisite?
> Is importing to a semi-configured Sat6 supported, e.g., if it already has
> some orgs, users, etc? Are the conditions, best practices, or similar that
> we should be including?
> 
> thanks

The main purpose for hammer-import, is to get an initial setup of your brand-new Sat6 instance, with as much of your old-Sat5 data as makes sense. The longer your Sat6 instance is up and running, the less likely you are to want to do things "the Sat5 way", or to need any of the Sat5 data. 'all' is even less likely to be useful past initial install. 

However, you can run import whenever you want. The tool tries to handle collisions, and if it can't, it logs an error and keeps soldiering on. But honestly, once you're up and running in Sat6, you're less and less likely to want to move old-data into your new system. The two applications are *different*; the longer you're running Sat6, the less useful "old way" information is.
Comment 39 David O'Brien 2016-02-25 04:11:48 UTC 
Tech review and peer review implemented. Merged and pushed.
Comment 40 Andrew Dahms 2016-04-28 00:05:43 UTC 
This content is now live on the Customer Portal.

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