Bug 1805313

Summary: Layout is distorted when switching from Sync templates to Sync Status
Product: Red Hat Satellite Reporter: Ranjan Kumar <rankumar>
Component: Templates PluginAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Jitendra Yejare <jyejare>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: egolov, mhulan, oprazak
Target Milestone: 6.7.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_templates-7.0.7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:28:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Sync Status page none

Description Ranjan Kumar 2020-02-20 16:32:37 UTC
Created attachment 1664450 [details]
Sync Status page

Description of problem: Layout is distorted when switching from Sync templates to Sync Status 


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


How reproducible: Always

Screen Attached

Comment 3 Ondřej Pražák 2020-02-21 08:20:41 UTC
Created redmine issue https://projects.theforeman.org/issues/29107 from this bug

Comment 4 Bryan Kearney 2020-02-21 09:02:58 UTC
Upstream bug assigned to oprazak

Comment 5 Bryan Kearney 2020-02-21 09:03:01 UTC
Upstream bug assigned to oprazak

Comment 6 Bryan Kearney 2020-03-05 11:03:06 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29107 has been resolved.

Comment 7 Jitendra Yejare 2020-03-09 14:45:15 UTC
Verified!

@ satellite 6.7 snap 15

Steps:
---------
1. Go to Hsts -> Sync Templates.
2. Go to Content -> Sync Status


Observation:
-----------------
The layout is not distorted and loos sane.

Comment 10 errata-xmlrpc 2020-04-14 13:28:54 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-2020:1454