Uploaded image for project: 'Project Quay'
  1. Project Quay
  2. PROJQUAY-3921

The build log generated by uploading dockerfile can not be filtered out by build ID in Build Logs page

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • quay-v3.7.1
    • quay-builder
    • False
    • None
    • False

      Description of problem:

      Quay build has many triggers, uploading dockerfile, github, gitlab, bitbucket and so on.  After completing build processes by different build triggers successfully, filter out build logs by build ID in Super User Admin Panel Build Logs page.  The build log generated by github, gitlab, bitbucket triggers can be filtered out successfully, but the build log generated by uploading dockerfile can not be filtered out, the quay web console will go to 500 error page. 

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

      quay-operator-bundle-container-v3.7.1-16
      Index image v4.10: registry-proxy.engineering.redhat.com/rh-osbs/iib:246636
      quay-operator-rhel8@sha256:5619aa0fab34e963116c1a0f4416a6183c575437dfe035ca7a131121fe7b4146

      How reproducible:

      always

      Steps to Reproduce:
      1. set up kubernetesPodman build environment, complete build processes by uploading dockerfile, github, gitlab, bitbucket triggers.
      2. filter build log by build ID in Super User Admin Panel Build Logs page

      Actual results:

      The build log generated by github, gitlab, bitbucket triggers can be filtered out successfully, but the build log generated by uploading dockerfile can not be filtered out, the quay web console will go to 500 error page. 

      the successful build processes

      filter out build log generated by uploading dockerfile

      filter out build log generated by github

       

      Expected results:

      All build log should be filtered out successfully

      Additional info:

      Got below error in quay pod log 

      
      5266 gunicorn-web stdout |   File "/quay-registry/endpoints/api/__init__.py", line 343, in wrapped
      5267 gunicorn-web stdout |     return func(*args, **kwargs)
      5268 gunicorn-web stdout |   File "/quay-registry/endpoints/api/__init__.py", line 382, in wrapped
      5269 gunicorn-web stdout |     return func(*args, **kwargs)
      5270 gunicorn-web stdout |   File "/quay-registry/endpoints/api/superuser.py", line 1091, in get
      5271 gunicorn-web stdout |     build = pre_oci_model.get_repository_build(build_uuid)
      5272 gunicorn-web stdout |   File "/quay-registry/endpoints/api/superuser_models_pre_oci.py", line 111, in get_repository_build
      5273 gunicorn-web stdout |     _create_user(build.trigger.pull_robot),
      5274 gunicorn-web stdout | AttributeError: 'NoneType' object has no attribute 'pull_robot'
      5275 gunicorn-web stdout | 2022-06-07 08:56:34,916 [220] [INFO] [gunicorn.access]  - - [07/Jun/2022:08:56:34 +0000] "GET /api/v     1/superuser/8da4ea1d-a923-4b39-a3c6-369fee63711f/build HTTP/1.0" 500 0 "-" "-"

       

      The attachment includes the whole quay pod log

        1. quayregistry-quay-app-999b84594-6zl9t.log
          1.44 MB
          Weihua Hu
        2. Screenshot from 2022-06-07 15-36-53.png
          102 kB
          Weihua Hu
        3. Screenshot from 2022-06-07 17-56-25.png
          114 kB
          Weihua Hu
        4. Screenshot from 2022-06-07 18-13-39.png
          122 kB
          Weihua Hu

              Unassigned Unassigned
              rhwhu Weihua Hu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: