Bug 2065068 - Too large subtable console errors in engine admin portal
Summary: Too large subtable console errors in engine admin portal
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ovirt-4.5.1
: ---
Assignee: rszwajko
QA Contact: Ivana Saranova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-17 09:38 UTC by Sandro Bonazzola
Modified: 2022-06-27 07:10 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-27 07:10:40 UTC
oVirt Team: UX
Embargoed:
sbonazzo: ovirt-4.5?
gdeolive: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 337 0 None open webadmin: update OpenSans fonts bundled with PF3 2022-05-05 14:07:04 UTC
Red Hat Issue Tracker RHV-45347 0 None None None 2022-03-17 09:45:34 UTC

Description Sandro Bonazzola 2022-03-17 09:38:55 UTC
Description of problem:

On a fresh installed system, logging in to admin interface, the browser console shows errors:

downloadable font: kern: Too large subtable (font-family: "Open Sans" style:normal weight:400 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Regular-webfont.woff2
downloadable font: Table discarded (font-family: "Open Sans" style:normal weight:400 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Regular-webfont.woff2
downloadable font: kern: Too large subtable (font-family: "Open Sans" style:normal weight:600 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Semibold-webfont.woff2
downloadable font: Table discarded (font-family: "Open Sans" style:normal weight:600 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Semibold-webfont.woff2
downloadable font: kern: Too large subtable (font-family: "Open Sans" style:normal weight:700 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Bold-webfont.woff2
downloadable font: Table discarded (font-family: "Open Sans" style:normal weight:700 stretch:100 src index:3) source: https://engine.lab/ovirt-engine/webadmin/theme/00-ovirt.brand/bundled/patternfly/fonts/OpenSans-Bold-webfont.woff2


Version-Release number of selected component (if applicable):
ovirt-engine-4.5.0

Comment 1 Sharon Gratch 2022-03-21 13:31:30 UTC
This is reproduced for both Admin portal and VM portal.

Comment 2 rszwajko 2022-04-05 12:54:06 UTC
Logs above are triggered because OpenSans fonts bundled with PatternFly 3 have too large kerning table. 
As per [1] this is non-critical problem with the given font version.

In VM Portal this should be solved once migration to PatternFly 4 is complete. 
In Web Admin it's possible to replace the orignal fonts with the newest available version (requires manual compression and repackaging)

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1185685

Comment 3 Sharon Gratch 2022-04-19 12:24:51 UTC
This is an old issue exists since oVirt 4.3 or even earlier.
Since we are not going to upgrade webadmin to use PF4 (except ui-extensions dialogs), then I assume that replacing the original font might be nice to have to get rid of those error messages.

The question is if by doing that we might encounter other issues of inconsistency/font sizes issues/patternfly 3 css conflicts etc. If it's a smoothly action then why not doing that? We do update other bundled packages so we can also handle this.

Comment 4 rszwajko 2022-04-19 16:51:23 UTC
> The question is if by doing that we might encounter other issues of inconsistency/font sizes issues/patternfly 3 css conflicts etc.
>

Replacing original fonts with newer version should not impact the layout. 


> If it's a smoothly action then why not doing that? 
>

First, this is a minor inconvenience. The errors should be actually logged as warnings as they are not critical. 
Second, it's clearly a fix that should be released by PF3.
Beside that, I see no technical problems with fixing that.

Comment 9 Ivana Saranova 2022-06-24 12:03:30 UTC
Steps:
1) check errors in the console going through webadmin and vm portal

Results:
No errors, except for the PF3 components as mentioned in Comment 2.

Verified in:
ovirt-engine-4.5.1.2-0.11.el8ev.noarch


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