[Starlingx-discuss] build-pkgs: package built failed , mock package missing
This is the result of a daily build exercise from zero as part of our StarlingX/Developer Guide creation: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide One of the things to debug failures during build-pkgs is to find out the failed packages, a "fail" file is created under each package directory: $ find $MY_WORKSPACE/std/results/ -name fail Now we choose one packages from our failing list e.g. .../shim-signed-12-1.tis.2/fail We want to verify the specific build failure for that package but its build.log shows only the Mock Version: $ cat $MY_WORKSPACE/std/results/aarcemor-starlingx-tis-r5-pike-std/build-info-1.0-3.tis/build.log Mock Version: 1.3.4 build-srpm-parallel was successful, we are in build-rpms-parallel stage. One error is common to all packages: 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? And this is reflected also as our exit error when we try to enter the mock shell: $ mock -r $MY_BUILD_CFG --shell ... Installed: ... Dependency Installed: ... ... Complete! Finish: yum install ERROR: Could not find useradd in chroot, maybe the install failed? Then we look for that package, and it is part of shadow-utils $ sudo yum whatprovides \*useradd shadow-utils-4.1.5.1-24.el7.x86_64 $ sudo yum install shadow-utils We look at the content from our mock configuration, the shadow-utils is there: $ echo $MY_BUILD_CFG /localdisk/loadbuild/aarcemor/starlingx/std/configs/aarcemor-starlingx-tis-r5-pike-std/aarcemor-starlingx-tis-r5-pike-std.cfg $ vi $MY_BUILD_CFG config_opts['yum_install_command'] = 'install yum yum-utils shadow-utils distribution-gpg-keys' Looking more into the mock environment, we see no content under /var/lib/mock/. Any help is highly appreciated to debug further.
I'm not observing this. Perhaps a change in the @buildsys-build package group on your system. More inline below ... On 18-06-29 10:17 AM, Arce Moreno, Abraham wrote:
This is the result of a daily build exercise from zero as part of our StarlingX/Developer Guide creation: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
One of the things to debug failures during build-pkgs is to find out the failed packages, a "fail" file is created under each package directory:
$ find $MY_WORKSPACE/std/results/ -name fail
Now we choose one packages from our failing list e.g. .../shim-signed-12-1.tis.2/fail
We want to verify the specific build failure for that package but its build.log shows only the Mock Version:
$ cat $MY_WORKSPACE/std/results/aarcemor-starlingx-tis-r5-pike-std/build-info-1.0-3.tis/build.log Mock Version: 1.3.4
build-srpm-parallel was successful, we are in build-rpms-parallel stage. One error is common to all packages:
13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed?
And this is reflected also as our exit error when we try to enter the mock shell:
$ mock -r $MY_BUILD_CFG --shell [SL] If you are using parallel build, please use the b0 config under the configs directory ... e.g.
export MY_BUILD_ENVIRONMENT=$USER-$PROJECT-$SRC_BUILD_ENVIRONMENT export MY_DEBUG_BUILD_CFG_STD=$MY_WORKSPACE/std/configs/${MY_BUILD_ENVIRONMENT}-std/${MY_BUILD_ENVIRONMENT}-std.b0.cfg mock -r $MY_DEBUG_BUILD_CFG_STD --shell If you find that shadow-utils is still missing, I'd add it to ... $MY_REPO/build-tools/modify-build-cfg ... grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" $FILE || \ echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" >> $FILE ...
... Installed: ... Dependency Installed: ... ... Complete! Finish: yum install ERROR: Could not find useradd in chroot, maybe the install failed?
Then we look for that package, and it is part of shadow-utils
$ sudo yum whatprovides \*useradd shadow-utils-4.1.5.1-24.el7.x86_64 $ sudo yum install shadow-utils
We look at the content from our mock configuration, the shadow-utils is there:
$ echo $MY_BUILD_CFG /localdisk/loadbuild/aarcemor/starlingx/std/configs/aarcemor-starlingx-tis-r5-pike-std/aarcemor-starlingx-tis-r5-pike-std.cfg $ vi $MY_BUILD_CFG config_opts['yum_install_command'] = 'install yum yum-utils shadow-utils distribution-gpg-keys'
Looking more into the mock environment, we see no content under /var/lib/mock/.
Any help is highly appreciated to debug further.
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I'm not observing this. Perhaps a change in the @buildsys-build package group on your system.
More inline below ...
Thanks for your guidance! I am now able to continue with the compilation process, I will debug some time later what are the changes in my setup.
13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed?
And this is reflected also as our exit error when we try to enter the mock shell:
$ mock -r $MY_BUILD_CFG --shell
[SL] If you are using parallel build, please use the b0 config under the configs directory ... e.g.
Confirmed b0 config being used...
If you find that shadow-utils is still missing, I'd add it to ...
$MY_REPO/build-tools/modify-build-cfg
... grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" $FILE || \ echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" >> $FILE ...
I added it as suggested but it continued failing then I search for any other place buildsys-build [0] was used and I find that adding shadow-utils under b0 config made useradd to be installed and let me continue with the compilation process: $ .../ user-starlingx-tis-r5-pike-std.b0.cfg config_opts['rpmbuild_timeout'] = 0 config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils' config_opts['module_install'] = [] [0] https://fedoraproject.org/wiki/Archive:Legacy/Mock?rd=Legacy/Mock
> > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? It looked the local repo failed to be created. please check and assure "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to the mirror. On 30/06/2018, 1:09 PM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: > I'm not observing this. Perhaps a change in the @buildsys-build package group > on your system. > > More inline below ... Thanks for your guidance! I am now able to continue with the compilation process, I will debug some time later what are the changes in my setup. > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed? > > > > And this is reflected also as our exit error when we try to enter the mock shell: > > > > $ mock -r $MY_BUILD_CFG --shell > [SL] If you are using parallel build, please use the b0 config under the configs > directory ... e.g. Confirmed b0 config being used... > If you find that shadow-utils is still missing, I'd add it to ... > > $MY_REPO/build-tools/modify-build-cfg > > ... > grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 > yumshadow-utils'" $FILE || \ > echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 > yumshadow-utils'" >> $FILE ... I added it as suggested but it continued failing then I search for any other place buildsys-build [0] was used and I find that adding shadow-utils under b0 config made useradd to be installed and let me continue with the compilation process: $ .../ user-starlingx-tis-r5-pike-std.b0.cfg config_opts['rpmbuild_timeout'] = 0 config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils' config_opts['module_install'] = [] [0] https://fedoraproject.org/wiki/Archive:Legacy/Mock?rd=Legacy/Mock _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks Yong!
13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed?
It looked the local repo failed to be created. please check and assure "~/cgcs- root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to the mirror.
I have checked comps.xml and it is there, the symbolic links were also updated using our script update_links_from_mirror.sh. Team here in Mexico have started the building only from external sources yesterday. It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch. 2 changes for stx-tools not yet merged to integrate to complete a full external build: - cgcs-centos-repo: https://review.openstack.org/#/c/579709/ - cgcs-dl: https://review.openstack.org/#/c/577953/ Do not hesitate to provide any feedback or modify our wiki as required. Abraham
It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch.
Yeah, we will have someone to do the exercise based on this guide. Pls stay tuned. On 03/07/2018, 8:44 PM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: Thanks Yong! > > > 13:37:39 ERROR: Could not find useradd in chroot, maybe the install > > > failed? > > It looked the local repo failed to be created. please check and assure "~/cgcs- > root/cgcs-centos-repo/Binary/comps.xml" is there, and the sub-dirs in > ""~/cgcs-root/cgcs-centos-repo/Binary/" do exist with correct symbol links to > the mirror. I have checked comps.xml and it is there, the symbolic links were also updated using our script update_links_from_mirror.sh. Team here in Mexico have started the building only from external sources yesterday. It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch. 2 changes for stx-tools not yet merged to integrate to complete a full external build: - cgcs-centos-repo: https://review.openstack.org/#/c/579709/ - cgcs-dl: https://review.openstack.org/#/c/577953/ Do not hesitate to provide any feedback or modify our wiki as required. Abraham
It will be great if someone else could take our Developer Guide https://wiki.openstack.org/wiki/StarlingX/Developer_Guide and build the ISO from scratch.
Yeah, we will have someone to do the exercise based on this guide. Pls stay tuned.
Cool! Thank you!
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you!
Hi Abraham,
Hi Yong!
Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
Only build-pkgs, let me execute with build-pkgs --serial and I will get back to you with my findings and documentation updates.
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
Thanks Zhipeng for your help! Feel free to modify the content as required, please refresh since I wrote some final comments a few minutes ago. For now no more updates from my side. At this point I am able to finally complete all steps except build-iso using the guide. Important Sections/Steps from the guide to double check: - Section 3 Build the CentOS Mirror Repository - Part Setup Repository Docker Container Step 2: "A successful build could depend on the patches to be merged into stx-tools\ make sure you cherry picked them..." - Part Verify Packages "In case there are missing or failed ones due to network instability (or timeout), \ you should download them manually..." - Section 4 Create StarlingX Packages - Part Build Packages "ERROR: Could not find useradd in chroot, maybe the install failed?..." During the build-pkgs process I faced compilation errors due to missing/corrupted packages: 06:18:23 Failed to build packages: tpm-kmod-4.12-0.tis.5.src.rpm spectre-meltdown-checker-0.37+-0.tis.src.rpm \ qemu-kvm-ev-2.10.0-0.tis.0.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm integrity-kmod-4.12-0.tis.5.src.rpm \ cgcs-users-1.0-0.tis.2.src.rpm cgts-mtce-common-1.0-134.tis.src.rpm libvirt-3.5.0-1.tis.2.src.rpm The packages were manually copied to the container to fix some of the above problems were: - tpm-kmod-668a8270.tar.gz - integrity-kmod-668a8270.tar.gz - ibsh-0.3e.tar.gz - ldapscripts-2.0.8.tgz - cppcheck-1.80-1.el7.x86_64.rpm I will filed a bug to track the issues under downloads directory, problem might be a wrong packaging structure. For spectre-meltdown-checker-0.37+-0.tis.src.rpm, please cherry pick the following: - https://review.openstack.org/#/c/580019/ - https://review.openstack.org/#/c/580015/ I will continue with build-iso after zZzZz...
Hi Abraham, I just found, In https://wiki.openstack.org/wiki/StarlingX/Developer_Guide The step 5 of "Download Source Code Repositories" has to be modified due to a patch of stx-manifest.git merged yesterday. https://review.openstack.org/#/c/580170/ Thanks. Yi -----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: Wednesday, July 4, 2018 4:04 PM To: Hu, Yong <yong.hu@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
Hi Yong!
Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
Only build-pkgs, let me execute with build-pkgs --serial and I will get back to you with my findings and documentation updates.
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
Thanks Zhipeng for your help! Feel free to modify the content as required, please refresh since I wrote some final comments a few minutes ago. For now no more updates from my side. At this point I am able to finally complete all steps except build-iso using the guide. Important Sections/Steps from the guide to double check: - Section 3 Build the CentOS Mirror Repository - Part Setup Repository Docker Container Step 2: "A successful build could depend on the patches to be merged into stx-tools\ make sure you cherry picked them..." - Part Verify Packages "In case there are missing or failed ones due to network instability (or timeout), \ you should download them manually..." - Section 4 Create StarlingX Packages - Part Build Packages "ERROR: Could not find useradd in chroot, maybe the install failed?..." During the build-pkgs process I faced compilation errors due to missing/corrupted packages: 06:18:23 Failed to build packages: tpm-kmod-4.12-0.tis.5.src.rpm spectre-meltdown-checker-0.37+-0.tis.src.rpm \ qemu-kvm-ev-2.10.0-0.tis.0.src.rpm ldapscripts-2.0.8-0.tis.2.src.rpm integrity-kmod-4.12-0.tis.5.src.rpm \ cgcs-users-1.0-0.tis.2.src.rpm cgts-mtce-common-1.0-134.tis.src.rpm libvirt-3.5.0-1.tis.2.src.rpm The packages were manually copied to the container to fix some of the above problems were: - tpm-kmod-668a8270.tar.gz - integrity-kmod-668a8270.tar.gz - ibsh-0.3e.tar.gz - ldapscripts-2.0.8.tgz - cppcheck-1.80-1.el7.x86_64.rpm I will filed a bug to track the issues under downloads directory, problem might be a wrong packaging structure. For spectre-meltdown-checker-0.37+-0.tis.src.rpm, please cherry pick the following: - https://review.openstack.org/#/c/580019/ - https://review.openstack.org/#/c/580015/ I will continue with build-iso after zZzZz... _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
I just found, In https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
The step 5 of "Download Source Code Repositories" has to be modified due to a patch of stx-manifest.git merged yesterday. https://review.openstack.org/#/c/580170/
Thanks Yi! Changes has been made to https://wiki.openstack.org/wiki/StarlingX/Developer_Guide ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
build-pkgs will by default run in parallel mode. This means two things, a different build order than the serial build, and the possibility that earlier packages built in a different mock environment. It likely works in a serial build because an earlier package has a "Require: X" where X is shadow-utils or something that depends on shadow-utils. Since we reuse the mock environment rather than clearing it after each package (faster builds), the shadow-utils package is available for later packages and might allow then to get away with a missing dependency. The real solution is to add 'Requires: shadow-utils' to the spec file of the package that breaks. Adding it via modify-build-cfg was based on the theory (unconfirmed) that @buildsys-build macro has been redefined on newer CentOS systems and shadow-utils has been dropped from the set of packages that @buildsys-build maps to. It seems like a quicker way to enable folks, rather than adding 'Requires: shadow-utils' to potemtially a lot of packages. Scott On 18-07-04 03:15 AM, Hu, Yong wrote:
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
build-pkgs will by default run in parallel mode. This means two things, a different build order than the serial build, and the possibility that earlier packages built in a different mock environment. It likely works in a serial build because an earlier package has a "Require: X" where X is shadow-utils or something that depends on shadow-utils. Since we reuse the mock environment rather than clearing it after each package (faster builds), the shadow-utils package is available for later packages and might allow then to get away with a missing dependency.
The real solution is to add 'Requires: shadow-utils' to the spec file of the package that breaks.
In one round of compilation I saw more than 20 packages failing due to this missing shadow-utils dependency so several changes might be required. Let me add some other packages are failing due to another missing dependency: rpm-build. Only 2 for now so far seen in my setup.
Adding it via modify-build-cfg was based on the theory (unconfirmed) that @buildsys-build macro has been redefined on newer CentOS systems and shadow-utils has been dropped from the set of packages that @buildsys-build maps to. It seems like a quicker way to enable folks, rather than adding 'Requires: shadow-utils' to potemtially a lot of packages.
Agree! Since we are reusing this mock environment, I am in favor to add via modify-build-cfg.
Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Abraham, One more comment to this guide: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide We might have to add a session to update initial images, *if kernel or device modules are modified*. Here are steps: 1). Run command: $ update-pxe-network-installer After this is done, there should be 3 new files (vmlinuz, initrd.img and squashfs.img) generated in: $BUILD_FOLDER/pxe-network-installer/output 2). copy these 3 files into mirror “/import/mirrors/CentOS/tis-installer/” and put appropriate postfix. Note, the new info (images with the postfix) need to updated accordingly in in “build_srpm.data” and “pxe-network-installer.spec” under “cgcs-root/addons/wr-cgcs/layers/cgcs/mwa-beas/installer/pxe-network-installer/centos/” 3). re-build pkgs and iso: (no need to make a clean build) On 05/07/2018, 11:14 AM, "Liu, ZhipengS" <zhipengs.liu@intel.com> wrote: Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks Yong!
One more comment to this guide: https://wiki.openstack.org/wiki/StarlingX/Developer_Guide We might have to add a session to update initial images, *if kernel or device modules are modified*.
In you experience, how would we identify this "update initial images" is required? Are we having a specific error saying the image is not found and take it as a trigger? Can we make this a default process to follow? We have the following steps under the same guide, are they still meaningful? Should they be replaced by the steps you have shared? Mirror Binaries $ mkdir -p $HOME/starlingx/mirror/CentOS/tis-installer $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/initrd.img $HOME/starlingx/mirror/CentOS/tis-installer/initrd.img-stx-0.2 $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/images/pxeboot/vmlinuz $HOME/starlingx/mirror/CentOS/tis-installer/vmlinuz-stx-0.2 $ cp $HOME/starlingx/mirror/CentOS/stx-r1/CentOS/pike/Binary/LiveOS/squashfs.img $HOME/starlingx/mirror/CentOS/tis-installer/squashfs.img-stx-0.2
Here are steps: 1). Run command: $ update-pxe-network-installer After this is done, there should be 3 new files (vmlinuz, initrd.img and squashfs.img) generated in: $BUILD_FOLDER/pxe-network-installer/output 2). copy these 3 files into mirror “/import/mirrors/CentOS/tis-installer/” and put appropriate postfix. Note, the new info (images with the postfix) need to updated accordingly in in “build_srpm.data” and “pxe-network- installer.spec” under “cgcs-root/addons/wr-cgcs/layers/cgcs/mwa- beas/installer/pxe-network-installer/centos/” 3). re-build pkgs and iso: (no need to make a clean build)
These are our building steps: $ cd $MY_WORKSPACE $ build-pkgs --serial $ generate-cgcs-tis-repo $ build-srpms --installer $ build-rpms --installer $ build-iso Where do you suggest we add the "update initial images" process?
Hi Abraham, When I followed your guide, there are 3 issues I found. 1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. 2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/ 3) lighttpd not started by default in build container, and also could not started manually. =============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker -----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: > > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned. Cool! Thank you! _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks Little！ We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little！ We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ 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
Thanks Mingyuan! Some RPM exactly missing. Hi Abraham, We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ======================================== Thanks! Zhipeng -----Original Message----- From: Qi, Mingyuan Sent: 2018年7月12日 14:38 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little！ We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ 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 Scott and Abraham, After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally. 23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. 23:40:14 Will try to build again (if some other package will succeed). 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... 23:40:18 Start: init plugins 23:40:18 INFO: selinux disabled 23:40:18 Finish: init plugins 23:40:18 Start: run 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) BRs zhipeng -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月12日 21:33 To: Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Mingyuan! Some RPM exactly missing. Hi Abraham, We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ======================================== Thanks! Zhipeng -----Original Message----- From: Qi, Mingyuan Sent: 2018年7月12日 14:38 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? Thanks, Mingyuan -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Thanks Little！ We also found it should be OK that sed used later yesterday. Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found Zhipeng -----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing You shouldn't have to do that. The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. Scott On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ 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
For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote:
Hi Scott and Abraham,
After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally.
23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. 23:40:14 Will try to build again (if some other package will succeed). 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... 23:40:18 Start: init plugins 23:40:18 INFO: selinux disabled 23:40:18 Finish: init plugins 23:40:18 Start: run 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock)
BRs zhipeng
-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月12日 21:33 To: Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Thanks Mingyuan! Some RPM exactly missing.
Hi Abraham,
We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ========================================
Thanks! Zhipeng
-----Original Message----- From: Qi, Mingyuan Sent: 2018年7月12日 14:38 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Zhipeng,
The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded?
Thanks, Mingyuan
-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 12, 2018 9:45 To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Thanks Little！ We also found it should be OK that sed used later yesterday.
Before we changed this place, we could not build any RPM. It always gave out errors like below 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) 15:13:50 Requires: /usr/bin/python 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) 15:13:50 Requires: libsoftokn3.so()(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1()(64bit) 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libcom_err.so.2()(64bit) 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........
After changed this place, no this issue found anymore, but another error we saw all the time. 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Zhipeng
-----Original Message----- From: Scott Little [mailto:scott.little@windriver.com] Sent: 2018年7月11日 23:49 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
You shouldn't have to do that.
The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO.
There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs.
Scott
On 18-07-11 04:14 AM, Liu, ZhipengS wrote:
Hi Abraham,
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis-Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
BRs zhipeng -----Original Message----- From: Liu, ZhipengS Sent: 2018年7月5日 11:14 To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham,
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
-----Original Message----- From: Hu, Yong [mailto:yong.hu@intel.com] Sent: 2018年7月4日 15:15 To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Hi Abraham, Did you run "build-pkgs" or "build-pkgs --serial"? If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. 13:42:03 Failed to build packages: memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm python-2.7.5-58.el7.tis.3.src.rpm
In the meantime, @Zhipeng is following steps in https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote:
> > > > It will be great if someone else could take our Developer Guide > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide > > > > and build the ISO from scratch. > > Yeah, we will have someone to do the exercise based on this guide. Pls stay > tuned.
Cool! Thank you!
_______________________________________________ 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
Zhipeng, It looks the local repo in your build environment is not correct. You can check if "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" exists. If no, you need to recreate "cgcs-centos-repo" with the latest version of "stx-tools/toCOPY/generate-cgcs-centos-repo.sh" to assure: 1. the folder structure in "~/cgcs-root/cgcs-centos-repo/Binary/" is correct 2. "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" does exist Regards, Yong On 12/07/2018, 8:36 AM, "Scott Little" <scott.little@windriver.com> wrote: For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote: > Hi Scott and Abraham, > > After I add missing RPMS, build still failed as below. However, with the mirror I built, > the build in our old build environment is ongoing normally. > > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm > 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. > 23:40:14 Will try to build again (if some other package will succeed). > 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... > 23:40:18 Start: init plugins > 23:40:18 INFO: selinux disabled > 23:40:18 Finish: init plugins > 23:40:18 Start: run > 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) > > BRs > zhipeng > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] > Sent: 2018年7月12日 21:33 > To: Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Mingyuan! > Some RPM exactly missing. > > Hi Abraham, > > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== > > Thanks! > Zhipeng > > -----Original Message----- > From: Qi, Mingyuan > Sent: 2018年7月12日 14:38 > To: Liu, ZhipengS <zhipengs.liu@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Zhipeng, > > The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. > Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? > > Thanks, > Mingyuan > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] > Sent: Thursday, July 12, 2018 9:45 > To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Little！ > We also found it should be OK that sed used later yesterday. > > Before we changed this place, we could not build any RPM. > It always gave out errors like below > 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) > 15:13:50 Requires: /usr/bin/python > 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libsoftokn3.so()(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1()(64bit) > 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libcom_err.so.2()(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ > > After changed this place, no this issue found anymore, but another error we saw all the time. > 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. > 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > > Zhipeng > > -----Original Message----- > From: Scott Little [mailto:scott.little@windriver.com] > Sent: 2018年7月11日 23:49 > To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > You shouldn't have to do that. > > The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. > > There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. > > Scott > > > On 18-07-11 04:14 AM, Liu, ZhipengS wrote: >> Hi Abraham, >> >> When I followed your guide, there are 3 issues I found. >> >> 1) We need change mock.cfg.proto file as below [TisCentos7Distro] >> name=Tis-Centos-7-Distro >> enabled=1 >> baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary >> // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. >> >> 2) In Download Source Code Repositories step of the guide. >> cgcs-dl >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads >> // change to >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/stx/ >> >> 3) lighttpd not started by default in build container, and also could not started manually. >> >> =============================================================== >> Raised below 2 stories. >> 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto >> 2002938 lighttpd not started by default in build container >> >> >> BRs >> zhipeng >> -----Original Message----- >> From: Liu, ZhipengS >> Sent: 2018年7月5日 11:14 >> To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham >> <abraham.arce.moreno@intel.com>; Scott Little >> <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io >> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> >> When I run below step >> $ docker build -t user:centos-mirror-repository -f Dockerfile . >> It mentioned >> Get https://registry-1.docker.io/v2/: net/http: request canceled while >> waiting for connection >> >> It can work after following below steps. >> =========================================================== >> Here is a link to the official docker doc for proxy >> http:https://docs.docker.com/engine/admin/systemd/#http-proxy >> A quick outline: >> First, create a systemd drop-in directory for the docker service: >> mkdir /etc/systemd/system/docker.service.d >> Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: >> [Service] >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" >> Flush changes: >> $ sudo systemctl daemon-reload >> Verify that the configuration has been loaded: >> $ sudo systemctl show --property Environment docker >> Environment=HTTP_PROXY=http://proxy.example.com:80/ >> Restart Docker: >> $ sudo systemctl restart docker >> >> -----Original Message----- >> From: Hu, Yong [mailto:yong.hu@intel.com] >> Sent: 2018年7月4日 15:15 >> To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little >> <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> Did you run "build-pkgs" or "build-pkgs --serial"? >> If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. >> 13:42:03 Failed to build packages: >> memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm >> python-2.7.5-58.el7.tis.3.src.rpm >> >> In the meantime, @Zhipeng is following steps in >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> >> On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: >> >> > > > > It will be great if someone else could take our Developer Guide >> > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> > > > > and build the ISO from scratch. >> > >> > Yeah, we will have someone to do the exercise based on this guide. Pls stay >> > tuned. >> >> Cool! Thank you! >> >> >> _______________________________________________ >> 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
Hi Yong and Abraham Mingyuan asked me checked comps.xml yesterday, it didn't exist. I also could not create it through executing generate-cgcs-centos-repo.sh. Zhipeng -----Original Message----- From: Hu, Yong Sent: 2018年7月12日 23:47 To: Scott Little <scott.little@windriver.com>; Liu, ZhipengS <zhipengs.liu@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Zhipeng, It looks the local repo in your build environment is not correct. You can check if "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" exists. If no, you need to recreate "cgcs-centos-repo" with the latest version of "stx-tools/toCOPY/generate-cgcs-centos-repo.sh" to assure: 1. the folder structure in "~/cgcs-root/cgcs-centos-repo/Binary/" is correct 2. "~/cgcs-root/cgcs-centos-repo/Binary/comps.xml" does exist Regards, Yong On 12/07/2018, 8:36 AM, "Scott Little" <scott.little@windriver.com> wrote: For more details, examine the log files in this directory ... /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis/ On 18-07-12 11:13 AM, Liu, ZhipengS wrote: > Hi Scott and Abraham, > > After I add missing RPMS, build still failed as below. However, with the mirror I built, > the build in our old build environment is ongoing normally. > > 23:40:14 Start: chroot init > 23:40:14 INFO: calling preinit hooks > 23:40:14 INFO: enabled root cache > 23:40:14 INFO: enabled yum cache > 23:40:14 Start: cleaning yum metadata > 23:40:14 Finish: cleaning yum metadata > 23:40:14 INFO: enabled HW Info plugin > 23:40:14 Mock Version: 1.4.11 > 23:40:14 INFO: Mock Version: 1.4.11 > 23:40:14 Start: yum install > 23:40:14 Finish: yum install > 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds > 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5-pike-std/tis-extensions-1.0-2.tis > 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? > 23:40:14 End build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis-extensions-1.0-2.tis.src.rpm > 23:40:14 Error building tis-extensions-1.0-2.tis.src.rpm. > 23:40:14 Will try to build again (if some other package will succeed). > 23:40:14 Start build: /localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:14 building tpm2-openssl-engine-1.0-2.tis.src.rpm > 23:40:18 INFO: mock.py version 1.4.11 starting (python version = 2.7.5)... > 23:40:18 Start: init plugins > 23:40:18 INFO: selinux disabled > 23:40:18 Finish: init plugins > 23:40:18 Start: run > 23:40:18 INFO: Start(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tpm2-openssl-engine-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) > > BRs > zhipeng > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] > Sent: 2018年7月12日 21:33 > To: Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Mingyuan! > Some RPM exactly missing. > > Hi Abraham, > > We'd better add > 3rd-centos_rpms_missing_L1.txt to below as well > ======================================== > Verify Packages > 1.Verify there are no missing or failed packages: > # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt > ======================================== > > Thanks! > Zhipeng > > -----Original Message----- > From: Qi, Mingyuan > Sent: 2018年7月12日 14:38 > To: Liu, ZhipengS <zhipengs.liu@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Zhipeng, > > The failure is due to your mirror package missing, such as python, nss-softokn3... so that mock init failed at the beginning. > Could you check whether packages in rpms_from_centos_3rd_parties.lst are totally downloaded? > > Thanks, > Mingyuan > > > -----Original Message----- > From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] > Sent: Thursday, July 12, 2018 9:45 > To: Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > Thanks Little！ > We also found it should be OK that sed used later yesterday. > > Before we changed this place, we could not build any RPM. > It always gave out errors like below > 15:13:50 Error: Package: python-urlgrabber-3.10-8.el7.noarch (TisCentos7Distro) > 15:13:50 Requires: /usr/bin/python > 15:13:50 Error: Package: nss-3.28.4-1.2.el7_3.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libsoftokn3.so()(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libfreebl3.so(NSSRAWHASH_3.12.3)(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1()(64bit) > 15:13:50 Error: Package: krb5-libs-1.15.1-19.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libcom_err.so.2()(64bit) > 15:13:50 Error: Package: rpm-libs-4.11.3-32.el7.x86_64 (TisCentos7Distro) > 15:13:50 Requires: libelf.so.1(ELFUTILS_1.0)(64bit) > 15:13:50 Error: Package: glibc-2.17-222.el7.x86_64 (TisCentos7Distro) ........ > > After changed this place, no this issue found anymore, but another error we saw all the time. > 19:30:45 failure: repodata/repomd.xml from TisCentos7Distro: [Errno 256] No more mirrors to try. > 19:30:45 http://127.0.0.1:8088/MY_REPO/cgcs-centos-repo/Binary/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found > > Zhipeng > > -----Original Message----- > From: Scott Little [mailto:scott.little@windriver.com] > Sent: 2018年7月11日 23:49 > To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> > Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing > > You shouldn't have to do that. > > The mock.cfg.proto file is processed by the modify-build-cfg script. You should see it using sed to substitute "MY_REPO_DIR" with $MY_REPO. > > There might be weaknesses elsewhere in the build process where it attempts to determine if modify-build-cfg should be re-run. e.g. I don't think we test for changes to environment variables between runs. > > Scott > > > On 18-07-11 04:14 AM, Liu, ZhipengS wrote: >> Hi Abraham, >> >> When I followed your guide, there are 3 issues I found. >> >> 1) We need change mock.cfg.proto file as below [TisCentos7Distro] >> name=Tis-Centos-7-Distro >> enabled=1 >> baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary >> // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found. >> >> 2) In Download Source Code Repositories step of the guide. >> cgcs-dl >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads >> // change to >> $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ >> $MY_REPO/stx/ >> >> 3) lighttpd not started by default in build container, and also could not started manually. >> >> =============================================================== >> Raised below 2 stories. >> 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto >> 2002938 lighttpd not started by default in build container >> >> >> BRs >> zhipeng >> -----Original Message----- >> From: Liu, ZhipengS >> Sent: 2018年7月5日 11:14 >> To: Hu, Yong <yong.hu@intel.com>; Arce Moreno, Abraham >> <abraham.arce.moreno@intel.com>; Scott Little >> <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io >> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> >> When I run below step >> $ docker build -t user:centos-mirror-repository -f Dockerfile . >> It mentioned >> Get https://registry-1.docker.io/v2/: net/http: request canceled while >> waiting for connection >> >> It can work after following below steps. >> =========================================================== >> Here is a link to the official docker doc for proxy >> http:https://docs.docker.com/engine/admin/systemd/#http-proxy >> A quick outline: >> First, create a systemd drop-in directory for the docker service: >> mkdir /etc/systemd/system/docker.service.d >> Now create a file called /etc/systemd/system/docker.service.d/http-proxy.conf that adds the HTTP_PROXY environment variable: >> [Service] >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: >> Environment="HTTP_PROXY=http://proxy.example.com:80/" >> Environment="NO_PROXY=localhost,127.0.0.0/8,docker-registry.somecorporation.com" >> Flush changes: >> $ sudo systemctl daemon-reload >> Verify that the configuration has been loaded: >> $ sudo systemctl show --property Environment docker >> Environment=HTTP_PROXY=http://proxy.example.com:80/ >> Restart Docker: >> $ sudo systemctl restart docker >> >> -----Original Message----- >> From: Hu, Yong [mailto:yong.hu@intel.com] >> Sent: 2018年7月4日 15:15 >> To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Scott Little >> <scott.little@windriver.com>; starlingx-discuss@lists.starlingx.io >> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , >> mock package missing >> >> Hi Abraham, >> Did you run "build-pkgs" or "build-pkgs --serial"? >> If I run "run-pkgs" (parallel mode) I saw the similar errors as you did, but if using "-- serial" the build went smoothly and further, except for failures on following 3 packages, which is known issue. >> 13:42:03 Failed to build packages: >> memcached-1.4.39-1.el7.tis.1.src.rpm kubernetes-1.10.0-1.tis.1.src.rpm >> python-2.7.5-58.el7.tis.3.src.rpm >> >> In the meantime, @Zhipeng is following steps in >> https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> >> On 04/07/2018, 7:02 AM, "Arce Moreno, Abraham" <abraham.arce.moreno@intel.com> wrote: >> >> > > > > It will be great if someone else could take our Developer Guide >> > > > > https://wiki.openstack.org/wiki/StarlingX/Developer_Guide >> > > > > and build the ISO from scratch. >> > >> > Yeah, we will have someone to do the exercise based on this guide. Pls stay >> > tuned. >> >> Cool! Thank you! >> >> >> _______________________________________________ >> 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
Mingyuan asked me checked comps.xml yesterday, it didn't exist. I also could not create it through executing generate-cgcs-centos-repo.sh.
Thanks Zhipeng, Mingyuan, Understood about the problem. Yong and Erich were talking a few days ago internally about the way to handle comps.xml and they suggested a minimal xml so time to bring this conversation out. How about this first version [0]? If it is possible for you to test and see if we can start taking this as our base file. [0] https://pastebin.com/KMB8QLNX
Mingyuan asked me checked comps.xml yesterday, it didn't exist. I also could not create it through executing generate-cgcs-centos-repo.sh.
Thanks Zhipeng, Mingyuan,
Understood about the problem. Yong and Erich were talking a few days ago internally about the way to handle comps.xml and they suggested a minimal xml so time to bring this conversation out.
How about this first version [0]? If it is possible for you to test and see if we can start taking this as our base file.
Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445
Hi Abraham, I have tried your comps.xml, it can work! Now I have finished all build except iso building Thanks! zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月18日 11:23 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Hu, Yong <yong.hu@intel.com>; 'Scott Little' <scott.little@windriver.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing
Mingyuan asked me checked comps.xml yesterday, it didn't exist. I also could not create it through executing generate-cgcs-centos-repo.sh.
Thanks Zhipeng, Mingyuan,
Understood about the problem. Yong and Erich were talking a few days ago internally about the way to handle comps.xml and they suggested a minimal xml so time to bring this conversation out.
How about this first version [0]? If it is possible for you to test and see if we can start taking this as our base file.
Review submitted: "Add minimal comps.xml file into cgcs-centos generator" https://review.openstack.org/#/c/583445
Hi ZhipengS,
After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally.
Important to get your feedback on the activities asked to be executed by Scott and Yong.
23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/tis- extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx-tis-r5- pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build:
You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE
Hi Araham, I changed modify-build-cfg according to your below solution, below issue fixed
23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? Now, RPM build is ongoing normally, and I can see some "Success building".
Thank you so much! BRs zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月13日 9:40 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi ZhipengS,
After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally.
Important to get your feedback on the activities asked to be executed by Scott and Yong.
23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/t is- extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx -tis-r5- pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build:
You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE
Hi, Has a fix been pushed to the repo for this ? Thanks, Brent -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 12, 2018 10:35 PM To: Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Little, Scott <Scott.Little@windriver.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi Araham, I changed modify-build-cfg according to your below solution, below issue fixed
23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? Now, RPM build is ongoing normally, and I can see some "Success building".
Thank you so much! BRs zhipeng -----Original Message----- From: Arce Moreno, Abraham Sent: 2018年7月13日 9:40 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Qi, Mingyuan <mingyuan.qi@intel.com>; Scott Little <scott.little@windriver.com>; Hu, Yong <yong.hu@intel.com>; 'starlingx-discuss@lists.starlingx.io' <starlingx-discuss@lists.starlingx.io> Subject: RE: [Starlingx-discuss] build-pkgs: package built failed , mock package missing Hi ZhipengS,
After I add missing RPMS, build still failed as below. However, with the mirror I built, the build in our old build environment is ongoing normally.
Important to get your feedback on the activities asked to be executed by Scott and Yong.
23:40:14 Start: chroot init 23:40:14 INFO: calling preinit hooks 23:40:14 INFO: enabled root cache 23:40:14 INFO: enabled yum cache 23:40:14 Start: cleaning yum metadata 23:40:14 Finish: cleaning yum metadata 23:40:14 INFO: enabled HW Info plugin 23:40:14 Mock Version: 1.4.11 23:40:14 INFO: Mock Version: 1.4.11 23:40:14 Start: yum install 23:40:14 Finish: yum install 23:40:14 ERROR: Exception(/localdisk/loadbuild/zhipengl/starlingx/std/rpmbuild/SRPMS/t is- extensions-1.0-2.tis.src.rpm) Config(zhipengl-starlingx-tis-r5-pike-std/mock) 0 minutes 2 seconds 23:40:14 INFO: Results and/or logs in: /localdisk/loadbuild/zhipengl/starlingx/std/results/zhipengl-starlingx -tis-r5- pike-std/tis-extensions-1.0-2.tis 23:40:14 ERROR: Could not find useradd in chroot, maybe the install failed? 23:40:14 End build:
You are hitting " ERROR: Could not find useradd in chroot, maybe the install failed?" Information is spread among the different messages under thread: "[Starlingx-discuss] build-pkgs: package built failed , mock package missing" http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000125.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000129.html http://lists.starlingx.io/pipermail/starlingx-discuss/2018-July/000206.html In summary, to pass this and other dependency issue during build-pkgs is by adding - shadow-utils - rpm-build to modify-build-cfg under build-tools diff --git a/build-tools/modify-build-cfg b/build-tools/modify-build-cfg ... -grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ - echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum'" >> $FILE +grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" $FILE || \ + echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build'" >> $FILE _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Thanks again ZhipengS!
We'd better add 3rd-centos_rpms_missing_L1.txt to below as well ======================================== Verify Packages 1.Verify there are no missing or failed packages: # cat output/3rd_rpms_missing_L1.txt output/3rd_srpms_missing_L1.txt output/centos_rpms_missing_L1.txt output/centos_srpms_missing_L1.txt ========================================
Added! https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Verify_Packages
Thanks ZhipengS!
When I followed your guide, there are 3 issues I found.
1) We need change mock.cfg.proto file as below [TisCentos7Distro] name=Tis- Centos-7-Distro enabled=1 baseurl=LOCAL_BASE/MY_REPO_DIR/cgcs-centos-repo/Binary // change MY_REPO_DIR to MY_REPO, No MY_REPO_DIR found.
Scott's reply annotated. On hold, waiting for more comments. https://storyboard.openstack.org/#!/story/2002939
2) In Download Source Code Repositories step of the guide. cgcs-dl $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/addons/wr-cgcs/layers/cgcs/downloads // change to $ ln -s /import/mirrors/CentOS/stx-r1/CentOS/pike/downloads/ $MY_REPO/stx/
Done! https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Download_Source_Co...
3) lighttpd not started by default in build container, and also could not started manually.
=============================================================== Raised below 2 stories. 2002939 The url of TisCentos7Distro is wrong in mock.cfg.proto 2002938 lighttpd not started by default in build container
Thanks ZhipengS!
When I run below step $ docker build -t user:centos-mirror-repository -f Dockerfile . It mentioned Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection
It can work after following below steps. =========================================================== Here is a link to the official docker doc for proxy http:https://docs.docker.com/engine/admin/systemd/#http-proxy A quick outline: First, create a systemd drop-in directory for the docker service: mkdir /etc/systemd/system/docker.service.d Now create a file called /etc/systemd/system/docker.service.d/http- proxy.conf that adds the HTTP_PROXY environment variable: [Service] Environment="HTTP_PROXY=http://proxy.example.com:80/" If you have internal Docker registries that you need to contact without proxying you can specify them via the NO_PROXY environment variable: Environment="HTTP_PROXY=http://proxy.example.com:80/" Environment="NO_PROXY=localhost,127.0.0.0/8,docker- registry.somecorporation.com" Flush changes: $ sudo systemctl daemon-reload Verify that the configuration has been loaded: $ sudo systemctl show --property Environment docker Environment=HTTP_PROXY=http://proxy.example.com:80/ Restart Docker: $ sudo systemctl restart docker
I have add the url for this, your post, as a reference under https://wiki.openstack.org/wiki/StarlingX/Developer_Guide#Software_Requireme... We will leave the hard work to change references using best tech writing guidelines to our experts.
Did I actually post 'yumshadow-utils' ? That should read 'shadow-utils'. Scott On 18-06-30 01:08 AM, Arce Moreno, Abraham wrote:
I'm not observing this. Perhaps a change in the @buildsys-build package group on your system.
More inline below ... Thanks for your guidance! I am now able to continue with the compilation process, I will debug some time later what are the changes in my setup.
13:37:39 ERROR: Could not find useradd in chroot, maybe the install failed?
And this is reflected also as our exit error when we try to enter the mock shell:
$ mock -r $MY_BUILD_CFG --shell
[SL] If you are using parallel build, please use the b0 config under the configs directory ... e.g. Confirmed b0 config being used...
If you find that shadow-utils is still missing, I'd add it to ...
$MY_REPO/build-tools/modify-build-cfg
... grep -q "config_opts\['chroot_setup_cmd'\] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" $FILE || \ echo "config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yumshadow-utils'" >> $FILE ... I added it as suggested but it continued failing then I search for any other place buildsys-build [0] was used and I find that adding shadow-utils under b0 config made useradd to be installed and let me continue with the compilation process:
$ .../ user-starlingx-tis-r5-pike-std.b0.cfg config_opts['rpmbuild_timeout'] = 0 config_opts['chroot_setup_cmd'] = 'install @buildsys-build pigz lbzip2 yum shadow-utils' config_opts['module_install'] = []
[0] https://fedoraproject.org/wiki/Archive:Legacy/Mock?rd=Legacy/Mock
Did I actually post 'yumshadow-utils' ? That should read 'shadow-utils'.
No issues. So far this " ERROR: Could not find useradd in chroot, maybe the install failed? " is seen in 2 different setups started from scratch, looking more into the source code this ['chroot_setup_cmd'] is found in 2 files: - build-tools/build_minimal_iso/build.cfg - build-tools/modify-build-cfg How possible is it we can add the "required" packages into "modify-build-cfg"? Iso building differ but have them including 'shadow-utils'. Adding them under "modify-build-cfg" allowed me to continue running the build-pkgs and get rid of the problem. Any other cleaner way? Complete repo grep output: [user@8848c894bb36 cgcs-root]$ repo grep buildsys-build cgcs-root/build-tools/build_minimal_iso/build.cfg:config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build' cgcs-root/build-tools/build_minimal_iso/build.cfg:config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build pigz lbzip2 yum shadow-utils rpm-build lbzip2 gcc glibc-headers make gcc-c++ java-devel' cgcs-root/build-tools/modify-build-cfg:grep -q "config_opts\['chroot_setup_cmd'\] = \ 'install @buildsys-build pigz lbzip2 yum'" $FILE || \ cgcs-root/build-tools/modify-build-cfg: echo "config_opts['chroot_setup_cmd'] = \ 'install @buildsys-build pigz lbzip2 yum'" >> $FILE
participants (7)
-
Arce Moreno, Abraham
-
Hu, Yong
-
Liu, ZhipengS
-
Qi, Mingyuan
-
Rowsell, Brent
-
Scott Little
-
Wang, Yi C