Bug 783474

Description of problem:

Owner info compliance data is using the consumer facts to sort compliance status. Fact is sent by the client, so if a SAM/Katello UI user assigns subscriptions, their org can still show out of compliance even when they just fixed it, until the relevant systems check in.

Steps to Reproduce:
1. Register a non-compliant consumer to Candlepin.

2. Manually trigger an auto-bind by hitting REST API directly: curl -X POST -i -k -u admin:admin https://localhost:8443/candlepin/consumers/fba46ffd-7768-4b12-bba1-d222cafd9ead/entitlements

3. See that server can see the system as compliant: curl -i -k -u admin:admin https://localhost:8443/candlepin/consumers/fba46ffd-7768-4b12-bba1-d222cafd9ead/compliance

  "status" : "valid",

4. View owner info: curl -i -k -u admin:admin https://localhost:8443/candlepin/owners/admin/info

  
Actual results:

  "consumerCountsByComplianceStatus" : {
    "invalid" : 1
  },


Expected results: 

In this case above, one system in one org, there should be no invalid systems.

This is because owner info is driven by the client submitted fact, but when the client has not yet checked in, it remains invalid even though the admin just made it compliant, and will now be very confused when looking at Katello/SAM compliance graphs.


Additional info: