[cni] do_compile network issue behind proxy for Hardknott

[cni] do_compile network issue behind proxy for Hardknott

[Joakim Roubert]

Hi!

After upgrade to Hardknott from Gatesgarth, building cni on a machine 
behind a proxy gives me network errors:

run.do_compile.18062' failed with exit code 1:                      go: 
github.com/onsi/ginkgo@v1.13.0: Get 
"https://proxy.golang.org/github.com/onsi/ginkgo/@v/v1.13.0.mod": dial 
tcp 142.250.74.81:443: connect: network is unreachable

The command that fails is

https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-networking/cni/cni_git.bb?h=hardknott&id=6c9b889224cedd42191ef5edc7e1f37b0c8ecfec#n37

and can be mitigated by explicitly setting the proxy environment 
variable on that line:

http_proxy=http://<myproxyserver>:<proxyport> 
https_proxy=http://<myproxyserver>:<proxyport> ${GO} build

Since building with Gatesgarth (where that line is the same in the 
recipe, but the cni version 0.7 instead of 0.8) worked fine I did not 
expect this to happen. Do you guys have any ideas? (Setting the 
environment variable as describe above does not strike me as the 
proper/best solution...)

BR,

/Joakim

Re: [meta-virtualization] [cni] do_compile network issue behind proxy for Hardknott

[Bruce Ashfield]

On Tue, Jun 15, 2021 at 7:31 AM Joakim Roubert <joakim.roubert@axis.com> wrote:
>
> Hi!
>
> After upgrade to Hardknott from Gatesgarth, building cni on a machine
> behind a proxy gives me network errors:
>
> run.do_compile.18062' failed with exit code 1:                      go:
> github.com/onsi/ginkgo@v1.13.0: Get
> "https://proxy.golang.org/github.com/onsi/ginkgo/@v/v1.13.0.mod": dial
> tcp 142.250.74.81:443: connect: network is unreachable
>
> The command that fails is
>
> https://git.yoctoproject.org/cgit/cgit.cgi/meta-virtualization/tree/recipes-networking/cni/cni_git.bb?h=hardknott&id=6c9b889224cedd42191ef5edc7e1f37b0c8ecfec#n37
>
> and can be mitigated by explicitly setting the proxy environment
> variable on that line:
>
> http_proxy=http://<myproxyserver>:<proxyport>
> https_proxy=http://<myproxyserver>:<proxyport> ${GO} build
>
> Since building with Gatesgarth (where that line is the same in the
> recipe, but the cni version 0.7 instead of 0.8) worked fine I did not
> expect this to happen. Do you guys have any ideas? (Setting the
> environment variable as describe above does not strike me as the
> proper/best solution...)

I have a note written on the paper in front of me "fix cni build for
no-network", and a half started fix. :D

So yes, cni is doing some fetches, due to missing go dependencies and
trying to do a go.mod build. Neither of which we want.

Let me dig up my changs and see how far away they are from being ready for test.

Bruce

>
> BR,
>
> /Joakim
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

Re: [meta-virtualization] [cni] do_compile network issue behind proxy for Hardknott

[Joakim Roubert]

On 2021-06-15 14:10, Bruce Ashfield wrote:
> 
> I have a note written on the paper in front of me "fix cni build for
> no-network", and a half started fix. :D

:-D

> Let me dig up my changs and see how far away they are from being ready 
> for test.

Awesome, thanks! I will be more than happy to evaluate such changes here 
in my builds.

BR,

/Joakim