[Starlingx-discuss] Does openstack-helm-infra needs network access to build?
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
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@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Do you guys have this commit? https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bb... It flips the networking flag to True Al -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi AI, We do have this update in build-tools. The problem was that our build environment is not able to directly access Google site without a special http/https proxy. Regards, Yong On 07/11/2018, 10:14 PM, "Bailey, Henry Albert (Al)" <Al.Bailey@windriver.com> wrote: Do you guys have this commit? https://github.com/openstack/stx-root/commit/1615f281093af91da3b998209ff90bb... It flips the networking flag to True Al -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On Wed, 2018-11-07 at 22:22 +0800, Hu, Yong wrote:
Hi AI, We do have this update in build-tools. The problem was that our build environment is not able to directly access Google site without a special http/https proxy.
This means that for anyone (like us) that lives behind a proxy, the build is broken, unless changes are applied in the mock configuration. I'm not sure if it's good to require network access to build a package. This is similar to python code needing to run pip when a rpm is created, or Golang software using "go get". If the package needs something extra to be build, then there is hidden dependency and we need to provide it in a different way. -Erich
Regards, Yong
On 07/11/2018, 10:14 PM, "Bailey, Henry Albert (Al)" <Al.Bailey@wind river.com> wrote:
Do you guys have this commit? https://github.com/openstack/stx-root/commit/1615f281093af91da3b9 98209ff90bbfd0c74350
It flips the networking flag to True
Al
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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@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.storag e.googleapis.com Error: Looks like "https://kubernetes-charts.storage.googleap is.com" is not a valid chart repository or cannot be reached: Get htt ps://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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx- discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-disc uss
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/1615f281093af91da3b998209ff90bb...
It flips the networking flag to True
Al
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
That sounds like a good approach. Al -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Wednesday, November 07, 2018 10:33 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? 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/1615f281093af91da3b998209ff90bb...
It flips the networking flag to True
Al
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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@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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Then this reaises a question, should helm chart creation be a build task (manage by build-pkgs) or a configuration task (managed by config_controller) ? -Erich On Wed, 2018-11-07 at 15:36 +0000, Bailey, Henry Albert (Al) wrote:
That sounds like a good approach. Al
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Wednesday, November 07, 2018 10:33 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build?
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/1615f281093af91da3b998 209ff90bbfd0c74350
It flips the networking flag to True
Al
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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_p roxy_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.m alibran@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.googleapi s.com" is not a valid chart repository or cannot be reached: Get ht tps://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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-d iscuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus s _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus s
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
This review should get people with limited network access building again https://review.openstack.org/#/c/616237 Al -----Original Message----- From: Cordoba Malibran, Erich [mailto:erich.cordoba.malibran@intel.com] Sent: Wednesday, November 07, 2018 11:02 AM To: Little, Scott; Bailey, Henry Albert (Al); starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build? Then this reaises a question, should helm chart creation be a build task (manage by build-pkgs) or a configuration task (managed by config_controller) ? -Erich On Wed, 2018-11-07 at 15:36 +0000, Bailey, Henry Albert (Al) wrote:
That sounds like a good approach. Al
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: Wednesday, November 07, 2018 10:33 AM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Does openstack-helm-infra needs network access to build?
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/1615f281093af91da3b998 209ff90bbfd0c74350
It flips the networking flag to True
Al
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: Tuesday, November 06, 2018 10:50 PM To: Cordoba Malibran, Erich; starlingx-discuss@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_p roxy_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.m alibran@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.googleapi s.com" is not a valid chart repository or cannot be reached: Get ht tps://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@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-d iscuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus s _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discus s
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
participants (4)
-
Bailey, Henry Albert (Al)
-
Cordoba Malibran, Erich
-
Hu, Yong
-
Scott Little