Description of problem:

Configure a kubernetesPodman build environment, then trigger a build. After click Start Build button, the web page goes to a 500 page.

But login quay again, the build has been started successfully.

Version-Release number of selected component (if applicable):

quay 3.8.1
quay-operator-bundle-container-v3.8.1-16
Index image v4.11: registry-proxy.engineering.redhat.com/rh-osbs/iib:411069
registry.redhat.io/quay/quay-operator-rhel8@sha256:6c71ee77241394a24e4c518c12ca5fc8c0affc06313600c0c41c7b8e4dca9dab
registry.redhat.io/quay/quay-rhel8@sha256:e4ca9954d8adce2ac9ae4cc1416741e94080aac3bbbf35bbe141fb6ceed3f69e

How reproducible:

always

Steps to Reproduce:
1. setup a kubernetesPodman build environment
2. configure a build trigger, such as bitbucket build trigger
3. start new build by click "Start New Build" button
4. check expected branch and click "Start Build" button

Actual results:

The web page goes to a 500 error page

After got 500 error page, access quay  again, in Repository Builds page, can see the build has been triggered successfully.

Expected results:

After trigger the build process, the web page should go to  Repository Builds page directly, without any error page