puppet enterprise code manager issue

[Robert Chen]

my environment needs http_proxy, https_proxy for modules. probably code manager issue is an proxy issue 

#  puppet-code deploy  lab -l debug --wait

2016-05-12 13:39:48.388674 DEBUG puppetlabs.puppet-code - Loaded global configuration from /etc/puppetlabs/client-tools/puppet-code.conf

2016-05-12 13:39:48.388889 DEBUG puppetlabs.puppet-code - Loaded user configuration from /root/.puppetlabs/client-tools/puppet-code.conf

Deploying environment: lab

2016-05-12 13:39:48.388961 INFO  puppetlabs.puppet-access - Finding token at path /root/.puppetlabs/token

2016-05-12 13:39:48.390796 DEBUG puppetlabs.puppet-code - puppet-code version is 0.1.0 (commit 9caf577c432f50830341215aab29dc490909981e)

2016-05-12 13:39:48.390879 DEBUG leatherman.curl:223 - requesting https://aaa.bbb:8170/code-manager/v1/deploys.

2016-05-12 13:39:48.395317 DEBUG leatherman.curl:463 - Trying 10.254.12.72...

2016-05-12 13:39:48.398554 DEBUG leatherman.curl:463 - Connected to gateway.bbb(10.254.12.72) port 8000 (#0)

2016-05-12 13:39:48.398610 DEBUG leatherman.curl:463 - Establish HTTP proxy tunnel to lvappi00356.bbb:8170

2016-05-12 13:39:48.415798 DEBUG leatherman.curl:463 - Received HTTP code 504 from proxy after CONNECT

2016-05-12 13:39:48.415885 DEBUG leatherman.curl:463 - Closing connection 0

Unhandled exception: Failure when receiving data from the peer

I saw something under code-staging but no modules there:

[root@lvappi00356 lab]# pwd

/etc/puppetlabs/code-staging/environments/lab

[root@lvappi00356 lab]# ls -l

total 12

drwxr-xr-x. 2 pe-puppet pe-puppet   37 May 12 12:01 manifests

-rw-r--r--. 1 pe-puppet pe-puppet  218 May 12 12:01 metadata.json

-rw-r--r--. 1 pe-puppet pe-puppet 1172 May 12 13:23 Puppetfile

-rw-r--r--. 1 pe-puppet pe-puppet 1589 May 12 12:01 README.md

drwxr-xr-x. 2 pe-puppet pe-puppet   20 May 12 12:01 tests

 

 

I can git clone the modules:

 

[root@lvappi00356 /]# git clone https://github.com/puppetlabs/puppetlabs-dsc.git

Cloning into 'puppetlabs-dsc'...

remote: Counting objects: 13452, done.

remote: Compressing objects: 100% (13/13), done.

remote: Total 13452 (delta 1), reused 0 (delta 0), pack-reused 13438

Receiving objects: 100% (13452/13452), 11.53 MiB | 3.84 MiB/s, done.

Resolving deltas: 100% (8767/8767), done.

[Alex Dreyer]

The puppet code command connects to code-manager in puppet-server over https. It looks like your proxy is getting in the way of that. Can you disable the proxy configuration in the shell you're running puppet code from? You may get better messages that way. You can also try tailing  '/var/log/puppetlabs/puppetserver/puppetserver.log' while you're deploying.

Unfortunately, http proxies for git repos won't be supported until the next release of Puppet Enterprise. You could try mirroring modules internally or installing them from puppet forge which code-manager can use proxies to connect to in all releases. Otherwise you'll have to wait for the next Puppet Enterprise release to use code-manager. 

[Rob Nelson]

A hack might be to have a proxy in the network. I'm sure you could use squid to transparent proxy for the master only and let everything else go direct, or redirect port 80 from the master to a proxy semi-transparently (no agent config but requires some packet inspection and retorting of traffic).

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/54b7c064-9dc5-49e0-8a55-6c2f191667dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Rob Nelson
rnel...@gmail.com