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 1311794 - Update defaults for 'hammer import all'
Summary: Update defaults for 'hammer import all'
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Transitions
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-25 01:43 UTC by David O'Brien
Modified: 2019-09-26 14:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-21 21:14:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1162717 0 medium CLOSED Document use of "hammer import all" 2021-02-22 00:41:40 UTC

Internal Links: 1162717

Description David O'Brien 2016-02-25 01:43:23 UTC
Description of problem:

Notes from BZ where this originated:


--synchronize, --wait, and --no-async don't take arguments (alas), they're either specified, or not-specified. You don't, for example, say "--wait=true" or "--wait=false" - you either say "--wait", or nothing.

There *are* use-cases where you want to maximize hammer-import's ability to parallelize - but they're only useful if you're an expert who knows exactly what you're doing, and whose Sat6 instance isn't going to fall over when it is asked to do manymany things at once.

We should almost certainly say "you should always use this flag". If I could go back and do it over again, I would probably just do the equivalent of --wait --no-async --synchronize, and and not even give the user the option to do otherwise. You could open an RFE and ask for those three options to a) default to true, and b) have a way to turn them *off* for the expert user.

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

* hammer_cli_foreman (0.5.1)
 * hammer_cli_foreman_bootdisk (0.1.3)
 * hammer_cli_foreman_docker (unknown version)
 * hammer_cli_foreman_tasks (unknown version)
 * hammer_cli_gutterball (1.0.1)
 * hammer_cli_import (0.10.22)
 * hammer_cli_katello (0.0.20)

How reproducible:

Always

Actual results:

Default values for various hammer import all arguments are those *not* recommended for non-expert users.

Expected results:

Default values should be "safe" and not lead to possible issues if you are not very familiar with the command and its processes.


Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:03:36 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Bryan Kearney 2017-03-21 21:14:18 UTC
I do not believe this will be addressed int he next few releases, so I am closing this out. If you feel this was incorrect, please feel free to re-open with additional information.


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