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.

 *** [FAIL] registry.connect.redhat.com/couchbase/server@sha256:01d289f7fe41520ffc6662717aba1bd2351e5576b1a4ffa76e8ebb62e73269c0

 is not schema_version == 2

 
Server version 6.0.3-1 is the image being referenced by the sha above

 skopeo inspect docker://registry.connect.redhat.com/couchbase/server:6.0.3-1 

...

"Digest": "sha256:01d289f7fe41520ffc6662717aba1bd2351e5576b1a4ffa76e8ebb62e73269c0",

 
The reason why this specific image is scanned is because it was referenced in RELATED_IMAGE environment var..

- name: RELATED_IMAGE_COUCHBASE_SERVER

  value: registry.connect.redhat.com/couchbase/server:6.0.3-1 

http://registry.connect.redhat.com/couchbase/server:6.0.3-1(as required by K8S-1284)
 
And that Image is v1 schema

skopeo inspect --raw docker://registry.connect.redhat.com/couchbase/server:6.0.3-1 | grep schemaVersion

 "schemaVersion": 1

Whereas 6.0.4-1 is v2

 skopeo inspect --raw docker://registry.connect.redhat.com/couchbase/server:6.0.4-1 | grep schemaVersion "schemaVersion": 2,  

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.