-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
quay-v3.8.1
-
False
-
None
-
False
-
-
Description of problem:
Cancel a build process, this cancel operation isn't displayed in repository Usage Logs page. Customer can't audit this cancel operation.
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 builder environment and log in with a non-super user
2. configure a build trigger, such as bitbucket build trigger
3. Start a new build
4. cancel this build process
5 Start a new build again
6. disable the build trigger
7. enable the build trigger
8. check audit logs in repository Usage Logs page
Actual results:
The "setup build trigger" operation, the "build from docker" operation, the "push" operation, the "build trigger disable" operation and the "build trigger enable" operation are logged in the Usage Logs page.
But the cancel build operation isn't logged.
Expected results:
The cancel operation should be logged in the Usage Logs page too.