Bug 1385445 - [typo] Satellite web UI -> Infrastructure -> Domains
Summary: [typo] Satellite web UI -> Infrastructure -> Domains
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
low
low vote
Target Milestone: Unspecified
Assignee: Swapnil Abnave
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 04:11 UTC by Julie
Modified: 2019-09-26 14:02 UTC (History)
4 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:


Attachments (Terms of Use)
typo (48.10 KB, image/png)
2016-10-17 04:11 UTC, Julie
no flags Details
verified (135.76 KB, image/png)
2017-06-20 21:01 UTC, Chris Brown
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16962 0 None None None 2016-10-17 07:04:49 UTC

Description Julie 2016-10-17 04:11:38 UTC
Created attachment 1211224 [details]
typo

Go to Satellite web UI -> Infrastructure -> Domains:

----
Satellite considers a domain and a DNS zone as the same thing.
That is, if you are planning to manage a site where all the machines are or the form hostname.somewhere.com then the domain is somewhere.com.
----

s/are or the form/are of the form


Kind regards,
Julie

Comment 2 Bryan Kearney 2016-10-17 10:09:25 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16962 has been resolved.

Comment 3 Daniel Lobato Garcia 2017-01-27 08:50:49 UTC
Setting as triaged as there's a fix already upstream

Comment 4 Chris Brown 2017-06-20 20:58:54 UTC
Verified in Satellite 6.3 Snap 3.

Comment 5 Chris Brown 2017-06-20 21:01:05 UTC
Created attachment 1289847 [details]
verified

Screenshot verifying the typo was fixed

Comment 7 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.