Jira (PUP-10121) Could not request certificate

18 views
Skip to first unread message

Gauthier HEISS (JIRA)

unread,
Nov 7, 2019, 9:22:03 AM11/7/19
to puppe...@googlegroups.com
Gauthier HEISS created an issue
 
Puppet / Bug PUP-10121
Could not request certificate
Issue Type: Bug Bug
Affects Versions: PUP 5.5.17
Assignee: Unassigned
Components: Networking
Created: 2019/11/07 6:21 AM
Environment:

Redhat Entreprise Linux 7.7
Puppet agent 5.5.17

Priority: Normal Normal
Reporter: Gauthier HEISS

Puppet Version: 5.5.17
Puppet Server Version: 5.3.6
OS Name/Version: RHEL 7.7

I am migrating RHEL servers from RHS 5 to 6. Everything is working properly, except for requesting Puppet Certificate. After editing my puppet.conf on my client, and do a puppet agent -t for example, I have error "Error: Could not request certificate: wrong number of arguments (given 1, expected 2)".

Desired Behavior: Get an actual certificate request

Actual Behavior: Got the error "Error: Could not request certificate: wrong number of arguments (given 1, expected 2)".

 

Debug: Selected server from the ca_server setting: [RHS URL]
Debug: Selected port from the ca_port setting: 8140
Debug: Creating new connection for [RHS URL]:8140
Error: Could not request certificate: wrong number of arguments (given 1, expected 2)
/opt/puppetlabs/puppet/lib/ruby/2.4.0/net/http/exceptions.rb:6:in `initialize'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:322:in `new'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:322:in `rescue in execute_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:306:in `execute_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:186:in `block (2 levels) in do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:332:in `block in with_connection'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/nocache_pool.rb:15:in `with_connection'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:331:in `with_connection'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:183:in `block in do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:180:in `upto'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:180:in `do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/connection.rb:80:in `get'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:160:in `http_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:139:in `http_get'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:174:in `block in find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:263:in `block in do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/request.rb:231:in `do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:263:in `do_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:167:in `find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/certificate/rest.rb:12:in `find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:198:in `find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:201:in `certificate'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/ssl/host.rb:329:in `wait_for_cert'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:483:in `wait_for_certificates'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:349:in `run_command'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `block in run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:667:in `exit_on_fail'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:375:in `run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:139:in `run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:77:in `execute'
/opt/puppetlabs/puppet/bin/puppet:5:in `<main>'

 

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Josh Cooper (JIRA)

unread,
Nov 7, 2019, 5:28:03 PM11/7/19
to puppe...@googlegroups.com

Josh Cooper (JIRA)

unread,
Nov 7, 2019, 5:28:03 PM11/7/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Team: Coremunity

Josh Cooper (JIRA)

unread,
Nov 8, 2019, 12:26:03 PM11/8/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 6.11.0
Fix Version/s: PUP 6.4.5
Fix Version/s: PUP 5.5.18

Melissa Stone (JIRA)

unread,
Nov 8, 2019, 12:44:04 PM11/8/19
to puppe...@googlegroups.com
Melissa Stone assigned an issue to Melissa Stone
Change By: Melissa Stone
Assignee: Melissa Stone

Melissa Stone (JIRA)

unread,
Nov 8, 2019, 12:45:03 PM11/8/19
to puppe...@googlegroups.com
Melissa Stone updated an issue
Change By: Melissa Stone
Sprint: Platform Core KANBAN

Josh Cooper (JIRA)

unread,
Nov 12, 2019, 6:17:04 PM11/12/19
to puppe...@googlegroups.com

Melissa Stone (JIRA)

unread,
Nov 12, 2019, 7:32:03 PM11/12/19
to puppe...@googlegroups.com

In progress since I need to backport these changes to the 5.5.x branch

Melissa Stone (JIRA)

unread,
Nov 14, 2019, 11:51:03 AM11/14/19
to puppe...@googlegroups.com

This has passed CI as a part of the master pipeline, but I still need to backport it to the 5.5.x branch. The merge up to 6.4.x and to master will also need some hand holding. I'd like to keep this ticket open until that work is wrapped up.

Melissa Stone (JIRA)

unread,
Nov 14, 2019, 12:02:04 PM11/14/19
to puppe...@googlegroups.com
Melissa Stone updated an issue
Change By: Melissa Stone
Release Notes Summary:     Rather than create a new exception class when we catch connection
    errors, we should raise the original exception. Previously, this rescue
    block was modified to add additional contextual information to the
    exceptions we were catching to give the user more information around the
    context of failures. Rather than raising the original message, it would
    create a new exception with the additional information.

    This commit simply logs the error with Puppet with the additional
    information, and raises the original caught exception. This saves us
    from errors that stem from different error initializer expectations.
Release Notes: Bug Fix

Josh Cooper (JIRA)

unread,
Nov 14, 2019, 2:30:05 PM11/14/19
to puppe...@googlegroups.com

Melissa Stone (JIRA)

unread,
Nov 15, 2019, 1:18:05 PM11/15/19
to puppe...@googlegroups.com

and this has passed ci for 5.5.x with puppet-agent 5.5.17.80.g75ab990. Since it's passed both master and 5.5.x, I think it's safe to assume it'll pass for 6.4.x as well.

Heston Hoffman (JIRA)

unread,
Nov 15, 2019, 5:37:05 PM11/15/19
to puppe...@googlegroups.com
Heston Hoffman updated an issue
Change By: Heston Hoffman
Labels: resolved-issue-added
Reply all
Reply to author
Forward
0 new messages