Bug 1540974

Summary:	foreman-poxy raises "Failed to show puppet classes: Caught recursion on hostname" on listing classes for environments
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Puppet	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.13	CC:	dmitri, paji
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-02-28 19:35:24 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 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