Issue with the report when we download it as SVG

Description

Customer description of the issue “an issue with the report when we download it as SVG. Currently, we are using OpenNMS 2021.

Steps:

Reports -> Database reports -> Default Classic reports.
Change the format to SVG in Report Delivery Options and click Deliver report. we are getting below error.

Error message:
"The OpenNMS Web User Interface Has Experienced an Error. The OpenNMS web UI has encountered an error that it does not know how to handle. Possible causes could be that the database is not responding, the OpenNMS application has stopped or is not running, or there is an issue with the servlet container. Please bring this message to the attention of the person responsible for maintaining OpenNMS for your organization and have him or her check that OpenNMS, the external servlet container (if applicable), and the database are all running without errors. To reveal details of the error encountered and instructions for reporting it, click here."

We faced the same issue in 2020 as well. Here I have attached the reference ticket: SUPPORT-1702.

Note: We created OpenNMS 2021 without any of our product customizations and are still facing this issue. We also noticed the following issues:

Reports -> Database reports -> Availability by BroadWorks node. Change the format to SVG in Report Delivery Options and create a report. It shows 500 error page.

Error details:

An unexpected error occurred: 500
{
"data": {},
"status": 500,
"config": {
"method": "POST",
"transformRequest": [
null
],
}

Question: Has this issue been fixed in M2021? If so, could you please share the PR and Git URL?”

 

The customer ran the following on Aug 28, 2024: Database/default classic report and choose SVG as the report format

We ran the reports multiple times today (28/08/2024) between 08:30 and 09:30 to collect these logs.

For example:

  • local_defaultClassicReport bwadmin 08h58m34s157test

  • local_defaultClassicReport bwadmin 09h26m50s462

 

I see in the customer provided “reports.log”

 

I will attached the logs.

Environment

Powered by Meridian 2021

Acceptance / Success Criteria

None

Attachments

12

Activity

Show:

Eric Maki 10 hours ago

Thank you , I will update the customer

Chandra Gorantla 14 hours ago

Hi If we can’t reproduce this issue in our Meridian release, it is likely that customer may not have merged the changes cleanly or we are not properly replicating the issue. Attaching the screenshot which shows release branch tags for this commit

Eric Maki 15 hours ago

Hi and ,

 

A comment below states:

This PR on meridian-2020 resolved issue for the customer

 

However, the customer states that:

Meridian-2021.1.38-1 release.
We have already merged this fix in our repo but still facing the same issue.

 

Can we please find the version or the commit hash for the fix for the customer?

Best regards,

Eric

Eric Maki February 12, 2025 at 9:27 PM

Hi and ,

 

A comment below states:

This PR on meridian-2020 resolved issue for the customer

 

However, the customer states that:

Meridian-2021.1.38-1 release.
We have already merged this fix in our repo but still facing the same issue.

 

Can we please find the version or the commit hash for the fix for the customer?

Best regards,

Eric

Eric Maki November 26, 2024 at 10:14 PM

Shadid and I think that this issue was already fixed and that the customer needs to rebuild their Powered by instance. Neither one of us could replicate the issue.

Details

Assignee

Reporter

Labels

HB Grooming Date

HB Backlog Status

Sprint

Priority

PagerDuty

Created August 28, 2024 at 7:36 PM
Updated 10 hours ago