Hi Xiexs, You might need to configure pip to use your proxy.
I added my own element here: cache-devstack/install.d/98-setup-pip Basically: set -eux mkdir -p /root/.pip/ cat <<EOF > /root/.pip/pip.conf [global] proxy = <your proxy> EOF cp -f /root/.pip/pip.conf /etc/ Ramy From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com] Sent: Tuesday, August 04, 2015 12:05 AM To: OpenStack Development Mailing List (not for usage questions) <firstname.lastname@example.org> Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool Hi Ramy, Thanks for your help. I have already confirmed proxy setting again, and it works fine(no matter whether the NODEPOOL_ variables are declared or not): 1) not only in the host machine on which DIB run, 2) but also in the first half part of DIB(before the DIB running chroot). 3) furthmore, I ran the commands manually in the host env, they also works fine. $ sudo -H virtualenv /usr/zuul-swift-logs-env $ sudo -H /usr/zuul-swift-logs-env/bin/pip install python-magic argparse requests glob2 So, if I understood correctly, it seems obvious, that the proxy setting is missed when DIB goes into chroot env. Thus, when DIB attempts to connect internet to download/install/update some materials to prepare the image within the chroot env, the error will be encountered. In this case, DIB will run “pip install” in the chroot env zuul-swift-logs-env to install python-magic, argparse and so forth. Actually, all NODEPOOL_ variables were already declared by the install_master.sh previously, and the proxy setting also derived from the host machine`s proxy setting. Xiexs From: Asselin, Ramy [mailto:ramy.asse...@hp.com] Sent: Tuesday, August 04, 2015 12:54 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [CI]How to set proxy for nodepool Hi Xiexs, You are using disk image builder (DIB), so make sure your proxy is set correctly also without the NODEPOOL_ prefix. Those NODEPOOL_ prefixed variables are what would be used when DIB is not used / when the script approach is used with nova/glance (nodepool image-update). I don’t recommend using that if you can use DIB. Also, I’ve found some of the infra project-config elements don’t work in my environment and aren’t needed as they’re specific to infra. For those, simply comment out the portions that don’t work. I didn’t notice any negative side-effects. Ramy From: Xie, Xianshan [mailto:xi...@cn.fujitsu.com] Sent: Monday, August 03, 2015 9:37 PM To: email@example.com<mailto:firstname.lastname@example.org> Subject: [openstack-dev] [CI]How to set proxy for nodepool Hi All, When I ran “nodepool image-build <image-name>” to create a new image, I got this error message: … INFO nodepool.image.build.dpc: + sudo -H virtualenv /usr/zuul-swift-logs-env INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01 INFO nodepool.image.build.dpc: + sudo -H /usr/zuul-swift-logs-env/bin/pip install python-magic argparse requests glob2 INFO nodepool.image.build.dpc: sudo: unable to resolve host fnst01 INFO nodepool.image.build.dpc: Collecting python-magic INFO nodepool.image.build.dpc: Retrying (Retry(total=4, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with hostname'))': /simple/python-magic/ INFO nodepool.image.build.dpc: Retrying (Retry(total=3, connect=None, read=None, redirect=None)) after connection broken by 'ProtocolError('Connection aborted.', gaierror(-5, 'No address associated with hostname'))': /simple/python-magic/ … And I exported the bash env when the script elements/nodepool-base/install.d/90-venv-swift-logs ran, it seems that the nodepool proxy and dns has already been set: declare -x NODEPOOL_HTTPS_PROXY=http://xx.xx.xx.xx:8080/ <--valid proxy declare -x NODEPOOL_HTTP_PROXY="http://xx.xx.xx.xx:8080/" declare -x NODEPOOL_NO_PROXY="localhost,127.0.0.1" declare -x NODEPOOL_SCRIPTDIR="/etc/nodepool/scripts" declare -x NODEPOOL_STATIC_NAMESERVER="xx.xx.xx.xx" declare -x PS1="(zuul-swift-logs-env)" INFO nodepool.image.build.dpc: + cat /etc/resolv.conf INFO nodepool.image.build.dpc: nameserver xx.xx.xx.xx <--valid dns And I have tried to add element “local-config” into nodepool.yaml, but it does not work. So, my questions are: 1) These bash env will be passed into the virtualenv zuul-swift-logs-env after chroot, is it right? 2) If not, how to configure the proxy for nodepool? Many thanks to any suggestion. Xiexs
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev