[
https://issues.apache.org/jira/browse/HBASE-29556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18059305#comment-18059305
]
Dávid Paksy commented on HBASE-29556:
-------------------------------------
With the changes the error messages (if there are are any) will be displayed
under the respective report section, it looks like this:
!https://private-user-images.githubusercontent.com/1415396/483179558-bc2cc74c-8ee8-4383-8911-9c878a0030d4.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzE0MTY5ODQsIm5iZiI6MTc3MTQxNjY4NCwicGF0aCI6Ii8xNDE1Mzk2LzQ4MzE3OTU1OC1iYzJjYzc0Yy04ZWU4LTQzODMtODkxMS05Yzg3OGEwMDMwZDQucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDIxOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjAyMThUMTIxMTI0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTU0ZjNjNDYxMGY2NTRjODkwYjhhYWUwYzM2ODFhNDY0M2U5NzZiNDVkNmMyMThlZDJlN2JmNTViMWMzNzYzYyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.NiBWf5IOCmkPV4Lfy348MgewxvLKWwm-TQiVyojFodQ|width=1060,height=544!
> Display HBCK and CatalogJanitor report errors properly on HBCK Report page
> --------------------------------------------------------------------------
>
> Key: HBASE-29556
> URL: https://issues.apache.org/jira/browse/HBASE-29556
> Project: HBase
> Issue Type: Improvement
> Components: UI
> Reporter: Dávid Paksy
> Assignee: Dávid Paksy
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.4, 2.5.13
>
> Attachments: image-2025-08-28-15-26-10-482.png
>
>
> h2. As is
> When we fail to generate the HBCK Chore Report or the CatalogJanitor
> Consistency Issues report, the error message is displayed on top of the page
> half-covered by the navbar and thus barely readable.
> !image-2025-08-28-15-26-10-482.png|width=1152,height=757!
> h2. To be
> The error messages should be readable and not covered by other UI elements.
> Display the errors inside the page (inside the container div) instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)