Bug 1838191 - Arrow position is on left rather in the middle under "Start Time"
Summary: Arrow position is on left rather in the middle under "Start Time"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Sync Plans
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.8.0
Assignee: Samir Jha
QA Contact: Stephen Wadeley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-20 15:51 UTC by Akhil Jha
Modified: 2020-10-27 13:02 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-3.16.0-0.16.rc4.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:02:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Screenshot (42.65 KB, image/png)
2020-05-20 15:51 UTC, Akhil Jha 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30220 0 Normal Closed Arrow position is on left rather in the middle under "Start Time" 2020-10-28 17:41:05 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:02:55 UTC

Description Akhil Jha 2020-05-20 15:51:48 UTC 
Created attachment 1690288 [details]
Screenshot

Description of problem:
Arrow position is on left rather in the middle under "Start Time"

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

How reproducible:
Always

Steps to Reproduce:
1. Login to Satellite UI
2. Content->Sync Plans-> Create Sync Plan
3. Under Start Time, position of the arrows should be in the middle.

Actual results:
Position of arrows are on the left

Expected results:
Position of the arrows should be in the middle.

Additional info:
Comment 3 Samir Jha 2020-06-25 16:13:31 UTC 
Created redmine issue http://projects.theforeman.org/issues/30220 from this bug
Comment 4 Bryan Kearney 2020-07-04 20:06:30 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30220 has been resolved.
Comment 5 Justin Sherrill 2020-07-14 12:59:20 UTC 
moving back to post since we are pulling in more 3.16 rcs
Comment 11 errata-xmlrpc 2020-10-27 13:02:42 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 (Important: Satellite 6.8 release), 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.