You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In deploy-release stage, messages similar to the following can be seen for operator, bundle, catalog images. This hasn't affected the CD/release. But we should investigate and resolve them. Changes to resolve this might require changes to the CD pipeline.
Validation Unsuccessful
When validating entry : 'bundle-1.4.0', the following observations were made
Artifact field: Artifact field is missing the sha256 suffix
Ensure the artifact follows the format <static_name>:<version>@sha256:<sha256_digest> OR <static_name>@sha256:<sha256_digest>
Validation for artifact field will be successful if you provide the artifact field's value as cp.stg.icr.io/cp/open-liberty-operator-bundle:1.4.0@sha256:1eee24d0e5510194a5be1463164116520cbce81915462d418f35b32128b3a216.
Please add the sha256 field in the end of the artifact value as shown to have this field successfully validated.
Ensure the artifact follows the format <static_name>:<version>@sha256:<sha256_digest> OR <static_name>@sha256:<sha256_digest>
The text was updated successfully, but these errors were encountered:
In deploy-release stage, messages similar to the following can be seen for operator, bundle, catalog images. This hasn't affected the CD/release. But we should investigate and resolve them. Changes to resolve this might require changes to the CD pipeline.
Build OLO CI 585:
The text was updated successfully, but these errors were encountered: