Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-9942

no_proxy environment variable does not work

    XMLWordPrintable

Details

    • Coremunity
    • Platform Core KANBAN
    • Needs Assessment
    • Bug Fix
    • Hide
      If the agent is configured to use an HTTP proxy and it attempts to connect to a host that matches an entry in the "NO_PROXY" environment variable, then puppet will not use the proxy, and instead connect directly to the host. This feature was originally introduced in PUP-4030, but it didn't work.
      Show
      If the agent is configured to use an HTTP proxy and it attempts to connect to a host that matches an entry in the "NO_PROXY" environment variable, then puppet will not use the proxy, and instead connect directly to the host. This feature was originally introduced in PUP-4030 , but it didn't work.
    • Needs Assessment

    Description

      Commit 90560edf0f43f5382bd539646988f7a96ea3809e for PUP-4030 added the ability to skip an http proxy if the host and port matched an entry in the NO_PROXY environment variable. However it didn't actually work because our connection factory passed the Site object instead of a String or URI. To reproduce specify an unused http proxy port and try to not use a proxy for the puppet server:

      $ env NO_PROXY=$(bundle exec puppet config print server --section main) bundle exec puppet agent -t --http_proxy_host localhost --http_proxy_port 12345
      		 
      Warning: Unable to fetch my node definition, but the agent run will continue:
      		 
      Warning: Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)
      		 
      Info: Retrieving pluginfacts
      		 
      Error: /File[/Users/josh/.puppetlabs/opt/puppet/cache/facts.d]: Failed to generate additional resources using 'eval_generate': Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)
      		 
      Error: /File[/Users/josh/.puppetlabs/opt/puppet/cache/facts.d]: Could not evaluate: Could not retrieve file metadata for puppet:///pluginfacts: Failed to open TCP connection to localhost:12345 (Connection refused - connect(2) for "localhost" port 12345)
      		 
      ...

       

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-4030 Add support for no_proxy env var

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

              josh Josh Cooper
              josh Josh Cooper
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support