Subscription detail page is empty
I found the subscription detail page empty while debugging a problem with subscriptions (running Katello 3.8.0). On my personal demo system which was still 3.6 it worked, but running all the updates from 3.7 over 3.8 to 3.9 I found the page always empty. The browser console or the logs do not show an error.
To reproduce go to Content > Subscriptions and click on the name of the subscription. (https://KATELLOHOST/subscriptions/1/)
I also tried an API call which gives me the subscription details (https://KATELLOHOST/katello/api/organizations/1/subscriptions/1).
- Refs #25515 - Mount React components in the body
Otherwise the result is:
$(tfm.reactMounter.mount('katello', '#reactRoot', , false));
Script tags are not supposed to show up outside of HTML.
- Fixes #25515 - Fix react router paths
The Route paths are already using exact. Otherwise (at least in nightly)
you need to use /subscriptions/1$/ as a path. The regex is also changed
to require at least one number.
#1 Updated by John Mitsch over 2 years ago
- Status changed from New to Need more information
We can double check if these pages work in the releases you mention, but can you try a few things first?
- Try a hard refresh of the browser page
- Try a different browser i.e. chrome instead of firefox
- Try an 'incognito' window or its equivalent
Let us know if any of these resolve the issue. If not, some information on your browser and version would be helpful. Also, please double check for browser console errors during the refresh.
#4 Updated by Tony Coffman over 2 years ago
Found the same thing in 1.20.1/Katello 3.10
Looking at /subscriptions/<subscription number> results in a blank page. I was able to use /legacy_subscriptions as a workaround.
In 3.10, the /subscriptions page shows a data grid but the boxes are empty which sounds like it might be a different (new) bug?
#5 Updated by Jonathon Turel about 2 years ago
- Triaged changed from Yes to No
- Target version changed from Katello Backlog to Katello 3.11.0
Marking this for triage into an upcoming release. It still does not work in nightly builds but doesn't seem easily reproducible in development environments even when running in production mode with precompiled assets.
#7 Updated by Walden Raines about 2 years ago
Just a quick update with my findings so far.
I can reproduce this in katello 3.11 production and in nightly production. I can not reproduce this in master or when checking out katello 3.11 directly. I also cannot reproduce this in the relevant downstream releases.
The above leads me to believe that this is a packaging issue (perhaps a missing package or an outdated one). Will continue to investigate further.