Host not creating whil erun puppet agent

Problem: Built th enew setup with Foreman 3.10 and puppet 7. Added smart proxy for puppet master. But when run puppet agent on client it not get creating in Foreman in All Hosts.

Expected outcome: When run the puppet agent, host should create in foreman.

Foreman and Proxy versions: Foreman 3.10

Foreman and Proxy plugin versions: Foreman 3.10

Distribution and version: Formeman 3.10 and puppet 7

Other relevant data:

While run puppet agent on host, Foreman production logs showing the it fetched the reports but host on visible in Foreman GUI.

2024-07-30T04:08:53 [I|app|0e0eff52] Started GET “/notification_recipients” for 172.27.52.104 at 2024-07-30 04:08:53 -0700
2024-07-30T04:08:53 [I|app|0e0eff52] Processing by NotificationRecipientsController#index as JSON
2024-07-30T04:08:53 [I|app|0e0eff52] Completed 200 OK in 5ms (Views: 0.1ms | ActiveRecord: 0.7ms | Allocations: 1967)
2024-07-30T04:08:55 [I|app|bdca97fc] Started POST “/api/hosts/facts” for 10.210.160.12 at 2024-07-30 04:08:55 -0700
2024-07-30T04:08:55 [I|app|bdca97fc] Processing by Api::V2::HostsController#facts as JSON
2024-07-30T04:08:55 [I|app|bdca97fc] Parameters: {“facts”=>“[FILTERED]”, “name”=>“noivl-rhel84.cadence.com”, “certname”=>“noivl-rhel84.cadence.com”, “apiv”=>“v2”, “host”=>{“certname”=>“noivl-rhel84.cadence.com”, “name”=>“noivl-rhel84.example.com”}}
2024-07-30T04:08:55 [I|app|bdca97fc] Import facts for ‘noivl-rhel84.cadence.com’ completed. Added: 0, Updated: 27, Deleted 0 facts
2024-07-30T04:08:55 [I|app|bdca97fc] Completed 201 Created in 178ms (Views: 2.5ms | ActiveRecord: 28.9ms | Allocations: 45690)
2024-07-30T04:08:55 [I|app|171f57e2] Started GET “/node/noivl-rhel84.example.com?format=yml” for 10.210.160.12 at 2024-07-30 04:08:55 -0700
2024-07-30T04:08:55 [I|app|171f57e2] Processing by HostsController#externalNodes as YML
2024-07-30T04:08:55 [I|app|171f57e2] Parameters: {“name”=>“noivl-rhel84.example.com”}
2024-07-30T04:08:55 [I|app|171f57e2] Rendered text template (Duration: 0.0ms | Allocations: 1)
2024-07-30T04:08:55 [I|app|171f57e2] Completed 200 OK in 34ms (Views: 0.2ms | ActiveRecord: 6.3ms | Allocations: 13788)
2024-07-30T04:08:56 [I|app|228e0be8] Started POST “/api/config_reports” for 10.210.160.12 at 2024-07-30 04:08:56 -0700
2024-07-30T04:08:56 [I|app|228e0be8] Processing by Api::V2::ConfigReportsController#create as JSON
2024-07-30T04:08:56 [I|app|228e0be8] Parameters: {“config_report”=>“[FILTERED]”, “apiv”=>“v2”}
2024-07-30T04:08:56 [I|app|228e0be8] Scanning report with: Foreman::PuppetReportScanner, ForemanAnsible::AnsibleReportScanner
2024-07-30T04:08:56 [I|app|228e0be8] Imported report for noivl-rhel84.example.com in 27.7 ms, status refreshed in 16.2 ms
2024-07-30T04:08:56 [I|app|228e0be8] Rendered api/v2/config_reports/create.json.rabl (Duration: 1.5ms | Allocations: 822)
2024-07-30T04:08:56 [I|app|228e0be8] Completed 201 Created in 53ms (Views: 2.5ms | ActiveRecord: 12.8ms | Allocations: 23434)

Not : In Foreman setting under facts, Option “Create new host when facts are uploaded” is “Yes”

Just a wild guess, but this is usually caused by the hosts being created without any organization/location context. Can you see the hosts when you switch both organization and location to “Any”?
If this is the problem, you can create a custom fact on the hosts before running Puppet against the new infrastructure to pre-assign the organization and location. The facts need to be named “foreman_organization” and “foreman_location” by default, the names can be changed via a setting (Administer → Settings → Facts in the UI).