Skip to content
Execute Tests

Fix Kyverno require-valid-owner-reference for Neo4j operations pods #699

Sign in to view logs

Fix Kyverno require-valid-owner-reference for Neo4j operations pods

Fix Kyverno require-valid-owner-reference for Neo4j operations pods #699

Re-run triggered March 10, 2026 07:39
@bfeshtibfeshti
#521
add-pod-owner-reference
Status Failure
Total duration 39m 51s
Artifacts –

tests.yml

on: pull_request
check-pr
2s
check-pr
Cleanup Dangling Resources
28s
Cleanup Dangling Resources
Debian GKE Creation
6m 10s
Debian GKE Creation
RedHat GKE Creation
7m 10s
RedHat GKE Creation
ReverseProxy and Backup Docker Image build
3m 36s
ReverseProxy and Backup Docker Image build
Debian Enterprise tests
29m 59s
Debian Enterprise tests
Debian Community Tests
18m 58s
Debian Community Tests
RedHat Enterprise Tests
31m 22s
RedHat Enterprise Tests
RedHat Community Tests
17m 54s
RedHat Community Tests
Debian GKE Cluster Deletion
30s
Debian GKE Cluster Deletion
ReverseProxy and Backup Docker Image build
0s
ReverseProxy and Backup Docker Image build
RedHat GKE Cluster Deletion
31s
RedHat GKE Cluster Deletion
Packaging and Release
0s
Packaging and Release
Fit to window
Zoom out
Zoom in

Annotations

3 errors
Debian Community Tests
Process completed with exit code 1.
Debian Enterprise tests
Process completed with exit code 1.
RedHat Enterprise Tests
Process completed with exit code 1.