<div dir="ltr">I was able to get most of the tests working by configuring the classic environment to use the proxy. I think long-term the correct solution is still system-wide proxy support on ubuntu core, and there's already a bug open for that, so I'll keep working with the current methods and propose changes for the tests if those are reasonable to make without affecting other functionality. Since the VMs are all in the lab, getting full network connections for them would be difficult to get approved by IS, and I think having most of the testing working behind the proxy is a pretty good state for now.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 7, 2017 at 1:55 PM, Gustavo Niemeyer <span dir="ltr"><<a href="mailto:gustavo.niemeyer@canonical.com" target="_blank">gustavo.niemeyer@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Max,<div><br></div><div>The problem isn't spread itself, as it won't try to communicate out of the host by itself. The problem is that snapd's test suite expects to be able to talk to the network.<div><br></div><div>Someone would have to go through and fix all such cases to go through the proxy, which is perhaps more troubling than connecting the VM itself into the network?</div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Mon, Jan 23, 2017 at 8:01 PM, Max Brustkern <span dir="ltr"><<a href="mailto:max.brustkern@canonical.com" target="_blank">max.brustkern@canonical.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div>I'm trying to run spread tests on an ubuntu core VM in a lab that needs to use a proxy for web access. The mirrors are redirected, so the package installations work as expected, but I run into problems with go get:<br><br>++ classic 'GOPATH=/home/gopath go get ../../home/gopath/src/<a href="http://github.com/snapcore/snapd/tests/lib/snapbuild" target="_blank">github.c<wbr>om/snapcore/snapd/tests/lib/sn<wbr>apbuild</a>'<br>Cannot determine calling user, logging into classic as root<br>mount: devpts is already mounted or /dev/pts busy<br> devpts is already mounted on /dev/pts<br>package <a href="http://gopkg.in/yaml.v2" target="_blank">gopkg.in/yaml.v2</a>: unrecognized import path "<a href="http://gopkg.in/yaml.v2" target="_blank">gopkg.in/yaml.v2</a>" (https fetch: Get <a href="https://gopkg.in/yaml.v2?go-get=1" target="_blank">https://gopkg.in/yaml.v2?go-ge<wbr>t=1</a>: dial tcp <a href="http://45.33.69.124:443" target="_blank">45.33.69.124:443</a>: i/o timeout)<br>package <a href="http://gopkg.in/check.v1" target="_blank">gopkg.in/check.v1</a>: unrecognized import path "<a href="http://gopkg.in/check.v1" target="_blank">gopkg.in/check.v1</a>" (https fetch: Get <a href="https://gopkg.in/check.v1?go-get=1" target="_blank">https://gopkg.in/check.v1?go-g<wbr>et=1</a>: dial tcp <a href="http://45.33.69.124:443" target="_blank">45.33.69.124:443</a>: i/o timeout)<br>++ sysctl -w net.ipv6.conf.all.disable_ipv6<wbr>=0<br>net.ipv6.conf.all.disable_ipv6 = 0<br>-----<br>2017/01/23 16:46:54 Restoring project on external:ubuntu-core-16-64...<br>2017/01/23 16:46:55 Successful tasks: 0<br>2017/01/23 16:46:55 Aborted tasks: 107<br>2017/01/23 16:46:55 Failed project prepare: 1<br> - external:ubuntu-core-16-64:pro<wbr>ject<br>2017/01/23 16:46:55 Keeping external:ubuntu-core-16-64 at <a href="http://127.0.0.1:54323" target="_blank">127.0.0.1:54323</a><br>error: unsuccessful run<br></div><br></div>I'm using the following spread commands to run on the local VM:<br>export SPREAD_EXTERNAL_ADDRESS=127.0.<wbr>0.1:$PORT<br>./tests/lib/external/prepare-s<wbr>sh.sh 127.0.0.1 $PORT $USER<br>spread -v -reuse external:ubuntu-core-16-64 | tee $WORKSPACE/spread-output<br><br></div><div>How should I configure spread to make go aware of the proxy?<br><br></div><div>Thanks,<br></div><div>Max<br></div></div>
<br></div></div><span class="HOEnZb"><font color="#888888">--<br>
Snapcraft mailing list<br>
<a href="mailto:Snapcraft@lists.snapcraft.io" target="_blank">Snapcraft@lists.snapcraft.io</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailm<wbr>an/listinfo/snapcraft</a><br>
<br></font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div class="m_-5956241181225859862gmail_signature" data-smartmail="gmail_signature">gustavo @ <a href="http://niemeyer.net" target="_blank">http://niemeyer.net</a></div>
</font></span></div></div></div>
<br>--<br>
Snapcraft mailing list<br>
<a href="mailto:Snapcraft@lists.snapcraft.io">Snapcraft@lists.snapcraft.io</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snapcraft" rel="noreferrer" target="_blank">https://lists.ubuntu.com/<wbr>mailman/listinfo/snapcraft</a><br>
<br></blockquote></div><br></div>