#7787 Intermittent build failures due to git clone failure
Opened a month ago by mbooth. Modified 13 days ago

Two of my modular RPM builds failed today so far:

https://koji.fedoraproject.org/koji/taskinfo?taskID=34828402
https://koji.fedoraproject.org/koji/taskinfo?taskID=34828404

This is an example of the error reported by koji:

$ git clone -n https://src.fedoraproject.org/rpms/jna /var/lib/mock/module-eclipse-2019-03-3120190513095549-5101262b-build-16233253-1162021/root/chroot_tmpdir/scmroot/jna
Cloning into '/var/lib/mock/module-eclipse-2019-03-3120190513095549-5101262b-build-16233253-1162021/root/chroot_tmpdir/scmroot/jna'...
fatal: repository 'https://src.fedoraproject.org/rpms/jna/' not found

I am resubmitting the builds and hoping for the best :-(


This is a bug in how the build gets submitted.
The build is submitted with "SCM URL: git+https://src.fedoraproject.org/rpms/jna?#53cd350fc6b7c458bdff4fd9f7dcb85291648982".
But there needs to a be a ".git" after the repo name.
E.g.: "SCM URL: git+https://src.fedoraproject.org/rpms/jna.git?#53cd350fc6b7c458bdff4fd9f7dcb85291648982"

So I don't know what is submitting this build for you, but if it's MBS (i.e. module), check your modulemd whether it contains the correct git repo url.

@puiterwijk I don't think that's the issue here. All module component builds are submitted from URLs like that, without .git suffix, and they complete just fine. Moreover, overriding SCM URL in modulemd is not allowed in Fedora MBS deployment.

This is a bug in how the build gets submitted.
The build is submitted with "SCM URL: git+https://src.fedoraproject.org/rpms/jna?#53cd350fc6b7c458bdff4fd9f7dcb85291648982".
But there needs to a be a ".git" after the repo name.
E.g.: "SCM URL: git+https://src.fedoraproject.org/rpms/jna.git?#53cd350fc6b7c458bdff4fd9f7dcb85291648982"
So I don't know what is submitting this build for you, but if it's MBS (i.e. module), check your modulemd whether it contains the correct git repo url.

That is not the issue, this build failed one in three times, which means that twice it worked with identical modulemd (hence intermittent)

I don't see any obvious errors in logs. Not sure what could be happening...

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: src.fp.o

a month ago

Could "eventual consistency" model of repoSpanner be the cause of this? Koji builder could've pulled from a repoSpanner node that hasn't received the commit yet, even though the push succeeded (majority of nodes received the commit).

@mizdebsk I don't think it could be. src.fedoraproject.org does not have repoSpanner. If this were happening on src.stg.fedoraproject.org then I would say it was possible.

@mbooth are you still seeing this?

@mbooth are you still seeing this?

Yes I saw it again this week, although I don't have the link to the build at hand because I was in a rush.

This still happens.
Example: https://koji.fedoraproject.org/koji/taskinfo?taskID=35125115

$ git clone -n https://src.fedoraproject.org/rpms/junit5 /var/lib/mock/module-javapackages-tools-201901-2820190529110025-f469ab01-build-16375846-1171750/root/chroot_tmpdir/scmroot/junit5
Cloning into '/var/lib/mock/module-javapackages-tools-201901-2820190529110025-f469ab01-build-16375846-1171750/root/chroot_tmpdir/scmroot/junit5'...
fatal: repository 'https://src.fedoraproject.org/rpms/junit5/' not found

The same issue just happened to me, outsides of Koji, when I tried to pull from an existing, already cloned repository:

$ git pull
fatal: repository 'https://src.fedoraproject.org/forks/mbi/rpms/velocity.git/' not found

Another occurance today:

https://koji.fedoraproject.org/koji/taskinfo?taskID=35408245

$ git clone -n https://src.fedoraproject.org/rpms/jackson-modules-base /var/lib/mock/module-eclipse-2019-03-3020190608151621-bd986a65-build-16503575-1182591/root/chroot_tmpdir/scmroot/jackson-modules-base
Cloning into '/var/lib/mock/module-eclipse-2019-03-3020190608151621-bd986a65-build-16503575-1182591/root/chroot_tmpdir/scmroot/jackson-modules-base'...
fatal: repository 'https://src.fedoraproject.org/rpms/jackson-modules-base/' not found

It's keeping me on my toes; module builds require serious babysitting:

https://koji.fedoraproject.org/koji/taskinfo?taskID=35521528

BuildError: Error running GIT command "git clone -n https://src.fedoraproject.org/rpms/protobuf /var/lib/mock/module-eclipse-2019-06-2920190613133453-72bf7ed8-build-16546230-1188136/root/chroot_tmpdir/scmroot/protobuf", see checkout.log for details

Login to comment on this ticket.

Metadata