Closed kamils85 closed 5 months ago
Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
Thank you for your prompt response. Unfortunately I cannot provide a step by step guide on how to reproduce this as this just happened to me and it seems like it is related to my environment only as nobody else seemed to raised this issue. I was hoping to get some advice what else I can check or debug so I can provide more information. Maybe some clear cache command that would help me.
I believe I still have a backup version prior to the upgrade. I will try to schedule some time next week to restore it and try to upgrade again to see if I can reproduce the issue.
@kamils85 can you move this over to discussions. I will close this issue as we can't reproduce. I think you will get better exposure and answers on the discussion list.
Deployment Type
Self-hosted
NetBox Version
v4.0.3
Python Version
3.10
Steps to Reproduce
Not sure if this is just me or if I missed something while upgrading from 3.x to 4.x but my default widgets on the welcome screen appear empty. It's been like that since the initial update to 4.x and it continues until the recent update. I am updating via the
git pull
method. It looks just like the screen below. I tried with different users, even created a new one and it's the same for everyone. Newly created widget also shows up as empty.Expected Behavior
.
Observed Behavior
There are no errors on the screen nor during the upgrade process. I have attached today's upgrade log in case it helps.