Bug 1797327

Summary: Timed out fetching new data message has no top margin on Cluster Settings page
Product: OpenShift Container Platform Reporter: Samuel Padgett <spadgett>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, hasha, jhadvig, jokerman
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:72.0) Gecko/20100101 Firefox/72.0
Last Closed: 2020-05-13 21:58:36 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
Stale data message has no top margin
none
Issue on the edit-secret page none

Description Samuel Padgett 2020-02-02 16:36:59 UTC
Created attachment 1657138 [details]
Stale data message has no top margin

Minor layout issue: The stale data message on the Cluster Settings page should have some top margin. I'm not sure if this is an issue on other pages. (See screenshot.)

To reproduce:

1. Go to the Cluster Settings page
2. Disconnect your computer from the network

Comment 1 Jakub Hadvig 2020-02-04 09:45:30 UTC
Created attachment 1657515 [details]
Issue on the edit-secret page

The issue is common on other pages as well.

Comment 3 shahan 2020-02-05 04:32:57 UTC
Timed out fetching new data message with top margin will show up when disconnected
registry.svc.ci.openshift.org/ocp/4.4-2020-02-05-023531@sha256:d6ad30e15ff827faec3b3c708a6b65cd96a893f731b015115d93c8aeb7156bba

Comment 5 errata-xmlrpc 2020-05-13 21:58:36 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/RHBA-2020:0581