ManageIQ / manageiq-ui-classic

Classic UI of ManageIQ
Apache License 2.0
50 stars 358 forks source link

"Unexpected error encountered" loading dashboard for some users #8908

Open jbarson47 opened 1 year ago

jbarson47 commented 1 year ago

Hi there - we're seeing an odd issue when attempting to edit a dashboard, and some users report seeing this issue on login as well when loading up the dashboard, resulting in an "Unexpected error encountered" screen displaying the following message: Validation failed: MiqWidgetSet: Set data Unable to find widget ids: 23, 25 [dashboard/show]

from production.log: [----] I, [2023-08-29T06:22:43.125452 #1737390:131f0] INFO -- production: Started GET "/dashboard/show" for 127.0.0.1 at 2023-08-29 06:22:43 +0000 [----] I, [2023-08-29T06:22:43.129525 #1737390:131f0] INFO -- production: Processing by DashboardController#show as HTML [----] F, [2023-08-29T06:22:43.171369 #1737390:131f0] FATAL -- production: Error caught: [ActiveRecord::RecordInvalid] Validation failed: MiqWidgetSet: Set data Unable to find widget ids: 23, 25

However, we confirmed that no miq_widget_set exists in the VMDB with miq_widget 23 or 25 in their miq_widgets, so we're having some trouble identifying what's referring to these widgets. Is there another way to determine what could be referencing the widget in the validation errors?

Fryguy commented 1 year ago

If I recall, the widget references are in a serialized column under the dashboard (not the best but it is what it is). @jeffibm do you recall where those lived exactly.

jeffibm commented 1 year ago

If I recall, the widget references are in a serialized column under the dashboard (not the best but it is what it is). @jeffibm do you recall where those lived exactly.

The widgets are stored in MiqWidgetSet.

MiqWidgetSet.last.set_data
 => {:col1=>[5, 19, 17], :col2=>[16, 6], :reset_upon_login=>false, :locked=>false} 
Fryguy commented 10 months ago

@jeffibm Can you take a look at this one or assign to someone?

jeffibm commented 10 months ago

@jeffibm Can you take a look at this one or assign to someone?

Hey @Fryguy

In which branch should we test this?

I believe this case has been fixed In the master branch though.

Fryguy commented 10 months ago

@jbarson47 Which version?

jbarson47 commented 10 months ago

@Fryguy We are running Najdorf 1.3.

miq-bot commented 7 months ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

jeffibm commented 7 months ago

is there an environment where we can test/reproduce this issue? if possible, a screen video would help narrow this down..

miq-bot commented 4 months ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

miq-bot commented 3 weeks ago

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.