Moving to subscription management component as the data in Candlepin is correct based on the hammer command.
I was able to reproduce this via: scenario 1: - imported a manifest (which is current) - add a new allocation to an existing subscription (via the satellite ui) - after the subscription was added, refresh the subscriptions page and click on the > next to the subscription - observe a javascript error in the console - > Uncaught TypeError: Cannot read property 'toggleSubscriptionGroup' of undefined scenario 2: (on a newly created install) - imported the same manifest as the above (which now has additional subs not in the manifest file, but in portal) - refresh the manifest to get those new subscriptions - after refresh completed, refresh the subscriptions page and click on the > next to the subscription - observe a javascript error in the console - > Uncaught TypeError: Cannot read property 'toggleSubscriptionGroup' of undefined Note: I suspect this is the same issue as bug 1738777.
I linked up https://projects.theforeman.org/issues/26908/ for this issue since this was fixed upstream. The issue is seen on any toggled subscription group (you don't have to add/remove subs to see it). The one thing to be aware of is we are seeing the menus collapsing when checked https://projects.theforeman.org/issues/26954 upstream. This is an issue that shows up when this BZ's error is addressed and you can toggle subscriptions again. You could likely see this when this BZ is fixed in 6.6. It is an annoyance but does not block functionality. I didn't see 26954 (the collapsing menu issue) on a 6.5 box so it has regressed since then if it shows up in 6.6. Let me know if you have any questions!
*** Bug 1738777 has been marked as a duplicate of this bug. ***
Verified in Satellite 6.6 Snap 22 After following the verification steps and refreshing the manifest, new subscriptions were shown. See attached video for verification.
*** Bug 1750970 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3172