perl-File-Find-Object epel10 branch creation only partially succeeded

pghmcfc commented

2024-09-03 10:43:41 +00:00

I requested an epel10 branch of perl-File-Find-Object this morning, but the request failed (https://pagure.io/releng/fedora-scm-requests/issue/66267) with Status: 500

Traceback (most recent call last):
  File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process
    self.process_ticket(issue)
  File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket
    self.create_new_branch(issue, issue_body)
  File "/code/toddlers/plugins/scm_request_processor.py", line 766, in create_new_branch
    self.dist_git.new_branch(
  File "/code/toddlers/utils/pagure.py", line 496, in new_branch
    raise PagureError(
toddlers.exceptions.pagure_error.PagureError: Couldn't create branch in project 'rpms/perl-File-Find-Object'

Request to 'https://src.fedoraproject.org/api/0/rpms/perl-File-Find-Object/git/branch':
{'branch': 'epel10', 'from_commit': '5257202447a0cb531083969a3eda4a1cd25578e6'}

Response:
None

Status code: 500

Nevertheless, the branch was actually created and I can push to it but the build fails with the error BuildError: package perl-File-Find-Object not in list for tag epel10.0-testing-candidate:

Building perl-File-Find-Object-0.3.8-1.el10 for epel10-candidate
Created task: 122881062
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122881062
Watching tasks (this may be safely interrupted)...
122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free
122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free -> assigned (buildvm-ppc64le-12.iad2.fedoraproject.org)
122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): assigned (buildvm-ppc64le-12.iad2.fedoraproject.org) -> open (buildvm-ppc64le-12.iad2.fedoraproject.org)
  122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free
  122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free -> assigned (buildvm-x86-20.iad2.fedoraproject.org)
  122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): assigned (buildvm-x86-20.iad2.fedoraproject.org) -> open (buildvm-x86-20.iad2.fedoraproject.org)
  122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): open (buildvm-x86-20.iad2.fedoraproject.org) -> closed
  0 free  1 open  1 done  0 failed
122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): open (buildvm-ppc64le-12.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-File-Find-Object not in list for tag epel10.0-testing-candidate
  0 free  0 open  1 done  1 failed

122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020) failed

This is the same as what happened for me with perl-Sereal yesterday (https://pagure.io/fedora-infrastructure/issue/12159). I was eventually able to build that several hours later in the day but I don't know whether that was because somebody actually did something to fix it, or a sync process happened that fixed it in the background.

I requested an epel10 branch of perl-File-Find-Object this morning, but the request failed (https://pagure.io/releng/fedora-scm-requests/issue/66267) with Status: 500 ``` Traceback (most recent call last): File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process self.process_ticket(issue) File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket self.create_new_branch(issue, issue_body) File "/code/toddlers/plugins/scm_request_processor.py", line 766, in create_new_branch self.dist_git.new_branch( File "/code/toddlers/utils/pagure.py", line 496, in new_branch raise PagureError( toddlers.exceptions.pagure_error.PagureError: Couldn't create branch in project 'rpms/perl-File-Find-Object' Request to 'https://src.fedoraproject.org/api/0/rpms/perl-File-Find-Object/git/branch': {'branch': 'epel10', 'from_commit': '5257202447a0cb531083969a3eda4a1cd25578e6'} Response: None Status code: 500 ``` Nevertheless, the branch was actually created and I can push to it but the build fails with the error BuildError: package perl-File-Find-Object not in list for tag epel10.0-testing-candidate: ``` Building perl-File-Find-Object-0.3.8-1.el10 for epel10-candidate Created task: 122881062 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122881062 Watching tasks (this may be safely interrupted)... 122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free 122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free -> assigned (buildvm-ppc64le-12.iad2.fedoraproject.org) 122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): assigned (buildvm-ppc64le-12.iad2.fedoraproject.org) -> open (buildvm-ppc64le-12.iad2.fedoraproject.org) 122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free 122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): free -> assigned (buildvm-x86-20.iad2.fedoraproject.org) 122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): assigned (buildvm-x86-20.iad2.fedoraproject.org) -> open (buildvm-x86-20.iad2.fedoraproject.org) 122881079 buildSRPMFromSCM (/rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): open (buildvm-x86-20.iad2.fedoraproject.org) -> closed 0 free 1 open 1 done 0 failed 122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020): open (buildvm-ppc64le-12.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-File-Find-Object not in list for tag epel10.0-testing-candidate 0 free 0 open 1 done 1 failed 122881062 build (epel10-candidate, /rpms/perl-File-Find-Object.git:5a70661c06ed5ab2fbdb1c0d5444bed0858f6020) failed ``` This is the same as what happened for me with perl-Sereal yesterday (https://pagure.io/fedora-infrastructure/issue/12159). I was eventually able to build that several hours later in the day but I don't know whether that was because somebody actually did something to fix it, or a sync process happened that fixed it in the background.

pghmcfc commented

2024-09-03 14:10:40 +00:00

Author

Still failing at the moment so if there's a background process fixing this, it doesn't seem to run very often.

zlopez commented

2024-09-03 14:12:01 +00:00

Contributor

The error means that the https://src.fedoraproject.org/ returned 500 when calling the branch creation API.

The script that is creating the branch is not doing anything with koji, so this must be caused somewhere else then during creation of the branch. My assumption would be that the pagure API is enabling the koji for the package and this failed.

Let me check if that is true.

The error means that the https://src.fedoraproject.org/ returned 500 when calling the branch creation API. The script that is creating the branch is not doing anything with koji, so this must be caused somewhere else then during creation of the branch. My assumption would be that the pagure API is enabling the koji for the package and this failed. Let me check if that is true.

zlopez commented

2024-09-03 14:12:22 +00:00

Contributor

Metadata Update from @zlopez:

Issue priority set to: Waiting on Assignee (was: Needs Review)
Issue tagged with: Needs investigation, epel, medium-gain, ops

**Metadata Update from @zlopez**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: Needs investigation, epel, medium-gain, ops

zlopez commented

2024-09-03 14:22:02 +00:00

Contributor

So the pagure API code doesn't touch koji at all, just trying to create the branch in pagure. So the koji enablement must happen somewhere else.

zlopez commented

2024-09-03 14:32:54 +00:00

Contributor

@carlwgeorge I think something is not correctly setup for epel10 yet, or is this expected behavior?

pghmcfc commented

2024-09-03 15:05:35 +00:00

Author

I don't think it's expected behavior because I've done dozens of epel10 branch requests over the last couple of weeks and only 2 have failed like this.

After the branch is created, is there a message sent out? I wonder if that message perhaps doesn't get sent out and then something else doesn't see the message and hence doesn't update koji?

I don't think it's expected behavior because I've done dozens of epel10 branch requests over the last couple of weeks and only 2 have failed like this. After the branch is created, is there a message sent out? I wonder if that message perhaps doesn't get sent out and then something else doesn't see the message and hence doesn't update koji?

zlopez commented

2024-09-03 15:10:31 +00:00

Contributor

The message is sent, you can see all the latest messages in datagrepper

EDIT: And here is the message about creation of the branch you requested.

The message is sent, you can see all the latest messages in [datagrepper](https://apps.fedoraproject.org/datagrepper/v2/search?topic=org.fedoraproject.prod.pagure.git.branch.creation) EDIT: And here is the [message](https://apps.fedoraproject.org/datagrepper/v2/id?id=41299bd9-ae48-4201-bdff-d5b2f342d117&is_raw=true&size=extra-large) about creation of the branch you requested.

kevin commented

2024-09-03 15:33:24 +00:00

The process that syncs projects/branches/ownership to koji is the koji_sync_listener service ( fm-consumer@koji_sync_listener.service ) running on bodhi-backend01.

It should be listening to those messages and acting on them. I don't know why it did not in this case.

It also runs once a day a 'full sync' where it checks all packages and syncs ownership/etc to koji.

The process that syncs projects/branches/ownership to koji is the koji_sync_listener service ( fm-consumer@koji_sync_listener.service ) running on bodhi-backend01. It should be listening to those messages and acting on them. I don't know why it did not in this case. It also runs once a day a 'full sync' where it checks all packages and syncs ownership/etc to koji.

pghmcfc commented

2024-09-03 15:39:56 +00:00

Author

There goes my theory then. No idea what's going wrong, though the traceback in the branch request does correlate with the koji issue manifesting.

Build still failing at the moment.

There goes my theory then. No idea what's going wrong, though the traceback in the branch request does correlate with the koji issue manifesting. Build still failing at the moment.

pghmcfc commented

2024-09-03 15:41:33 +00:00

Author

Ah, so does the once-a-day run take place sometime around 1900UTC? That could explain why my perl-Sereal build eventually worked yesterday.

carlwgeorge commented

2024-09-03 15:42:34 +00:00

Indeed the original error toddlers.exceptions.pagure_error.PagureError is because of the status code returned by pagure. I've seen it happen occasionally, but as of yet no one has done a deep dive investigation to figure out why. With the impending replacement of pagure I'm not entirely sure spending cycles on a rare intermittent error is worth the effort.

Allowing the package in koji is done in two ways:

koji_sync_listener notices the message and runs owner-sync-pagure for the package. The name is a bit misleading, as the ownership is set in the tag allowlist, which is what permits the package to be built in that tag.
There is a cron job that runs owner-sync-pagure for all packages once a day, to catch and clean up instances like this that were missed for whatever reason.

I believe the cron job would have picked this up and fixed it, but I went ahead and manually added the package to the tag allowlist to unblock you.

carl ~ 
❯ koji list-pkgs --tag epel10.0-testing-candidate --package perl-File-Find-Object
Package                 Tag                     Extra Arches     Owner          
----------------------- ----------------------- ---------------- ---------------
perl-File-Find-Object   epel10.0                                 pghmcfc

Indeed the original error `toddlers.exceptions.pagure_error.PagureError` is because of the status code returned by pagure. I've seen it happen occasionally, but as of yet no one has done a deep dive investigation to figure out why. With the impending replacement of pagure I'm not entirely sure spending cycles on a rare intermittent error is worth the effort. Allowing the package in koji is done in two ways: - [koji_sync_listener](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/files/koji_sync_listener.py) notices the message and runs [owner-sync-pagure](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/templates/owner-sync-pagure.j2) for the package. The name is a bit misleading, as the ownership is set in the tag allowlist, which is what permits the package to be built in that tag. - There is a [cron job](https://pagure.io/fedora-infra/ansible/blob/main/f/roles/bodhi2/backend/tasks/main.yml#_114-125) that runs owner-sync-pagure for all packages once a day, to catch and clean up instances like this that were missed for whatever reason. I believe the cron job would have picked this up and fixed it, but I went ahead and manually added the package to the tag allowlist to unblock you. ``` carl ~ ❯ koji list-pkgs --tag epel10.0-testing-candidate --package perl-File-Find-Object Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- perl-File-Find-Object epel10.0 pghmcfc ```

pghmcfc commented

2024-09-03 16:15:56 +00:00

Author

Thanks, build succeeded now. What time zone does that cron job run in? It'll be useful to know when to resubmit builds if this crops up again, which is quite likely given that I'm working through a lot of the perl stack for EPEL-10 at the moment. It'll save me having to keep re-submitting until it works.

kevin commented

2024-09-03 18:48:25 +00:00

It's UTC. All infrastructure machines are on UTC.

I'm a bit puzzled how this message wasn't processed, but I am not sure how to debug it any further. I looked for that message in the logs for the sync listener and didn't see it... ;(

It's UTC. All infrastructure machines are on UTC. I'm a bit puzzled how this message wasn't processed, but I am not sure how to debug it any further. I looked for that message in the logs for the sync listener and didn't see it... ;(

pghmcfc commented

2024-09-04 06:58:59 +00:00

Author

I'm not sure how my perl-Sereal build from yesterday (https://koji.fedoraproject.org/koji/buildinfo?buildID=2539922) started working now. The successful build started at 1655 after several failures at various points earlier in the day. However, the cron job seems to be set to run at 0415 so it seems unlikely that that cron job is what fixed things.

pghmcfc commented

2024-09-04 09:53:21 +00:00

Author

Saw a different error today (https://pagure.io/releng/fedora-scm-requests/issue/66371):

Error happened during processing:

Traceback (most recent call last):
  File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process
    self.process_ticket(issue)
  File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket
    self.create_new_branch(issue, issue_body)
  File "/code/toddlers/plugins/scm_request_processor.py", line 780, in create_new_branch
    self.pagure_io.close_issue(
  File "/code/toddlers/utils/pagure.py", line 191, in close_issue
    raise PagureError(
toddlers.exceptions.pagure_error.PagureError: Couldn't close issue 'https://pagure.io/releng/fedora-scm-requests/issue/66371'

Request to 'https://pagure.io/api/0/releng/fedora-scm-requests/issue/66371/status':
{'status': 'Processed'}

Response:
None

Status code: 500

Don't know if this is blocking a build or not because there is another issue affecting the epel10 buildroot today (https://pagure.io/releng/issue/12305), which I'm hitting for all epel10 builds. It doesn't look promising though:

$ koji list-pkgs --tag epel10.0-testing-candidate --package perl-Cpanel-JSON-XS
(no matching packages)

Saw a different error today (https://pagure.io/releng/fedora-scm-requests/issue/66371): ``` Error happened during processing: Traceback (most recent call last): File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process self.process_ticket(issue) File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket self.create_new_branch(issue, issue_body) File "/code/toddlers/plugins/scm_request_processor.py", line 780, in create_new_branch self.pagure_io.close_issue( File "/code/toddlers/utils/pagure.py", line 191, in close_issue raise PagureError( toddlers.exceptions.pagure_error.PagureError: Couldn't close issue 'https://pagure.io/releng/fedora-scm-requests/issue/66371' Request to 'https://pagure.io/api/0/releng/fedora-scm-requests/issue/66371/status': {'status': 'Processed'} Response: None Status code: 500 ``` Don't know if this is blocking a build or not because there is another issue affecting the epel10 buildroot today (https://pagure.io/releng/issue/12305), which I'm hitting for all epel10 builds. It doesn't look promising though: ``` $ koji list-pkgs --tag epel10.0-testing-candidate --package perl-Cpanel-JSON-XS (no matching packages) ```

zlopez commented

2024-09-04 10:03:47 +00:00

Contributor

Saw a different error today (https://pagure.io/releng/fedora-scm-requests/issue/66371):

Error happened during processing:

Traceback (most recent call last):
File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process
self.process_ticket(issue)
File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket
self.create_new_branch(issue, issue_body)
File "/code/toddlers/plugins/scm_request_processor.py", line 780, in create_new_branch
self.pagure_io.close_issue(
File "/code/toddlers/utils/pagure.py", line 191, in close_issue
raise PagureError(
toddlers.exceptions.pagure_error.PagureError: Couldn't close issue 'https://pagure.io/releng/fedora-scm-requests/issue/66371'

Request to 'https://pagure.io/api/0/releng/fedora-scm-requests/issue/66371/status':
{'status': 'Processed'}

Response:
None

Status code: 500

This error just means that the script couldn't close the ticket as processed, so it doesn't affect anything.

> Saw a different error today (https://pagure.io/releng/fedora-scm-requests/issue/66371): > ``` > Error happened during processing: > > Traceback (most recent call last): > File "/code/toddlers/plugins/scm_request_processor.py", line 189, in process > self.process_ticket(issue) > File "/code/toddlers/plugins/scm_request_processor.py", line 301, in process_ticket > self.create_new_branch(issue, issue_body) > File "/code/toddlers/plugins/scm_request_processor.py", line 780, in create_new_branch > self.pagure_io.close_issue( > File "/code/toddlers/utils/pagure.py", line 191, in close_issue > raise PagureError( > toddlers.exceptions.pagure_error.PagureError: Couldn't close issue 'https://pagure.io/releng/fedora-scm-requests/issue/66371' > > Request to 'https://pagure.io/api/0/releng/fedora-scm-requests/issue/66371/status': > {'status': 'Processed'} > > Response: > None > > Status code: 500 > ``` This error just means that the script couldn't close the ticket as processed, so it doesn't affect anything.

pghmcfc commented

2024-09-04 10:15:13 +00:00

Author

Well that's what I'd have thought too but the ticket did in fact get closed and perl-Cpanel-JSON-XS doesn't seem to be in the list for epel10.0-testing-candidate.

zlopez commented

2024-09-04 10:40:45 +00:00

Contributor

Yeah, It seems that the ticket was closed and the error happened in the code after closing the ticket.

pghmcfc commented

2024-09-04 17:45:06 +00:00

Author

Not unexpectedly, my perl-Cpanel-JSON-XS build (branch request ticket had error this morning) failed:

Building perl-Cpanel-JSON-XS-4.38-1.el10 for epel10-candidate
Created task: 122950817
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122950817
Watching tasks (this may be safely interrupted)...
122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free
122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-a64-11.iad2.fedoraproject.org)
  122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free
  122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-x86-22.iad2.fedoraproject.org)
122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-a64-11.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Cpanel-JSON-XS not in list for tag epel10.0-testing-candidate
  0 free  1 open  0 done  1 failed
  122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-x86-22.iad2.fedoraproject.org) -> closed
  0 free  0 open  1 done  1 failed

I'll try again later/tomorrow, by which time the cron job or whatever should have fixed the issue.

Not unexpectedly, my `perl-Cpanel-JSON-XS` build (branch request ticket had error this morning) failed: ``` Building perl-Cpanel-JSON-XS-4.38-1.el10 for epel10-candidate Created task: 122950817 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122950817 Watching tasks (this may be safely interrupted)... 122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free 122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-a64-11.iad2.fedoraproject.org) 122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free 122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-x86-22.iad2.fedoraproject.org) 122950817 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-a64-11.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Cpanel-JSON-XS not in list for tag epel10.0-testing-candidate 0 free 1 open 0 done 1 failed 122950825 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-x86-22.iad2.fedoraproject.org) -> closed 0 free 0 open 1 done 1 failed ``` I'll try again later/tomorrow, by which time the cron job or whatever should have fixed the issue.

pghmcfc commented

2024-09-05 06:21:03 +00:00

Author

Either the cron tab takes a very long time to run or it has not resolved the issue:

$ koji list-pkgs --tag epel10.0-testing-candidate --package perl-Cpanel-JSON-XS
(no matching packages)
$ TZ=UTC date; fedpkg build
Thu  5 Sep 06:02:51 UTC 2024
Building perl-Cpanel-JSON-XS-4.38-1.el10 for epel10-candidate
Created task: 122970998
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122970998
Watching tasks (this may be safely interrupted)...
122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free
122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildhw-a64-20.iad2.fedoraproject.org)
  122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free
  122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-a64-24.iad2.fedoraproject.org)
122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildhw-a64-20.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Cpanel-JSON-XS not in list for tag epel10.0-testing-candidate
  0 free  1 open  0 done  1 failed
  122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-a64-24.iad2.fedoraproject.org) -> closed
  0 free  0 open  1 done  1 failed

122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f) failed

Either the cron tab takes a very long time to run or it has not resolved the issue: ``` $ koji list-pkgs --tag epel10.0-testing-candidate --package perl-Cpanel-JSON-XS (no matching packages) $ TZ=UTC date; fedpkg build Thu 5 Sep 06:02:51 UTC 2024 Building perl-Cpanel-JSON-XS-4.38-1.el10 for epel10-candidate Created task: 122970998 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122970998 Watching tasks (this may be safely interrupted)... 122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free 122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildhw-a64-20.iad2.fedoraproject.org) 122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free 122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): free -> open (buildvm-a64-24.iad2.fedoraproject.org) 122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildhw-a64-20.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Cpanel-JSON-XS not in list for tag epel10.0-testing-candidate 0 free 1 open 0 done 1 failed 122971043 buildSRPMFromSCM (/rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f): open (buildvm-a64-24.iad2.fedoraproject.org) -> closed 0 free 0 open 1 done 1 failed 122970998 build (epel10-candidate, /rpms/perl-Cpanel-JSON-XS.git:94c4d9f800f5f168105447263e223caefe09751f) failed ```

pghmcfc commented

2024-09-05 12:45:54 +00:00

Author

And at last, I was able to build perl-Cpanel-JSON-XS. No idea what happened to change things.

pghmcfc commented

2024-09-05 14:03:54 +00:00

Author

Today's example: perl-Module-Find

Building perl-Module-Find-0.16-3.el10 for epel10-candidate
Created task: 122988156
Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122988156
Watching tasks (this may be safely interrupted)...
122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free
122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free -> open (buildvm-a64-06.iad2.fedoraproject.org)
  122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free
  122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free -> open (buildvm-a64-17.iad2.fedoraproject.org)
122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): open (buildvm-a64-06.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Module-Find not in list for tag epel10.0-testing-candidate
  0 free  1 open  0 done  1 failed
  122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): open (buildvm-a64-17.iad2.fedoraproject.org) -> closed
  0 free  0 open  1 done  1 failed

122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f) failed

No indication that anything went wrong in the branch request (https://pagure.io/releng/fedora-scm-requests/issue/66471).

Today's example: `perl-Module-Find` ``` Building perl-Module-Find-0.16-3.el10 for epel10-candidate Created task: 122988156 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=122988156 Watching tasks (this may be safely interrupted)... 122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free 122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free -> open (buildvm-a64-06.iad2.fedoraproject.org) 122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free 122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): free -> open (buildvm-a64-17.iad2.fedoraproject.org) 122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): open (buildvm-a64-06.iad2.fedoraproject.org) -> FAILED: BuildError: package perl-Module-Find not in list for tag epel10.0-testing-candidate 0 free 1 open 0 done 1 failed 122988159 buildSRPMFromSCM (/rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f): open (buildvm-a64-17.iad2.fedoraproject.org) -> closed 0 free 0 open 1 done 1 failed 122988156 build (epel10-candidate, /rpms/perl-Module-Find.git:28107c20603d2f7f111e6762f23eb43c068ca07f) failed ``` No indication that anything went wrong in the branch request (https://pagure.io/releng/fedora-scm-requests/issue/66471).

pghmcfc commented

2024-09-06 14:12:26 +00:00

Author

Now managed to build perl-Module-Find. Wasn't able to a couple of hours ago. Don't know what changed.

Now managed to build `perl-Module-Find`. Wasn't able to a couple of hours ago. Don't know what changed.

kevin commented

2024-10-02 21:44:18 +00:00

Are you still seeing this?

pghmcfc commented

2024-10-03 05:56:07 +00:00

Author

Seen it once since perl-Module-Find and it resolved itself after a day or so (https://pagure.io/releng/fedora-scm-requests/issue/67247).

I've done the bulk of my packages in the perl stack now so my request frequency is much lower in the last couple of weeks.

Seen it once since perl-Module-Find and it resolved itself after a day or so (https://pagure.io/releng/fedora-scm-requests/issue/67247). I've done the bulk of my packages in the perl stack now so my request frequency is much lower in the last couple of weeks.

kevin commented

2024-10-03 21:46:55 +00:00

ok, lets close this... if you see it again, can you please re-open and we can try and track it down while it's fresh.

kevin commented

2024-10-03 21:46:55 +00:00

Metadata Update from @kevin:

Issue close_status updated to: Insufficient data
Issue status updated to: Closed (was: Open)

**Metadata Update from @kevin**: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)

Rows
Columns

perl-File-Find-Object epel10 branch creation only partially succeeded #12162