[Starlingx-discuss] Does openstack-helm-infra needs network access to build?

Scott Little scott.little at windriver.com
Wed Nov 7 15:33:04 UTC 2018


Al,

Would it be possible to create build-pkgs --helm-charts .... or 
build-pkgs --network_required build phase.  A peer to 'std' and 'rt'.  
Only enable networking for that subset of builds.  Probably better than 
enabling networking for the build of all packages.

Proxy setup is still required for folks that want to do the container 
portions of the build.

Scott


On 18-11-07 09:13 AM, Bailey, Henry Albert (Al) wrote:
> Do you guys have this commit?
> https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bbfd0c74350
>
> It flips the networking flag to True
>
> Al
>
> -----Original Message-----
> From: Hu, Yong [mailto:yong.hu at intel.com]
> Sent: Tuesday, November 06, 2018 10:50 PM
> To: Cordoba Malibran, Erich; starlingx-discuss at lists.starlingx.io
> Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build?
>
> I also met the same problem, and resolved it by adding proxy settings into “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto”:
> config_opts[‘rpmbuild_networking’] = False
> + config_opts[‘no_proxy’] = ‘127.0.0.1’
> + config_opts[‘http_proxy’]= ‘http://<your_http_proxy>:<your_http_proxy_port>’
> + config_opts[‘https_proxy’]= ‘http:// <your_https_proxy>:<your_https_proxy_port>’
>
> Here is my screenshot of my build:
> 03:35:07 ===== wait for last jobs in iteration 1 to complete =====
> 03:35:07 building openstack-helm-infra-1.0-3.tis.src.rpm
> 03:36:02 End build on ‘b0’: /localdisk/loadbuild/yhu6/starlingx/std/rpmbuild/SRPMS/openstack-helm-infra-1.0-3.tis.src.rpm
> 03:36:02 Success building openstack-helm-infra-1.0-3.tis.src.rpm on ‘b0’ (edited)
>
> I might file a patch to "~/build-tools/repo_files/mock.cfg.proto b/build-tools/repo_files/mock.cfg.proto", which is the original copy of “~/cgcs-root/cgcs-centos-repo/mock.cfg.proto".
> Though, I also like to see if there is a better solution.
>
> -yong
>
> On 07/11/2018, 8:29 AM, "Cordoba Malibran, Erich" <erich.cordoba.malibran at intel.com> wrote:
>
>      Hi all,
>      
>      We are seeing a failure today in our build environment. The openstack-
>      helm-infra package is failing. Checking the logs it seems that the
>      network access is required during building:
>      
>      Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
>      Error: Looks like "https://kubernetes-charts.storage.googleapis.com" is not a valid chart repository or cannot be reached: Get https://kubernetes-charts.storage.googleapis.com/index.yaml: proxyconnect tcp: dial tcp: lookup <our-proxy> on [::1]:53: dial udp [::1]:53: connect: cannot assign requested address
>      error: Bad exit status from /var/tmp/rpm-tmp.KecSPl (%build)
>      
>      We run the build in an isolated environment without internet access.
>      
>      Is someone seeing something similar? If this is true, then what would
>      be the best practice here, do we want network access while building? or
>      it should work in an isolated environment?
>      
>      Thanks in advance
>      
>      -Erich
>      _______________________________________________
>      Starlingx-discuss mailing list
>      Starlingx-discuss at lists.starlingx.io
>      http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
>      
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss





More information about the Starlingx-discuss mailing list