Spread Tests with proxy (mostly go get)

[Max Brustkern]

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.

On Tue, Feb 7, 2017 at 1:55 PM, Gustavo Niemeyer <
gustavo.niemeyer at canonical.com> wrote:

> Hi Max,
>
> 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.
>
> 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?
>
> On Mon, Jan 23, 2017 at 8:01 PM, Max Brustkern <
> max.brustkern at canonical.com> wrote:
>
>> 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:
>>
>> ++ classic 'GOPATH=/home/gopath go get ../../home/gopath/src/github.c
>> om/snapcore/snapd/tests/lib/snapbuild'
>> Cannot determine calling user, logging into classic as root
>> mount: devpts is already mounted or /dev/pts busy
>>        devpts is already mounted on /dev/pts
>> package gopkg.in/yaml.v2: unrecognized import path "gopkg.in/yaml.v2"
>> (https fetch: Get https://gopkg.in/yaml.v2?go-get=1: dial tcp
>> 45.33.69.124:443: i/o timeout)
>> package gopkg.in/check.v1: unrecognized import path "gopkg.in/check.v1"
>> (https fetch: Get https://gopkg.in/check.v1?go-get=1: dial tcp
>> 45.33.69.124:443: i/o timeout)
>> ++ sysctl -w net.ipv6.conf.all.disable_ipv6=0
>> net.ipv6.conf.all.disable_ipv6 = 0
>> -----
>> 2017/01/23 16:46:54 Restoring project on external:ubuntu-core-16-64...
>> 2017/01/23 16:46:55 Successful tasks: 0
>> 2017/01/23 16:46:55 Aborted tasks: 107
>> 2017/01/23 16:46:55 Failed project prepare: 1
>>     - external:ubuntu-core-16-64:project
>> 2017/01/23 16:46:55 Keeping external:ubuntu-core-16-64 at 127.0.0.1:54323
>> error: unsuccessful run
>>
>> I'm using the following spread commands to run on the local VM:
>> export SPREAD_EXTERNAL_ADDRESS=127.0.0.1:$PORT
>> ./tests/lib/external/prepare-ssh.sh 127.0.0.1 $PORT $USER
>> spread -v -reuse external:ubuntu-core-16-64 | tee $WORKSPACE/spread-output
>>
>> How should I configure spread to make go aware of the proxy?
>>
>> Thanks,
>> Max
>>
>> --
>> Snapcraft mailing list
>> Snapcraft at lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/snapcraft
>>
>>
>
>
> --
> gustavo @ http://niemeyer.net
>
> --
> Snapcraft mailing list
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170208/c9cfa01a/attachment.html>