Bug 2065068
| Summary: | Too large subtable console errors in engine admin portal | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Sandro Bonazzola <sbonazzo> |
| Component: | Frontend.WebAdmin | Assignee: | rszwajko |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ivana Saranova <isaranov> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.5.0 | CC: | bugs, dfodor, gdeolive, rszwajko, sgratch |
| Target Milestone: | ovirt-4.5.1 | Flags: | sbonazzo:
ovirt-4.5?
gdeolive: testing_ack+ |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-27 07:10:40 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Sandro Bonazzola
2022-03-17 09:38:55 UTC
This is reproduced for both Admin portal and VM portal. 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 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. > 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. |