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 1410235 - Typos in satellite-installer --help
Summary: Typos in satellite-installer --help
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Ondřej Pražák
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-04 21:05 UTC by Matt Reid
Modified: 2019-09-26 15:39 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:54:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Help Output (141.59 KB, image/png)
2017-01-04 21:05 UTC, Matt Reid
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 17985 0 None None None 2017-01-09 14:47:23 UTC
Foreman Issue Tracker 17986 0 None None None 2017-01-09 14:51:05 UTC

Description Matt Reid 2017-01-04 21:05:35 UTC
Created attachment 1237335 [details]
Help Output

Description of problem:
From a 6.2.1 system, there are some typos in satellite-installer --help.

= Generic:
    --upgrade                     Run the steps neccessary for an upgrade such as migrations, rake tasks, etc. (default: false)
    --list-scenarios              List available installation scenaraios
    --force                       Force change of installation scenaraio

Necessary, scenario, and scenarios are spelled wrong. Acronym capitalization throughout is inconsistent (https vs HTTPS, SSL vs ssl, etc), but those are the only typos I saw in Writer. Would be nicer if the acronyms were capitalized consistently.

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

Additional info:

Comment 2 Stephen Benjamin 2017-01-09 14:47:21 UTC
Created redmine issue http://projects.theforeman.org/issues/17985 from this bug

Comment 3 Satellite Program 2017-01-09 15:05:12 UTC
Upstream bug assigned to stbenjam

Comment 4 Satellite Program 2017-01-09 15:05:16 UTC
Upstream bug assigned to stbenjam

Comment 5 Satellite Program 2017-01-09 17:05:15 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17986 has been resolved.

Comment 6 Chris Brown 2017-06-20 20:39:43 UTC
Also necessary for --upgrade-puppet under Generic

--upgrade-puppet              Run the steps neccessary to upgrade from Puppet 3 to Puppet 4. (default: false)

Comment 7 Chris Brown 2017-06-20 20:44:40 UTC
Also is this bug including "Would be nicer if the acronyms were capitalized consistently"?

Comment 8 Ondřej Pražák 2017-08-02 08:34:32 UTC
Verified.
Sat-6.3.0 snap 9.0

Removes the typos, does not include consistent acronym capitalization.

Comment 9 Satellite Program 2018-02-21 16:54:17 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-2018:0336


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