Description of problem: Host provisioned in Azure through Satellite, then registration fails after hanging for 5 minutes Version-Release number of selected component (if applicable): Satellite 6.13.1 but it's possible previous versions of Satellite are also affected How reproducible: Customer can reproduce the issue on demand Steps to Reproduce: 1. Provision from Satellite 2. Registration Fails 3. Delete the host from Satellite 4. Re-register > Successful. 1. Provision from Azure Portal > Register via workflow > Host is not present initially in Satellite > Successful Actual results: See above Expected results: See above Additional info: For some reason, the registration request got hang for 5 minutes many times, for example: 6256:2023-07-13T09:12:13 [D|tax|c773fda3] Current organization set to RIO TINTO 6413:2023-07-13T09:17:53 [I|app|c773fda3] ForemanWebhooks::EventSubscriber: host_updated.event.foreman event received 6434:2023-07-13T09:17:53 [I|app|c773fda3] ForemanWebhooks::EventSubscriber: host_updated.event.foreman event received 8214:2023-07-13T09:23:12 [I|app|c773fda3] ForemanWebhooks::EventSubscriber: host_updated.event.foreman event received 8222:2023-07-13T09:23:12 [I|aud|c773fda3] Katello::Host::SubscriptionFacet (126) update event on uuid 788a15ea-14c3-4729-85b7-962cc4c8eea4, c30ae099-0e89-493d-9aa2-281d0a3b6d51 8372:2023-07-13T09:29:16 [I|app|c773fda3] ForemanWebhooks::EventSubscriber: host_updated.event.foreman event received we need help to understand what could cause this. Further more, this only happens on the hosts built in Satellite. Please refer to case 03521529 for more details
Can you provide reproducer steps and results? Thanks!
Hi, I believe the problem is the rebuilding host while registering it, there is an upstream PR to fix this issue [0], could you verify that it solves your case? [0] https://github.com/theforeman/foreman/pull/9746
Adding needinfo based upon comment 7.
Hi Leos Stejskal, (In reply to Leos Stejskal from comment #7) > Hi, > I believe the problem is the rebuilding host while registering it, > there is an upstream PR to fix this issue [0], could you verify that it > solves your case? > > [0] https://github.com/theforeman/foreman/pull/9746 Thanks for the update. However, it doesn't seem the same problem to me. As I understand, the patch fixes the /register endpoint but in my case the issue resides in the /rhsm/consumers endpoint. This is because the post-install calls subscription-manager to register. Do you think it's still worth to apply the patch and register the host with the curl command? Thanks, Matt
> Do you think it's still worth to apply the patch and register the host with the curl command? Well, it's in the plan to use global registration also in kickstart templates, won't hurt to try it and see what are the improvements or yet unknown issues. > As I understand, the patch fixes the /register endpoint but in my case the issue resides in the /rhsm/consumers endpoint. Hmm, in that case it looks like a Katello issue. @Ian can your team take a look?
Moving the component to Content - Hosts since the issue appears to be in the /rhsm/consumers endpoint.