<div dir="ltr">Hi Niels, <br><br>Thanks a lot for the detailed steps. <br>I have recreated the full setup and tried the above steps again, but still it is failing for me. <div>The steps worked for Kaleb as well, but not sure what's wrong with my VM (I tried with 2 VMs) . Thanks Kaleb for your time today. </div><div><br><div>Attached is the steps followed and the output of the error I am getting. If anyone has any pointers, please let me know. </div><div><br></div><div>Regards</div><div>Rinku <br><br><br></div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 13, 2020 at 9:02 PM Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Oct 13, 2020 at 07:23:56PM +0530, Rinku Kothiya wrote:<br>
> Hi Team,<br>
> <br>
> I have been trying to run the following command to fix the centos ci<br>
> nightly builds but Its failing I am not sure what's wrong here.<br>
> Any help would be appreciated.<br>
<br>
For me, the following works:<br>
<br>
$ mkdir centos8-fluster<br>
$ cd centos8-gluster<br>
$ vagrant init centos/8<br>
$ vagrant up<br>
$ cat << EOF | vagrant ssh -c 'sudo sh'<br>
dnf -y update<br>
dnf -y install epel-release<br>
curl <a href="https://termbin.com/sc70j" rel="noreferrer" target="_blank">https://termbin.com/sc70j</a> > nightly-build.sh<br>
export CENTOS_VERSION=8 CENTOS_ARCH=x86_64 GERRIT_BRANCH=master<br>
sh -x nightly-build.sh<br>
EOF<br>
<br>
The <a href="https://termbin.com/sc70j" rel="noreferrer" target="_blank">https://termbin.com/sc70j</a> is a slightly modified version of the<br>
jobs/scripts/nightly-builds/nightly-builds.sh script from the<br>
gluster/centosci repository. It has some adaptions for CentOS-8, which<br>
will need to get merged in a cleaner way into the original script.<br>
<br>
You mentioned over chat that this didn't work for you. So I am wondering<br>
if others have problems with the above steps too.<br>
<br>
The CI environment provides a clean CentOS system for every run. It is<br>
installed with the minimal set of packages, similar to the Vagrant box.<br>
<br>
HTH,<br>
Niels<br>
<br>
<br>
> <br>
> # /usr/bin/mock --root epel-8-x86_64 --with=gnfs --resultdir<br>
> /srv/gluster/nightly/master/8/x86_64 --rebuild<br>
> /root/centosci/glusterfs/glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm<br>
> .<br>
> .<br>
> .<br>
> RPM build errors:<br>
> error: Directory not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster<br>
> error: File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*<br>
> error: File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__<br>
> error: File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils<br>
> Directory not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster<br>
> File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__init__.*<br>
> File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/__pycache__<br>
> File not found:<br>
> /builddir/build/BUILDROOT/glusterfs-20201007.d1d7a6f-0.0.el8.x86_64/gluster/cliutils<br>
> Finish: rpmbuild glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm<br>
> Finish: build phase for glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm<br>
> ERROR:<br>
> Exception(/root/centosci/glusterfs/glusterfs-20201007.d1d7a6f-0.0.autobuild.src.rpm)<br>
> Config(epel-8-x86_64) 6 minutes 19 seconds<br>
> INFO: Results and/or logs in: /srv/gluster/nightly/master/8/x86_64<br>
> INFO: Cleaning up build root ('cleanup_on_failure=True')<br>
> Start: clean chroot<br>
> Finish: clean chroot<br>
> ERROR: Command failed:<br>
> # /usr/bin/systemd-nspawn -q -M e76a1e2f68cc4c88af4159fea2987ad1 -D<br>
> /var/lib/mock/epel-8-x86_64/root -a -u mockbuild --capability=cap_ipc_lock<br>
> --bind=/tmp/mock-resolv.kxdftj8r:/etc/resolv.conf --bind=/dev/loop-control<br>
> --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3<br>
> --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7<br>
> --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11<br>
> --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir<br>
> --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin<br>
> --setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"<br>
> --setenv=PS1=<mock-chroot> \s-\v\$ --setenv=LANG=C.UTF-8 --resolv-conf=off<br>
> bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps<br>
> /builddir/build/SPECS/glusterfs.spec<br>
> <br>
> Regards<br>
> Rinku<br>
> <br>
> On Fri, Oct 9, 2020 at 12:22 PM Niels de Vos <<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>> wrote:<br>
> <br>
> > On Thu, Oct 08, 2020 at 04:21:50PM +0530, Rinku Kothiya wrote:<br>
> > > Hi Niels,<br>
> > ><br>
> > > Yaniv wanted the glusterfs nightly builds generated to be tested for<br>
> > > performance bottlenecks.<br>
> > ><br>
> > > I was working on the below project :<br>
> > > <a href="https://github.com/gluster/gluster-performance-test-suite" rel="noreferrer" target="_blank">https://github.com/gluster/gluster-performance-test-suite</a><br>
> > ><br>
> > > As of now we are running the above script on the glusterfs-nightly builds<br>
> > > every night through a jenkins machine.<br>
> > > Currently we have only been using Glusterfs-EL7 Nightly builds. But for<br>
> > > testing the Gusfterfs-EL8 nightly build, I need those nightly builds to<br>
> > be<br>
> > > generated.<br>
> > > I raised a request with Deepshikha and she said that you have been<br>
> > looking<br>
> > > at it in the past.<br>
> ><br>
> > Please have a look at the Jenkins Jobs Builder scripts from<br>
> > <a href="https://github.com/gluster/centosci/" rel="noreferrer" target="_blank">https://github.com/gluster/centosci/</a> that are used to run these jobs.<br>
> > For the nightly GlusterFS builds, there are two jobs involved:<br>
> ><br>
> > 1. jobs/build-rpms.yml contains the different versions and architectures<br>
> > that the gluster_build-rpms job can build. It needs to be extended to<br>
> > support the `release-8` branch<br>
> ><br>
> > 2. jobs/nightly-rpm-builds.yml does the triggering of the 1st job. It<br>
> > passes parameters to the job, which then will do the builds. Som in<br>
> > order to add a build for GlusterFS-8, inlucde an new `trigger-build`<br>
> > section.<br>
> ><br>
> > 3. jobs/scripts/nightly-builds/nightly-builds.sh is the script that does<br>
> > the actual work. You should be able to execute it manually on a<br>
> > CentOS system (set the environment like the parameters from 2) and<br>
> > see if it works for GlusterFS-8. Ideally the script does not need any<br>
> > changes.<br>
> ><br>
> > You can send a PR with changes that you need, and once it is merged (by<br>
> > Deepshika or one of the other active maintainers), it should<br>
> > automatically get updated in the Jenkins environment, and the next day<br>
> > there should be a new "Gluster 8 Nightly" repository.<br>
> ><br>
> > Adding gluster-devel to CC, as this information should enable others to<br>
> > add or improve CI jobs too.<br>
> ><br>
> > Good luck!<br>
> > Niels<br>
> ><br>
</blockquote></div>