OLM-2726, OCPBUGS-643: downstreaming opm serve changes from operator-registry

[grokspawn]

including two commits which seem to be of equal priority to pipeline:

• 215f413e do not fatally exit from serve commands (NO-ISSUE: Synchronize From Upstream Repositories #1016)
• 494b68e6 opm serve: use pre-existing cache, if set and up-to-date (OCPBUGS-56467: Synchronize From Upstream Repositories #1005)

[grokspawn]

/retest-required

[grokspawn]

/jira refresh

[openshift-ci-robot]

/retest-required

Remaining retests: 2 against base HEAD 11644a5 and 8 for PR HEAD b94e073 in total

[perdasilva]

/hold for qe-review

[Xia-Zhao-rh]

Hi, @grokspawn
I tested it, but failed.
catsrc is not ready due to "compute digest: compute hash: write tar: open /tmp/cache/cache: permission denied"
Please check detail information in bellow jira:
https://issues.redhat.com/browse/OCPBUGS-643
Thanks

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-650, which is invalid:

• expected the bug to target the "4.12.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

including two commits which seem to be of equal priority to pipeline:

• 215f413e do not fatally exit from serve commands (NO-ISSUE: Synchronize From Upstream Repositories #1016)
• 494b68e6 opm serve: use pre-existing cache, if set and up-to-date (OCPBUGS-56467: Synchronize From Upstream Repositories #1005)

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.

[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 New, which is one of the valid states (NEW, ASSIGNED, POST)

In response to this:

/jira refresh

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.

[grokspawn]

I included the upstream fix for the related bug in this since the functionality is a logical whole.

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-643, which is invalid:

• expected the bug to target the "4.12.0" version, but it targets "premerge" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

including two commits which seem to be of equal priority to pipeline:

• 215f413e do not fatally exit from serve commands (NO-ISSUE: Synchronize From Upstream Repositories #1016)
• 494b68e6 opm serve: use pre-existing cache, if set and up-to-date (OCPBUGS-56467: Synchronize From Upstream Repositories #1005)

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.

[grokspawn]

/jira refresh

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-643, which is invalid:

• expected the bug to target only the "4.12.0" version, but multiple target versions were set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[grokspawn]

/jira refresh

[openshift-ci-robot]

@grokspawn: This pull request references Jira Issue OCPBUGS-643, 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:

/jira refresh

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]

@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.

[Xia-Zhao-rh]

/label qe-approved

[Xia-Zhao-rh]

/hold for qe-review

[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

[perdasilva]

/hold cancel

[openshift-ci-robot]

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

• openshift/operator-framework-olm#374

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

In response to this:

including two commits which seem to be of equal priority to pipeline:

• 215f413e do not fatally exit from serve commands (NO-ISSUE: Synchronize From Upstream Repositories #1016)
• 494b68e6 opm serve: use pre-existing cache, if set and up-to-date (OCPBUGS-56467: Synchronize From Upstream Repositories #1005)

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.

[grokspawn]

/cherrypick release-4.11

[openshift-cherrypick-robot]

@grokspawn: #374 failed to apply on top of branch "release-4.11":

Applying: do not fatally exit from serve commands (#1016)
Using index info to reconstruct a base tree...
M	staging/operator-registry/cmd/opm/serve/serve.go
M	vendor/github.com/operator-framework/operator-registry/cmd/opm/serve/serve.go
Falling back to patching base and 3-way merge...
Auto-merging vendor/github.com/operator-framework/operator-registry/cmd/opm/serve/serve.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/cmd/opm/serve/serve.go
Auto-merging staging/operator-registry/cmd/opm/serve/serve.go
CONFLICT (content): Merge conflict in staging/operator-registry/cmd/opm/serve/serve.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 do not fatally exit from serve commands (#1016)
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-4.11

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.