Created redmine issue https://projects.theforeman.org/issues/25115 from this bug
Should we prioritize this for a future release rather than 6.6?
*If* we're planning on changing this behavior and implementing this RFE then we need to take some time and design a mockup. Either way we need to gather more information on whether this is even necessary.
I could also see the argument for closing this and opening a new RFE.
(In reply to Walden Raines from comment #22)
> Should we prioritize this for a future release rather than 6.6?
> *If* we're planning on changing this behavior and implementing this RFE then
> we need to take some time and design a mockup. Either way we need to gather
> more information on whether this is even necessary.
> I could also see the argument for closing this and opening a new RFE.
Ashfaqur, any thoughts on this?
Connecting redmine issue https://projects.theforeman.org/issues/27605 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27605 has been resolved.
Verified in 6.7 snap 2.
When the same subscription is added twice to a satellite. The two subscriptions can be shown nested under a subscription placeholder using the '>' symbol. The subscription placeholder shows the Contract, Start Date, End Date, Consumed, and Entitlements as NA.
Created attachment 1638593 [details]
Sensitive material has been edited to 'Hidden'
*** Bug 1794447 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.