Is there an existing issue for this?
Troubleshooting logs
Current Behavior
ScanJob's status for these two conditions:
One is "Failed with message: cannot discover images in registry ..."
The other is "Complete with Reason: NoImagesToScan"
Expected Behavior
ScanJob's status for these two conditions should be the same?
Steps To Reproduce
- Set up a registry with 0 image in it (ex: nvpublic/compliance_config in docker.io)
- Set up scanJob for it and the result is below (Failed with message: cannot
discover images in registry ...)
root@sbom-rke2-213-0121:~# k get scanjob test-0-image-nvpublic-compli6wgbh -o yaml
apiVersion: sbomscanner.kubewarden.io/v1alpha1
kind: ScanJob
metadata:
annotations:
sbomscanner.kubewarden.io/creation-timestamp: "2026-01-23T07:14:18.550733126Z"
sbomscanner.kubewarden.io/registry: '{"kind":"Registry","apiVersion":"sbomscanner.kubewarden.io/v1alpha1","metadata":{"name":"test-0-image-nvpublic-compli","namespace":"default","uid":"1ea6eefb-818b-4181-b1d7-4ba50fd564f4","resourceVersion":"693025","generation":1,"creationTimestamp":"2026-01-23T07:14:02Z"},"spec":{"uri":"docker.io","catalogType":"OCIDistribution","repositories":[{"name":"nvpublic/compliance_config"}]},"status":{}}'
creationTimestamp: "2026-01-23T07:14:18Z"
generateName: test-0-image-nvpublic-compli
generation: 1
name: test-0-image-nvpublic-compli6wgbh
namespace: default
ownerReferences:
- apiVersion: sbomscanner.kubewarden.io/v1alpha1
blockOwnerDeletion: true
controller: true
kind: Registry
name: test-0-image-nvpublic-compli
uid: 1ea6eefb-818b-4181-b1d7-4ba50fd564f4
resourceVersion: "693650"
uid: 2aa5b12f-3743-4784-ac48-c7802f883f79
spec:
registry: test-0-image-nvpublic-compli
status:
completionTime: "2026-01-23T07:15:31Z"
conditions:
- lastTransitionTime: "2026-01-23T07:14:18Z"
message: ScanJob failed
observedGeneration: 1
reason: Failed
status: "False"
type: Scheduled
- lastTransitionTime: "2026-01-23T07:15:31Z"
message: ScanJob failed
observedGeneration: 1
reason: Failed
status: "False"
type: InProgress
- lastTransitionTime: "2026-01-23T07:14:18Z"
message: ScanJob failed
observedGeneration: 1
reason: Failed
status: "False"
type: Complete
- lastTransitionTime: "2026-01-23T07:15:31Z"
message: 'failed to handle message on subject sbomscanner.catalog.create: cannot
discover images in registry test-0-image-nvpublic-compli: cannot list repository
contents: cannot create lister for repository index.docker.io/nvpublic/compliance_config:
GET https://index.docker.io/v2/nvpublic/compliance_config/tags/list?n=1000:
NAME_UNKNOWN: repository name not known to registry; map[name:nvpublic/compliance_config]'
observedGeneration: 1
reason: InternalError
status: "True"
type: Failed
startTime: "2026-01-23T07:15:30Z"
- Set up a registry and set up a non-existing platform filter for it (ex: setting windows/arm/v8 for it but that registry's images don't have this platform)
root@sbom-rke2-213-0121:~# k get registry test-nvpublic-al-non-exist-filter -o yaml
apiVersion: sbomscanner.kubewarden.io/v1alpha1
kind: Registry
metadata:
creationTimestamp: "2026-01-23T07:22:39Z"
generation: 1
name: test-nvpublic-al-non-exist-filter
namespace: default
resourceVersion: "696609"
uid: 73295738-d303-4671-ad7e-c1dec9b029ae
spec:
authSecret: ""
caBundle: ""
catalogType: OCIDistribution
insecure: false
platforms:
- arch: arm
os: windows
variant: v8
repositories:
- name: nvpublic/al
uri: docker.io
- Set up a scanJob for it and the result is below (Complete with Reason: NoImagesToScan)
root@sbom-rke2-213-0121:~# k get scanjob test-nvpublic-al-non-exist-filterpx5mn -o yaml
apiVersion: sbomscanner.kubewarden.io/v1alpha1
kind: ScanJob
metadata:
annotations:
sbomscanner.kubewarden.io/creation-timestamp: "2026-01-23T07:23:02.016602712Z"
sbomscanner.kubewarden.io/registry: '{"kind":"Registry","apiVersion":"sbomscanner.kubewarden.io/v1alpha1","metadata":{"name":"test-nvpublic-al-non-exist-filter","namespace":"default","uid":"73295738-d303-4671-ad7e-c1dec9b029ae","resourceVersion":"696609","generation":1,"creationTimestamp":"2026-01-23T07:22:39Z"},"spec":{"uri":"docker.io","catalogType":"OCIDistribution","repositories":[{"name":"nvpublic/al"}],"platforms":[{"arch":"arm","os":"windows","variant":"v8"}]},"status":{}}'
creationTimestamp: "2026-01-23T07:23:01Z"
generateName: test-nvpublic-al-non-exist-filter
generation: 1
name: test-nvpublic-al-non-exist-filterpx5mn
namespace: default
ownerReferences:
- apiVersion: sbomscanner.kubewarden.io/v1alpha1
blockOwnerDeletion: true
controller: true
kind: Registry
name: test-nvpublic-al-non-exist-filter
uid: 73295738-d303-4671-ad7e-c1dec9b029ae
resourceVersion: "697269"
uid: 99254766-645d-4159-a493-1400313e98a0
spec:
registry: test-nvpublic-al-non-exist-filter
status:
completionTime: "2026-01-23T07:24:14Z"
conditions:
- lastTransitionTime: "2026-01-23T07:23:02Z"
message: ScanJob completed successfully
observedGeneration: 1
reason: Complete
status: "False"
type: Scheduled
- lastTransitionTime: "2026-01-23T07:24:14Z"
message: ScanJob completed successfully
observedGeneration: 1
reason: Complete
status: "False"
type: InProgress
- lastTransitionTime: "2026-01-23T07:24:14Z"
message: No images to process
observedGeneration: 1
reason: NoImagesToScan
status: "True"
type: Complete
- lastTransitionTime: "2026-01-23T07:23:02Z"
message: ScanJob completed successfully
observedGeneration: 1
reason: Complete
status: "False"
type: Failed
startTime: "2026-01-23T07:23:02Z"
Environment
Anything else?
No response
Is there an existing issue for this?
Troubleshooting logs
Current Behavior
ScanJob's status for these two conditions:
One is "Failed with message: cannot discover images in registry ..."
The other is "Complete with Reason: NoImagesToScan"
Expected Behavior
ScanJob's status for these two conditions should be the same?
Steps To Reproduce
discover images in registry ...)
Environment
Anything else?
No response