I see that oc-mirror fails to generate signature files when mirroring ec and rc release payloads using tag and digest.
    

    4.18
    

    Always
    

    1. use the imageSetConfig as shown below
    2. Run command oc-mirror -c /tmp/isc.yaml --workspace file://test docker://localhost:5000 --dest-tls-verify=false --v2
    3.
    

    see that no signature files have been generated.
   2025/02/12 09:38:32  [INFO]   : === Results ===
2025/02/12 09:38:32  [INFO]   :  ✓  192 / 192 release images mirrored successfully
2025/02/12 09:38:32  [INFO]   : 📄 Generating IDMS file...
2025/02/12 09:38:32  [INFO]   : ec/working-dir/cluster-resources/idms-oc-mirror.yaml file created
2025/02/12 09:38:32  [INFO]   : 📄 Generating ITMS file...
2025/02/12 09:38:32  [INFO]   : ec/working-dir/cluster-resources/itms-oc-mirror.yaml file created
2025/02/12 09:38:32  [INFO]   : 📄 No catalogs mirrored. Skipping CatalogSource file generation.
2025/02/12 09:38:32  [INFO]   : 📄 No catalogs mirrored. Skipping ClusterCatalog file generation.
2025/02/12 09:38:32  [INFO]   : 📄 Generating UpdateService file...
2025/02/12 09:38:32  [INFO]   : ec/working-dir/cluster-resources/updateService.yaml file created
2025/02/12 09:38:32  [INFO]   : mirror time     : 2m25.806570546s
2025/02/12 09:38:32  [INFO]   : 👋 Goodbye, thank you for using oc-mirror

    

    signature files should be generated as rc and ec candidates does have signatures and they are being used by the customer.
    

    kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v2alpha1
mirror:
  platform:
    release: quay.io/openshift-release-dev/ocp-release:4.19.0-ec.1-x86_64
    graph: true

kind: ImageSetConfiguration
apiVersion: mirror.openshift.io/v2alpha1
mirror:
  platform:
    release: quay.io/openshift-release-dev/ocp-release@sha256:f0de3be10be2f5fc1a5b1c208bcfe5d3a71a70989cacbca57ebf7c5fe6e14b09
    graph: true