#10778 fedpkg update error: Could not execute update
Closed: Fixed 2 years ago by kevin. Opened 2 years ago by gbcox.

I'm trying to submit an update to testing for F36 and F35. When I attempt I receive the following error:

fedpkg update
Could not execute update: Could not generate update request: 500 Server Error: Internal Server Error for url: https://bodhi.fedoraproject.org/oidc/login-token
A copy of the filled in template is saved as bodhi.template.last


What version of bodhi-client and fedpkg do you have?

rpm -q bodhi-client fedpkg ?

rpm -q bodhi-client fedpkg
bodhi-client-6.0.0-2.fc36.noarch
fedpkg-1.42-2.fc36.noarch

@abompard Could you look at this issue?

Folks, I got tired of waiting and just downgraded bodhi-client, and it immediately worked. So, apparently, there is a problem with the new bodhi-client which has been pushed to stable? It would probably be a good idea to pull that update until you can understand what is happening.

Metadata Update from @phsmoura:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: high-gain, high-trouble, ops

2 years ago

OK, so the problem is that fedpkg's support for bodhi 6.0 has been in its main branch for a couple months but a new version has not been released yet. I'll try to push for a new release and a corresponding update asap.

Actually, the patch to support Bodhi 6.0 has been included in the RPM since fedpkg-1.42-2.f36, which is what the reporter uses. I'll do some more checks.

It may actually be related to bodhi #4569.
@gbcox could you please remove the ~/.config/bodhi/client.json file and try again (when you have a new update to create)?
Thanks.

It may actually be related to bodhi #4569.
@gbcox could you please remove the ~/.config/bodhi/client.json file and try again (when you have a new update to create)?
Thanks.

Will do. I'll post the results in this ticket. Thanks for help!

Yes, deleting the client.json file resolved the issue. It is working now.

did you post the correct reference? bodhi #4569 seems a bit old

I think this should be all fixed here. Please reopen if you need anything further.

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

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog