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.
Bug 1540974 - foreman-poxy raises "Failed to show puppet classes: Caught recursion on hostname" on listing classes for environments
Summary: foreman-poxy raises "Failed to show puppet classes: Caught recursion on host...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.2.13
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-01 12:35 UTC by Roman Plevka
Modified: 2023-09-14 04:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-28 19:35:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1187774 0 high CLOSED smart proxy puppet environment list errors under load 2021-02-22 00:41:40 UTC

Internal Links: 1187774

Description Roman Plevka 2018-02-01 12:35:17 UTC 
Description of problem:
A Content view publish task (with puppet modules) failed after its first subtask (Actions::Katello::Foreman::ContentUpdate) failed with getting a HTTP 406 from proxy (https://sat62_server.com:9090/puppet).

foreman-proxy/proxy.log reveals that the reason was most probably coming from puppet:
 E, [2018-01-31T03:45:25.847307 #71864] ERROR -- : Failed to show puppet classes: Caught recursion on hostname

this originates in a block in:
/usr/share/foreman-proxy/modules/puppet_proxy/puppet_api.rb:65


- second attempt (re-running the test) was successful (with using all the same settings) so it looks to me like we might deal with some concurrency issue (there was at least 1 more CV publish with puppet modules running in the same time window - see more in the attached logs)


Version-Release number of selected component (if applicable):
6.2.14-1

Steps to Reproduce:
1. possibly try to simultaneously publish multiple CV's containing the same puppet modules 

Actual results:
some publish tasks fail due to proxy returning 406.

Expected results:
no conflict.

Additional info:
Comment 3 Dmitri Dolguikh 2018-02-01 18:52:00 UTC 
"Caught recursion on hostname" error is coming from puppet. I was only able to find a report citing this error related to a Factor issue, not sure how this is related to puppet.

When puppet api provider is used (as opposed to the legacy provider), smart-proxy doesn't perform anything other than making a call to puppet server and relaying the data back.
Comment 5 Bryan Kearney 2019-02-07 12:09:45 UTC 
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Comment 6 Bryan Kearney 2019-02-28 19:35:24 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Comment 7 Red Hat Bugzilla 2023-09-14 04:16:15 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.