Bug 1956190 - Invalid json created and reported to cloud
Summary: Invalid json created and reported to cloud
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Inventory
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Shimon Shtein
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-03 07:39 UTC by Sanket Jagtap
Modified: 2021-05-12 09:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github theforeman foreman_rh_cloud pull 541 0 None open Filter out tags with empty values 2021-05-03 17:33:46 UTC

Description Sanket Jagtap 2021-05-03 07:39:42 UTC
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:


Note You need to log in before you can comment on or make changes to this bug.