Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1187374 - Inconsistency in wording on HTTP vs HTTPS enable flags in Repo screens
Inconsistency in wording on HTTP vs HTTPS enable flags in Repo screens
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: WebUI (Show other bugs)
6.0.7
Unspecified Unspecified
unspecified Severity low (vote)
: Beta
: Unused
Assigned To: Brad Buckingham
Jitendra Yejare
http://projects.theforeman.org/issues...
Verified in Upstream
: Triaged
: 1191628 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-01-29 17:15 EST by Mike McCune
Modified: 2016-07-27 04:47 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-27 04:47:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
screenshot (113.61 KB, image/png)
2015-01-29 17:15 EST, Mike McCune
no flags Details
Failed QA - Screenshot (183.21 KB, image/png)
2015-09-03 08:57 EDT, Jitendra Yejare
no flags Details
Verified Screenshot (182.98 KB, image/png)
2015-09-07 05:14 EDT, Jitendra Yejare
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 11627 None None None 2016-04-22 12:59 EDT
Red Hat Product Errata RHBA-2016:1500 normal SHIPPED_LIVE Red Hat Satellite 6.2 Base Libraries 2016-07-27 08:24:38 EDT

  None (edit)
Description Mike McCune 2015-01-29 17:15:33 EST
Created attachment 985792 [details]
screenshot

In the Satellite 6 GUI Repository details screen, there are two headings:

* Publish via HTTPS: True
* Publish via HTTP: Yes

These need to both say either Yes/No or True/False

See screenshot attached.
Comment 1 Steve Loranz 2015-01-30 10:46:25 EST
Do you have a preference for either one? (Yes/No vs True/False)

Seems like something Red Hat should have in some sort of human interface guidelines.
Comment 3 Brad Buckingham 2015-08-31 16:44:06 EDT
Created redmine issue http://projects.theforeman.org/issues/11627 from this bug
Comment 4 Bryan Kearney 2015-09-01 16:02:54 EDT
Moving to POST since upstream bug http://projects.theforeman.org/issues/11627 has been closed
-------------
Brad Buckingham
Applied in changeset commit:katello|f74d548fe1603910720216d2abe498b9057ea4ed.
Comment 5 Jitendra Yejare 2015-09-03 08:34:21 EDT
Tested this on Upstream build. The issue is still reproducible.

Screenshot attached.
Comment 6 Jitendra Yejare 2015-09-03 08:42:59 EDT
Versions:
ruby193-rubygem-katello-2.4.0-1.nightly.201508250010gitbbcea20.el7.noarch
Comment 7 Jitendra Yejare 2015-09-03 08:49:15 EDT
Versions:
ruby193-rubygem-katello-2.4.0-1.nightly.201508250010gitbbcea20.el7.noarch
foreman-1.10.0-0.develop.201508241946git8658fa3.el7.noarch
Comment 8 Jitendra Yejare 2015-09-03 08:57:58 EDT
Created attachment 1069802 [details]
Failed QA - Screenshot
Comment 9 Brad Buckingham 2015-09-03 09:10:25 EDT
The current upstream build doesn't include the fix.  It appears that the upstream nightly hasn't been built for a while.  This is the build upstream: http://koji.katello.org/koji/buildinfo?buildID=24171
Comment 10 Brad Buckingham 2015-09-04 12:12:26 EDT
*** Bug 1191628 has been marked as a duplicate of this bug. ***
Comment 11 Jitendra Yejare 2015-09-07 05:12:55 EDT
Verified in latest upstream build.

Both,
Publish via HTTPS and 
Publish via HTTP,
has displayed 'Yes'/'No'.

Screenshot attached.
Comment 12 Jitendra Yejare 2015-09-07 05:14:11 EDT
Created attachment 1070870 [details]
Verified Screenshot
Comment 17 errata-xmlrpc 2016-07-27 04:47:24 EDT
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/RHBA-2016:1500

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