hi,
downloading remote stemcell: Connection timed out - connect(2) (00:03:09)
Error 100: Connection timed out - connect(2)
For a more detailed error report, run: bosh task 5 --debug
so my openstack instance (the bosh vm too) is behind a proxy
so i answer YES to this assumption because a customization script could set the proxy; here is a sample :
#!/bin/bash
INSTANCE_USER=myuser
PROFILE_SCRIPT=/home/$INSTANCE_USER/.bash_profile
PROXY_PRESENT=`grep http_proxy $PROFILE_SCRIPT | wc -l`
if [[ $PROXY_PRESENT == "1" ]]
then
echo "proxy OK in $PROFILE_SCRIPT"
else
echo "proxy missing from $PROFILE_SCRIPT ; we add it"
echo "export https_proxy=proxy.intranet.fr:8080" >> $PROFILE_SCRIPT
echo "export no_proxy='127.0.0.1,localhost,169.254.169.254'" >> $PROFILE_SCRIPT
fi
with bosh micro i think i can't set this custo script ?
this case i try to add it by hand once bosh agent running
i try updating the following files :
/etc/profile OR /home/vcap/.bash_profile && /home/root/.bash_profile
(then always reboot the bosh agent)
but seems not solve my connect timeout issue
(cat /proc/<bosh agent or director PID>/environ never contains http_proxy env var)
i try to update director manifest file (target vm) : /var/vcap/jobs/director/config/director.yml
by adding "proxy_uri" attribute
but seems not solving my connect timeout too.. :'(
do you think that proxy_uri is supported for OpenStack ?
could i update bosh target vm to set http_proxy env var by hand ? where ?
should i restart the "micro bosh deploy" from scratch including "proxy_uri" attribute into micro_bosh.yml ?
in advance thanks
Regards
Brice