gluster / project-infrastructure

Issues related to GlusterFs infrastructure components.
0 stars 0 forks source link

devrpm-el7 and devrpm-fedora smoke tests are failing #187

Open Shwetha-Acharya opened 11 months ago

Shwetha-Acharya commented 11 months ago

devrpm-el7 and devrpm-fedora smoke tests are failing with the following error message:

15:30:41 rpmbuild --define '_topdir /home/jenkins/root/workspace/gh_devrpm-el7/extras/LinuxRPM/rpmbuild' -bs rpmbuild/SPECS/glusterfs.spec 15:30:42 Wrote: /home/jenkins/root/workspace/gh_devrpm-el7/extras/LinuxRPM/rpmbuild/SRPMS/glusterfs-2023.10.03-0.09.5959.el7.src.rpm 15:30:42 mv rpmbuild/SRPMS/* . 15:30:42 ERROR: Could not find required config file: /etc/mock/{build_flag}.cfg 15:30:42 ERROR: If you're trying to specify a path, include the .cfg extension, e.g. -r ./target.cfg

As these are the "Required" tests, merging of PRs are blocked and the release activity is affected.

@mscherer @rakshithakamath94

mscherer commented 11 months ago

@rakshithakamath94 looked at the issue, and we noticed that 1) the builder were reinstalled on the wrong version. Some change in ansible that triggered some variable priority change, and the automation dutifully executed.

Now, that was fixed, the problem seems to be on jenkins-update, as it doesn't replace {build_flag} in the script as before.

mscherer commented 11 months ago

I suspect it come from https://github.com/gluster/build-jobs/commit/891c0b70b385f25d3d2b293da2df7b3c2dae9ca7

mscherer commented 11 months ago

@rakshithakamath94 you remember why this was changed ? Is it ok if I revert the change partially ?

rakshithakamath94 commented 11 months ago

Hi @mscherer ,

When I noticed that the job was failing I made some manual changes to see if I can fix them. You can revert the changes, sorry I forgot to revert them :D

rakshithakamath94 commented 11 months ago

Actually when I saw the parameter {build_flag} not getting the value, I searched the job's definition to see if I can get it. I am glad that you fixed it.

mscherer commented 11 months ago

Mhh, but I fixed nothing, the job is still failling. Do you remember why the job use include-raw-escape ?

rakshithakamath94 commented 11 months ago

I don't remember exactly. But it's introducing extra set of brackets now isn't it? As in, ${some_variable} is now getting created as ${{some_variable}} right

mscherer commented 11 months ago

Yup. I guess I can revert on that job, it can't break it more than now.

mscherer commented 11 months ago

So that change nothing. I suspect a change on jjb that trigger the problem, but maybe I didn't fix it right.

mscherer commented 11 months ago

Ok so I just forgot to merge the PR. I had to debug the whole build of jjb to figure out the issue.

Shwetha-Acharya commented 10 months ago

@mscherer is the issue fixed now? Please update when fixed, so that I can re trigger the smoke runs

mscherer commented 10 months ago

I think it sopuld work. Sorry, I didn't looked at my github notifications