Bug 2213813

Summary: Inventory Host was not uploaded to your RH cloud inventory
Product: Red Hat Satellite Reporter: Taft Sanders <tasander>
Component: RH Cloud - InventoryAssignee: Shimon Shtein <sshtein>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.13.1CC: aruzicka
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-12 08:08:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Taft Sanders 2023-06-09 13:21:14 UTC
Description of problem:
All hosts are showing this message on a fresh install of Satellite 6.13 due to the Settings instance_id value not being enforced from the settings page. Inventory reports are being sent to console.redhat.com with random satellite_instance_id values with every upload

Version-Release number of selected component (if applicable):
satellite-6.13.1-1.el8sat.noarch
rubygem-foreman_rh_cloud-7.0.45-1.el8sat.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Create a new Satellite 6.13
2. Register a host
3. Generate an inventory report 2 or more times

Actual results:
The satellite_instance_id is supposed to match the Settings instance_id value

Expected results:
The provided settings instance_id value is used for each host in the report

Additional info:
Workaround is the reset the instance_id value using the command:
    # foreman-rake console

    >> Setting[:instance_id] = Foreman.uuid

    >> exit

Comment 1 Taft Sanders 2023-06-09 13:37:07 UTC
Here is an example from testing:

[root@taftsat 6-8-2023T171505]# hammer settings info --id instance_id
Id:            instance_id
Name:          instance_id
Description:   Foreman instance ID, uniquely identifies this Foreman instance.
Category:      General
Settings type: string
Value:         19b1acf2-cd60-47cc-bb30-a170a82a02ab

When asking for the value in foreman-rake, it keeps changing:
[root@taftsat foreman]# echo Setting[:instance_id] | foreman-rake console
Loading production environment (Rails 6.1.7)
Switch to inspect mode.
Setting[:instance_id]
"80af5d19-0a04-4fa6-a0c9-af2f7daae71f"
[root@taftsat foreman]# echo Setting[:instance_id] | foreman-rake console
Loading production environment (Rails 6.1.7)
Switch to inspect mode.
Setting[:instance_id]
"a94bbcc4-25b6-482d-bed6-e641b0c27310"

Upload 1:
[root@taftsat 6-8-2023T171153]# cat 4c26be68-5250-4f2b-83ab-7ae33993335e.json | json_reformat | grep satellite_instance_id
                        "satellite_instance_id": "36455441-ae8f-4ebf-a910-594349b2e0db",
                    "key": "satellite_instance_id",
                        "satellite_instance_id": "36455441-ae8f-4ebf-a910-594349b2e0db",
                    "key": "satellite_instance_id",

Upload 2: (2 mins later)
[root@taftsat 6-8-2023T171505]# cat ee499a98-aa96-431b-aad7-27552f0f396f.json | json_reformat | grep satellite_instance_id
                        "satellite_instance_id": "71cff013-fbd8-4fbd-8bce-6ecf1dac2613",
                    "key": "satellite_instance_id",
                        "satellite_instance_id": "71cff013-fbd8-4fbd-8bce-6ecf1dac2613",
                    "key": "satellite_instance_id",


After running the rake command to set the setting to a new UUID the uploads then continuously use the new value:
[root@taftsat 6-8-2023T171505]# echo Setting[:instance_id] = Foreman.uuid | foreman-rake console
Loading production environment (Rails 6.1.7)
Switch to inspect mode.
Setting[:instance_id] = Foreman.uuid
"dc4b3773-9ffe-447d-a904-ce8f58d92c7f"


Upload 3:
[root@taftsat 6-9-2023T092700]# cat b7dbe2e0-ed64-432b-8e43-38731ac327d4.json | json_reformat | grep satellite_instance_id
                        "satellite_instance_id": "dc4b3773-9ffe-447d-a904-ce8f58d92c7f",
                    "key": "satellite_instance_id",
                        "satellite_instance_id": "dc4b3773-9ffe-447d-a904-ce8f58d92c7f",
                    "key": "satellite_instance_id",


Upload 4:
[root@taftsat 6-9-2023T093500]# cat 985f82c6-0928-4cfe-8bdf-7ee2c4efad85.json | json_reformat | grep satellite_instance_id
                        "satellite_instance_id": "dc4b3773-9ffe-447d-a904-ce8f58d92c7f",
                    "key": "satellite_instance_id",
                        "satellite_instance_id": "dc4b3773-9ffe-447d-a904-ce8f58d92c7f",
                    "key": "satellite_instance_id",

Comment 2 Taft Sanders 2023-06-09 13:45:00 UTC
I forgot to mention. From the test Satellite, the UUID seen in the settings before running the foreman-rake command is one that was provided to it upon installation:
Value:         19b1acf2-cd60-47cc-bb30-a170a82a02ab

Comment 3 Shimon Shtein 2023-06-12 08:08:52 UTC

*** This bug has been marked as a duplicate of bug 2193451 ***