Description of problem: While troubleshooting a user not seeing data in Subscription Watch, we noticed that the metadata.json does not appear to meet Yupana's specification. Version-Release number of selected component (if applicable): tfm-rubygem-foreman_inventory_upload-1.0.2-0.1.el7sat.noarch.rpm How reproducible: 100% Steps to Reproduce: 1. Download report using the Satellite plugin 2. inspect metadata.json and compare to the Yupana API spec 3. Actual results: Expected results: Additional info:
*** Bug 1817553 has been marked as a duplicate of this bug. ***
*** Bug 1823396 has been marked as a duplicate of this bug. ***
Also, this writeup confuses different layers. Ingress does not reject anything or validate anything. Possible issues include: 1. Yupana rejects tar.gz format because you did not conform to syntax (see https://github.com/quipucords/yupana#-formatting-data-for-yupana-without-qpc). However, this has nothing to do with subscription_status 2. HBI may reject a host (not the tar.gz) based on invalid syntax. Yupana does NOT validate hosts. HBI validates hosts. So likely HBI didn't like subscription_status I do not think these issues are the same. - This bug relates to yupana validation - Bug https://bugzilla.redhat.com/show_bug.cgi?id=1823396 relates to HBI validate I do not think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1823396 based on the fact the validation failures are in different services.
*** Bug 1862250 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 (Important: Satellite 6.8 release), 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-2020:4366