Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
In the production logs, there is a issue that we are observing, related a invalid json been submitted to yupana from various accounts.
Version-Release number of selected component (if applicable):
foreman_rh_cloud_version":"3.0.18.1"
How reproducible:
Always
Steps to Reproduce:
Looks like the value for some key field is not propogated to the report and a invalid json is created. this is how the json looks,
{"namespace": "satellite","key": "lifecycle_environment",},
{"namespace": "satellite","key": "content_view",},
{"namespace": "satellite","key": "satellite_instance_id","value": "XXXXXXXXXXXXXXXXXXXXX4"},
{"namespace": "satellite","key": "organization_id","value": "1"}]},
Actual results:
Invalid json is reported and rejected.
Expected results:
Invalid json , should not be created, or (verified/linted) before being uploaded to cloud.
Additional info:
*** Satellite 6.9.2 and 6.9.2.1 Hotfix Available ***
1) Download tfm-rubygem-foreman_rh_cloud-3.0.18.1-2.HOTFIXRHBZ1956190.el7sat.noarch.rpm from this bugzilla to your Satellite
2) stop services:
satellite-maintain service stop
3) Install:
rpm -Uvh tfm-rubygem-foreman_rh_cloud-3.0.18.1-2.HOTFIXRHBZ1956190.el7sat.noarch.rpm
4) restart:
satellite-maintain service start
5) resume operations
Verified
Verified with:
- Satellite 6.10.0 snap 15
- tfm-rubygem-foreman_rh_cloud-4.0.26-1.el7sat.noarch.rpm
Test steps:
- Generated report from customer db 6.10.0 snap 15 satellite.
- Verified generated archive with Subscription Watch QE team.
OR
- Have hosts registered with satellite.
- Generate inventory reports.
Observations:
- Valid json file is created.
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 (Moderate: Satellite 6.10 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-2021:4702
Description of problem: In the production logs, there is a issue that we are observing, related a invalid json been submitted to yupana from various accounts. Version-Release number of selected component (if applicable): foreman_rh_cloud_version":"3.0.18.1" How reproducible: Always Steps to Reproduce: Looks like the value for some key field is not propogated to the report and a invalid json is created. this is how the json looks, {"namespace": "satellite","key": "lifecycle_environment",}, {"namespace": "satellite","key": "content_view",}, {"namespace": "satellite","key": "satellite_instance_id","value": "XXXXXXXXXXXXXXXXXXXXX4"}, {"namespace": "satellite","key": "organization_id","value": "1"}]}, Actual results: Invalid json is reported and rejected. Expected results: Invalid json , should not be created, or (verified/linted) before being uploaded to cloud. Additional info: