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 1462324 - Puppet/puppet-agent errors appearing in logs on capsule and hosts registered with capsule
Summary: Puppet/puppet-agent errors appearing in logs on capsule and hosts registered ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Puppet
Version: 6.2.9
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker 1317008
TreeView+ depends on / blocked
 
Reported: 2017-06-16 17:50 UTC by Mihir Lele
Modified: 2020-08-13 09:23 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1108365
Environment:
Last Closed: 2017-11-13 13:59:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Mihir Lele 2017-06-16 17:50:19 UTC 
Description of problem:

Newly registered hosts with capsule are unable to get certs.

How reproducible: Always

Steps to Reproduce:

1) Register a system with the capsule
2) Install puppet on the host
3) Run "puppet agent -t"



Actual results:

Seen in /var/log/messages:

Jun 13 10:42:31 cap1 puppet-agent[31445]: Finished catalog run in 1.45 seconds
Jun 13 10:42:31 cap1 puppet-agent[31445]: Could not send report: Error 405 on SERVER: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Jun 13 10:42:31 cap1 puppet-agent[31445]: <html><head>
Jun 13 10:42:31 cap1 puppet-agent[31445]: <title>405 Method Not Allowed</title>
Jun 13 10:42:31 cap1 puppet-agent[31445]: </head><body>
Jun 13 10:42:31 cap1 puppet-agent[31445]: <h1>Method Not Allowed</h1>
Jun 13 10:42:31 cap1 puppet-agent[31445]: <p>The requested method PUT is not allowed for the URL /KT_aceminc_abc_RHEL7_Capsule_25/report/test1.example.com.</p>
Jun 13 10:42:31 cap1 puppet-agent[31445]: </body></html>


Expected results:

Puppet agent -t should generate a cert sign request on the capsule.

Additional info:

Output from one host registered with capsule:

# systemctl status puppet
● puppet.service - Puppet agent
   Loaded: loaded (/usr/lib/systemd/system/puppet.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-06-15 16:02:24 EDT; 20s ago
 Main PID: 3603 (puppet)
   CGroup: /system.slice/puppet.service
           └─3603 /usr/bin/ruby /usr/bin/puppet agent --no-daemonize

Jun 15 16:02:31 test1.example.com puppet-agent[3612]: (/Stage[main]/Etc_snmp_snmpd_conf/File[/etc/snmp/snmpd.conf]) Could not ....conf
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: (/Stage[main]/Mesg_csh_sh/File[/etc/profile.d/mesg.sh]) Could not evalua...sg.sh
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: Finished catalog run in 1.44 seconds
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: Could not send report: Error 405 on SERVER: <!DOCTYPE HTML PUBLIC "-//IE.../EN">
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: <html><head>
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: <title>405 Method Not Allowed</title>
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: </head><body>
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: <h1>Method Not Allowed</h1>
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: <p>The requested method PUT is not allowed for the URL /KT_acmeinc....</p>
Jun 15 16:02:32 test1.example.com puppet-agent[3612]: </body></html>
Hint: Some lines were ellipsized, use -l to show in full.
Comment 3 Daniel Lobato Garcia 2017-11-13 08:23:39 UTC 
Mihir, is there any known way to reproduce this? As you mention, normally you get the cert request doing exactly these steps & in other capsule it's working fine.
Comment 4 Mihir Lele 2017-11-13 09:36:54 UTC 
There is no way to reproduce this. You can go ahead and close it this bz.
Comment 5 Brad Buckingham 2017-11-13 13:59:52 UTC 
Closing based upon comment 4.  Please feel free to re-open, if the issue is reproducible.
Note You need to log in before you can comment on or make changes to this bug.