#3856 500 internal server error when pushing new bodhi update
Closed: Fixed None Opened 10 years ago by nguzman.

= bug description =
Accessing https://admin.stg.fedoraproject.org/updates/save gives a "500 Internal error". This is when trying to add a new update.


You're attempting to submit an update to the staging bodhi instance, which cannot communicate with koji at the moment due to certificate issues. I don't know if Koji has ever properly worked in staging, actually.

If you want to submit a real update, please use the production bodhi instance: https://admin.fedoraproject.org/updates

We are working on plugin for Eclipse to make it easier for packagers. See https://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide?rd=Eclipse_Fedora_Packager_User_Guide#Pushing_a_Build_to_Koji . As part of our work we hoped that we can use the staging bodhi for testing purposes while we test our application. Will it be possible to enable the creation witout communicating it with Koji?

Replying to [comment:2 akurtakov]:

We are working on plugin for Eclipse to make it easier for packagers. See https://fedoraproject.org/wiki/Fedora_Packager_For_Eclipse_User_Guide?rd=Eclipse_Fedora_Packager_User_Guide#Pushing_a_Build_to_Koji . As part of our work we hoped that we can use the staging bodhi for testing purposes while we test our application. Will it be possible to enable the creation witout communicating it with Koji?

Yup, bodhi has a 'dummy' buildsystem layer that is enabled by default for the unit tests. I just enabled it in staging, but now I'm getting the following error when trying to submit an update:

{{{
hostname 'admin.stg.fedoraproject.org' doesn't match either of '*.fedoraproject.org', 'fedoraproject.org'
}}}

I am guessing this has to do with SSL verification in staging... reopening this ticket so we can continue to try and get things working properly in staging.

Okay, I figured it out. I changed bodhi's pkgdb_url to http://localhost/pkgdb to avoid doing any sort of SSL validation.

I was successfully able to submit a fake update: https://admin.stg.fedoraproject.org/updates/bodhi-1.2.3-4.el5

Please re-open if you hit any trouble testing your plugin against the bodhi staging instance.

Could you please sync the pkgs db so that I have commit access to some of the packages that I am trying to test with?

Or give me commit access to bodhi package for the staging instance.

I think this may be the last step before I can finally test submitting bodhi updates.

Can you go and apply for commit rights to bodhi in the stg pkgdb? https://admin.stg.fedoraproject.org/pkgdb/acls/name/bodhi

Thanks! It'll be much easier than updating the pkgdb db from production.

Can you go and apply for commit rights to bodhi in the stg pkgdb? https://admin.stg.fedoraproject.org/pkgdb/acls/name/bodhi

Yea, it'd be great if i can get approved

Replying to [comment:7 nguzman]:

Can you go and apply for commit rights to bodhi in the stg pkgdb? https://admin.stg.fedoraproject.org/pkgdb/acls/name/bodhi

Yea, it'd be great if i can get approved

Approved.

Replying to [comment:8 lmacken]:

Replying to [comment:7 nguzman]:

Can you go and apply for commit rights to bodhi in the stg pkgdb? https://admin.stg.fedoraproject.org/pkgdb/acls/name/bodhi

Yea, it'd be great if i can get approved

Approved.
Thank you! Setting it to fixed again, because I can now start testing the plugin.

Login to comment on this ticket.

Metadata