Jira (PUP-10106) Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb

2019-10-19 Thread Tom Parker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker commented on  PUP-10106  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb   
 

  
 
 
 
 

 
 Further testing shows that the issue is in the handling of no_proxy for a domain match.  NO_PROXY="ls.cbn, localhost, puppet, 127.0.0.1" fails. NO_PROXY="glycon.ls.cbn, ls.cbn, localhost, puppet, 127.0.0.1" works.   As far as I know this is incorrect behaviour as ls.cbn should match *.ls.cbn   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.8509.1571517780048%40Atlassian.JIRA.


Jira (PUP-10106) Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb

2019-10-19 Thread Tom Parker (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Parker created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-10106  
 
 
  Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 PUP 5.5.17  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/10/19 11:52 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Tom Parker  
 

  
 
 
 
 

 
 Puppet Version: 5.5.17 Puppet Server Version: 5.3.10 OS Name/Version: CentOS 7 Since the update to puppet agent 5.5.17 the puppetdb forge module is using the configured proxy server and ignoring the no_proxy setting when trying to validate the connection to puppetdb.  This worked properly on 5.5.16.  My environment proxy settings are: *http_proxy=http://ottinstall.ls.cbn:3128* *ftp_proxy=http://ottinstall.ls.cbn:3128* *https_proxy=http://ottinstall.ls.cbn:3128* no_proxy=ls.cbn, localhost, puppet, 127.0.0.1 My puppetdb server is: *https://glycon.ls.cbn:8081* Desired Behavior:  Respect the no_proxy value ls.cbn and not proxy connections to https://glycon.ls.cbn:8018 Actual Behavior: opening connection to ottinstall.ls.cbn:3128... opened <- "CONNECT glycon.ls.cbn:8081 HTTP/1.1\r\nHost: glycon.ls.cbn:8081\r\n\r\n" -> "HTTP/1.1 403 Forbidden\r\n" -> "Server: squid/3.5.20\r\n" -> "Mime-Version: 1.0\r\n" -> "Date: Sat, 19 Oct 2019 18:46:40 GMT\r\n" -> "Content-Type: text/html;charset=utf-8\r\n" -> "Content-Length: 3448\r\n" -> "X-Squid-Error: ERR_ACCESS_DENIED 0\r\n" -> "Vary: Accept-Language\r\n" -> "Content-Language: en\r\n" -> "X-Cache: MISS from ottinstall.ls.cbn\r\n" -> "X-Cache-Lookup: NONE from ottinstall.ls.cbn:80\r\n" -> "Via: 1.1 ottinstall.ls.cbn (squid/3.5.20)\r\n" -> "Connection: keep-alive\r\n" -> "\r\n" Conn close because of connect error 403 "Forbidden" Notice: Unable to connect to puppetdb server (https://glycon.ls.cbn:8081): 403 "Forbidden"