Re: [Starlingx-discuss] build-pkgs: package built failed , mock package missing

12 Jul 2018

      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