OCPBUGS-650: fixing reliance on candidate channel containing all referenced bundle…

[grokspawn]

…s (#1009)

Signed-off-by: Jordan Keister [email protected]
Upstream-commit: 52e35f0291529290363e0e2d23d5b0c1524103c1
Upstream-repository: operator-registry

[grokspawn]

/jira refresh

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-650, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.12.0) matches configured target version for branch (4.12.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

…s (#1009)

Signed-off-by: Jordan Keister [email protected]
Upstream-commit: 52e35f0291529290363e0e2d23d5b0c1524103c1
Upstream-repository: operator-registry

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, timflannagan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [timflannagan]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD fceaf8a and 2 for PR HEAD 1e25545 in total

[grokspawn]

/hold for qe-review

[timflannagan]

/lgtm

[grokspawn]

/test e2e-gcp-olm

[Xia-Zhao-rh]

Hi, @grokspawn

zhaoxia@xzha-mac OCP-53915 % cat catalog-semver-veneer-1.yaml
Schema: olm.semver
Candidate:
  Bundles:
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v0.0.1
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-alpha
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-beta
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-alpha20220829
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-alpha20220830
Stable:
  Bundles:
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-beta
Fast:
  Bundles:
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v0.0.1
  - Image: quay.io/olmqe/nginxolm-operator-bundle:v1.0.1-beta

 
zhaoxia@xzha-mac OCP-53915 %  opm-379 alpha render-veneer semver catalog-semver-veneer-1.yaml
2022/09/08 11:30:50 semver &{%!q(*os.file=&{{{0 0 0} 3 {0} <nil> 0 1 true true true} catalog-semver-veneer-1.yaml <nil> false false false})}: semver-render: unable to post-process bundle info: encountered bundle versions which differ only by build metadata, which cannot be ordered: [bundle version "1.0.1-alpha+20220829" cannot be compared to "1.0.1-alpha", bundle version "1.0.1-alpha+20220830" cannot be compared to "1.0.1-alpha"]

The error message is not correct, "semver &{%!q(*os.file=&{{{0 0 0} 3 {0} 0 1 true true true}" is meaningless, please don't print them.

[grokspawn]

Dangit. That's related to the pipe support for semver veneer that we had. I had seen that error before, but I thought it was fixed. If you open a bug for that I can get them to investigate.

[Xia-Zhao-rh]

@grokspawn Thanks a lot. I create a bug https://issues.redhat.com/browse/OCPBUGS-1004 to track that problem.

[Xia-Zhao-rh]

/label qe-approved

[grokspawn]

/hold cancel

[grokspawn]

/test e2e-upgrade

[openshift-ci]

@grokspawn: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@grokspawn: All pull requests linked via external trackers have merged:

• openshift/operator-framework-olm#379

Jira Issue OCPBUGS-650 has been moved to the MODIFIED state.

In response to this:

…s (#1009)

Signed-off-by: Jordan Keister [email protected]
Upstream-commit: 52e35f0291529290363e0e2d23d5b0c1524103c1
Upstream-repository: operator-registry

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.