Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1108365

Summary: Puppet/puppet-agent errors appearing in logs every half hour on capsule
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: InfrastructureAssignee: Ivan Necas <inecas>
Status: CLOSED WORKSFORME QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.3CC: bbuckingham, bkearney, cwelton, mfuruta, michele, ohadlevy, pcfe, sauchter, xdmoon
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1462324 (view as bug list) Environment:
Last Closed: 2016-06-02 18:29:11 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:
Bug Depends On:    
Bug Blocks: 1115190, 1317008    

Description Corey Welton 2014-06-11 19:58:05 UTC
Description of problem:
Getting some odd error messages on capsule logs, every half hour, when puppet tries to do....something.

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

Satellite-6.0.3-RHEL-6-20140605.0

How reproducible:
unsure.

Steps to Reproduce:
1.  Install/populate capsule.
2.  Perhaps use capsule as puppet ca/puppet master in a host group, and register a system to the host group?  Unsure if this is necessary. 
3. wait and wait, at least half an hour, maybe more.
4. View logfiles.

Actual results:

[root@ibm-x3550m3-09 httpd]# tail -f puppet_error_ssl.log
[Wed Jun 11 20:06:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 20:06:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 20:36:21 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 20:36:21 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 20:36:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 20:36:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:06:21 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:06:21 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:06:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:06:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:36:21 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:36:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:36:22 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production
[Wed Jun 11 21:36:23 2014] [error] [client 10.34.36.133] File does not exist: /etc/puppet/rack/public/production

Seen in /var/log/messages

Jun 11 21:36:22 ibm-x3550m3-09 puppet-agent[17395]: (/File[/var/lib/puppet/lib]) Could not evaluate: Could not retrieve information from environment production source(s) puppet://ibm-x3550m3-09.lab.eng.brq.redhat.com/plugins
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: Using cached catalog
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: Could not retrieve catalog; skipping run
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: Could not send report: Error 405 on SERVER: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: <html><head>
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: <title>405 Method Not Allowed</title>
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: </head><body>
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: <h1>Method Not Allowed</h1>
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: <p>The requested method PUT is not allowed for the URL /production/report/ibm-x3550m3-09.lab.eng.brq.redhat.com.</p>
Jun 11 21:36:23 ibm-x3550m3-09 puppet-agent[17395]: </body></html>

Expected results:

I suppose we shouldn't be seeing this stuff in logs.

Additional info:
pretty basic capsule install, nothing exotic.

Comment 2 Brad Buckingham 2014-07-29 19:50:30 UTC
This issue stems from installing capsule on a system that is not provisioned via Satellite 6 (or Foreman).

Comment 4 Ohad Levy 2016-05-16 06:23:50 UTC
was the capsule synced with puppet content? the errors seem to indicate there is no environment production defined?

Comment 6 Corey Welton 2016-06-02 18:29:11 UTC
Closing this bug as non-reproducible.  Please reopen if the behavior is seen again.