Hey @puppeteers I’m in real need to have this fixe...
# forge-modules
c
Hey @puppeteers I’m in real need to have this fixed. Every time I try to run pdk test unit here, I get these errors:
Copy code
Error: Could not connect via HTTPS to https://forgeapi.puppet.com
  Unable to verify the SSL certificate
    The certificate may not be signed by a valid CA
    The CA bundle included with OpenSSL may not be valid or up to date
Error: Could not connect via HTTPS to https://forgeapi.puppet.com
  Unable to verify the SSL certificate
    The certificate may not be signed by a valid CA
    The CA bundle included with OpenSSL may not be valid or up to date
Error: Could not connect via HTTPS to https://forgeapi.puppet.com
  Unable to verify the SSL certificate
    The certificate may not be signed by a valid CA
    The CA bundle included with OpenSSL may not be valid or up to date
If there’s something I need to do, that’s fine, I just need to know what’s up here? In the middle of all this, one of my runs worked, and then it went back to failing every time on SSL. It would be really nice to get some eyes on this. I thought it was VPN, but I got off the private network, restarted my machine, adn am still having the same issues.
🆘 1
s
Hey @CVQuesty I don't know if this is the same issue which you were referring to yesterday, but I've asked the infra team to look at this at priority
r
Hi @CVQuesty, do you experience same without PDK or its just with PDK? Also is it possible to get the specific IP which is complaining if possible?
Have checked with team and haven't got any lead as of now but will keep on checking.
c
Only with PDK. And when it is cloning fixtures. In contrast, r10k on our server works perfectly every time, also looking at forgeapi. I’m certain this is something to do with PDK, I just don’t have enough knowledge to dig deep
Keep in mind that since this is Amazon and fronted by CloudFront. That it could be any IP from the pool at any time, and to make matters even more difficult, all the addresses are IPv6
ack 1
r
hmm, thanks for details. I do also suspect PDK but I also have limited knowledge about PDK. Let me check with broader team.
What version of PDK you are using? Also can you please try with latest if not and confirm there as well its persist ?
c
I was using an older one early in the day yesterday. Now I am using latest. Let me make it to the office and I’ll pick up here. Sorry for the time differential.
r
no issues, take your time. Will wait for your response. Thanks
Looks like this is also a known issue reported by PDK team https://github.com/puppetlabs/pdk/blob/main/docs/pdk_known_issues.md with 3.0.1, so upgrading to >= 3.1.0 should resolve this issue.
c
WEll….
Copy code
chs@mac133983 repos (development) $ pdk --version
3.2.0
Here’s the full output in case onceover is the culprit:
Copy code
chs@mac133983 control_repo (development) $ pdk bundle exec onceover run spec
pdk (WARN): Unable to determine Puppet version for module: no metadata.json present in module.
pdk (INFO): Using Ruby 3.2.3
pdk (INFO): Using Puppet 8.6.0
INFO	 -> Using Puppetfile '/Users/chs/Projects/Puppet/control_repo/.onceover/etc/puppetlabs/code/environments/production/Puppetfile'
INFO	 -> Deploying module to /Users/chs/Projects/Puppet/control_repo/.onceover/etc/puppetlabs/code/environments/production/modules/mcollective
INFO	 -> Deploying module to /Users/chs/Projects/Puppet/control_repo/.onceover/etc/puppetlabs/code/environments/production/modules/archive
INFO	 -> Deploying module to /Users/chs/Projects/Puppet/control_repo/.onceover/etc/puppetlabs/code/environments/production/modules/epel
INFO	 -> Deploying module to /Users/chs/Projects/Puppet/control_repo/.onceover/etc/puppetlabs/code/environments/production/modules/php
ERROR	 -> Module epel failed to synchronize due to SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain)
ERROR	 -> Module archive failed to synchronize due to SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain)
ERROR	 -> Module php failed to synchronize due to SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain)
ERROR	 -> Module mcollective failed to synchronize due to SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain)

r10k: Runtime error: #<Faraday::SSLError wrapped=#<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain)>>
/opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/protocol.rb:46:in `connect_nonblock': SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain) (Faraday::SSLError)
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/protocol.rb:46:in `ssl_socket_connect'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1674:in `connect'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1580:in `do_start'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1569:in `start'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:138:in `request_via_get_method'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:129:in `request_with_wrapped_block'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:122:in `perform_request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:66:in `block in call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/adapter.rb:50:in `connection'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:64:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/connection/connection_failure.rb:9:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/middleware.rb:18:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response_middleware.rb:36:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response/follow_redirects.rb:79:in `perform_with_redirection'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response/follow_redirects.rb:67:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/rack_builder.rb:154:in `build_response'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/connection.rb:516:in `run_request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/connection.rb:202:in `get'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/v3/base.rb:69:in `request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/lazy_accessors.rb:85:in `fetch'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:128:in `deprecated?'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:175:in `install'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:69:in `sync'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:83:in `block (2 levels) in sync_thread'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:81:in `each'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:81:in `block in sync_thread'
/opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/protocol.rb:46:in `connect_nonblock': SSL_connect returned=1 errno=0 peeraddr=[2600:9000:24d2:a200:1b:3556:90c0:93a1]:443 state=error: certificate verify failed (self-signed certificate in certificate chain) (OpenSSL::SSL::SSLError)
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/protocol.rb:46:in `ssl_socket_connect'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1674:in `connect'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1580:in `do_start'
	from /opt/puppetlabs/pdk/private/ruby/3.2.3/lib/ruby/3.2.0/net/http.rb:1569:in `start'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:138:in `request_via_get_method'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:129:in `request_with_wrapped_block'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:122:in `perform_request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:66:in `block in call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/adapter.rb:50:in `connection'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:64:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/connection/connection_failure.rb:9:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/middleware.rb:18:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response_middleware.rb:36:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response/follow_redirects.rb:79:in `perform_with_redirection'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday_middleware-1.2.0/lib/faraday_middleware/response/follow_redirects.rb:67:in `call'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/rack_builder.rb:154:in `build_response'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/connection.rb:516:in `run_request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/faraday-1.10.3/lib/faraday/connection.rb:202:in `get'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/v3/base.rb:69:in `request'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/puppet_forge-3.2.0/lib/puppet_forge/lazy_accessors.rb:85:in `fetch'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:128:in `deprecated?'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:175:in `install'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/module/forge.rb:69:in `sync'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:83:in `block (2 levels) in sync_thread'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:81:in `each'
	from /Users/chs/.pdk/cache/ruby/3.2.0/gems/r10k-3.16.0/lib/r10k/content_synchronizer.rb:81:in `block in sync_thread'

Error while running: #<RuntimeError: r10k could not install all required modules>
chs@mac133983 control_repo (development) $
But this is happening in non-onceover situations as well
And here’s the deal…. SOME of those repos are making it. a handful are failing to synch… epel, archive, php, and mcollective
based ohn the errors, it would seem to be r10k having the issue
Looks like it’s happening in basic rspec as well now after I removed both the puppet agent and pdk and reinstalling the latest PDK.
ok, I think that ticket did the trick. I added both the github and the forgeapi certificate chains to the PDK cert.pem and everything started working on rsopec. Let me try onceover
It fixed the omceover process too
I’m going to update that ticket that it is still an issue in current PDK
r
@Paula @David 'The Anvil' can you please assist here?
c
I would say that if the issue is the cert.pem in the existing PDK, then a release of PDK is the right answer.