Description of problem: Subscription Asset Manager is used as a slave/bridge for subscription status and reporting. However, SAM and SAT5 have different paradigms/strategies for supporting organizations. This becomes an issue in reporting if the vDC subscription is used in a SAT5 multi-org environment. SAM (SAT6) is unable to support the vDC infrastructure subscription unless in a single org environment (see BZ https://bugzilla.redhat.com/show_bug.cgi?id=1142839). Documentation should be updated (along with a K-Base) to qualify this use case as a deviation until BZ 1142839 is fixed. Version-Release number of selected component (if applicable): current How reproducible: vDC is a multi-org environment Steps to Reproduce: vDC is a multi-org environment Actual results: SAM cannot support, and there is no documentation to provide the deviation to the customer. Expected results: SAM supports and this is a no issue for docs, but for now the docs need to document this deviation and work-around (collapse the orgs to a single org). Additionally, if the user cannot collapse their orgs then the behavior of the reporting should be detailed and correct on the deviation behavior. Additional info:
Moving to 'NEW' and the default assignee to be triaged as the schedule allows.
Russell, If I understand the initial problem correctly, the issue is really one of SAM not behaving as expected, requiring a documentation fix. If the existing SAM version has very limited support and the preference is for customers to move to RHSM/SAT, I think that we can drop this as something that probably should be fixed, but if no new SAM bugs will be taken by the engineering team then I think we're just asking for trouble by effectively encouraging customers to use it. So my vote is to close it as "WONTFIX" (not ideal, but I think we can better use resources elsewhere.