Tracking change of Related image version in our csv. While I suspect updating version will resolve the issue, we'll be able to track any unexpected error that may occur here.
Recent submission to RH Marketplace failed because validation ran a check on server 6.0.3-1 image and discovered it was using old v1 docker schema.
Server version 6.0.3-1 is the image being referenced by the sha above
The reason why this specific image is scanned is because it was referenced in RELATED_IMAGE environment var..
http://registry.connect.redhat.com/couchbase/server:6.0.3-1(as required by
And that Image is v1 schema
Whereas 6.0.4-1 is v2
And as also mentioned in
K8S-1404, schema must be v2. Good thing Ceej has already moved to new build tooling so we should be able to just submit with new server version.