Sync upstream to downstream 4.10#196
Conversation
70d8140 to
1bdc825
Compare
1bdc825 to
edc2fbe
Compare
18ff0b7 to
a098f1a
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timflannagan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
c7b2907 to
c8a7ca3
Compare
|
/retest |
2 similar comments
|
/retest |
|
/retest |
3a347f6 to
ddbcc0b
Compare
Update the .github/workflows/quickstart.yml github action and replace the usage of `kubectl wait ...` with a function that waits until the various OLM component deployment resources are present and reporting an available status. Using `kubectl wait ...` is potentially problematic as it doesn't support waiting until the creation of that resource, so in the case the PackageServer deployment doesn't exist yet as the catalog/olm operators are still being setup, this action will fail as `kubectl wait ...` will return a non-zero exit code. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: b98ff9d1601b41847fb47445a8366a1145c7cbe6
Failing to fetch catalog content should not silently return an empty cache. Instead, it should fail outright with an error that indicates which catalog(s) could not be fetched. Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 6ab5f1634093c91d7027b9245a88ede7b807088b
Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 1e7e1cc81d5c3e0f2de2a06cb4315ea622371cbe
Update to containerd 1.4.8 Signed-off-by: Vu Dinh <vudinh@outlook.com> Upstream-repository: operator-registry Upstream-commit: aa44cbec0df254fb503a34384a85e197a7e68e6f
Update the doc/design/release.md documentation around how to generate the root CHANGELOG.md. Previously, when running into API rate limiting behaviors locally, the suggestion was to modify a variable in the Ruby gem package that no longer exists. Now, specify the --max-issues CLI flag to lower the number of API requests to the OLM repository. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 5c40752a9605669d34234bf18a93dba948b59439
…ull requests (#2299) Update the e2e-tests.yml github workflow and avoid running that action on PRs that only change the doc directory. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 939bf94f834181d60a713191f78b13b80c7bec0f
Signed-off-by: Evan <cordell.evan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 538b1315eace85e33df7b2893a85a000f8757349
Signed-off-by: Evan <cordell.evan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 44fc44daf778cd9d36d6b6eb8edf63ff5a202304
… the root fs (openshift#733) Update internal/declcfg/load.go and avoid processing any files that are named `.indexignore` when walking the declarative config index root filesystem. When validating declarative config directories, the .indexignore file was being processed and validated. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-registry Upstream-commit: 78f27b39dc098c2e56681d9a3d8e786aae95d4fe
Signed-off-by: Joe Lanford <joe.lanford@gmail.com> Upstream-repository: operator-registry Upstream-commit: a390f86b3ca429c9618a7c20a31406bc2bd6ed16
Signed-off-by: Ben Luddy <bluddy@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 3a565917233c72d098f3a60d9239f0e3c5b55f76
Signed-off-by: Daniel Messer <dmesser@redhat.com> Upstream-repository: operator-registry Upstream-commit: 70cec5728f5634fc696e13a0608dd7d01a170e12
… workflow (openshift#730) Update the test.yml test workflow and replace the `e2e-kind` job name with `e2e`. Before, the e2e test workflow had ran e2e tests against both kind and minikube clusters before the latter job was removed entirely. Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-registry Upstream-commit: ff2c921e414926a013f82448b7241bc84fc95372
namespaces Update the root Makefile and extend the e2e/olm target to explicitly configure the ginkgo options that gets filtered to the staging/operator-lifecycle-manager e2e target when running on OpenShift clusters. Signed-off-by: timflannagan <timflannagan@gmail.com>
…ertions (#2403) * test/e2e: Wrap flake-prone garbage collection tests in eventually assertions Update the test/e2e/gc_e2e_test.go and wrap any error-prone test blocks in eventually assertions to reduce the number of flakes that occur when attempting to create/update/delete/etc. Kubernetes resources during individual CI runs on these garbage collection specs. Signed-off-by: timflannagan <timflannagan@gmail.com> * test/e2e: Replace context.TODO() with context.Background() Upstream-repository: operator-lifecycle-manager Upstream-commit: 23d84fa7dedff7546f1622253aabeaeee7ec693a
Temporary workaround until openshift/operator-framework-olm#196 merged. Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
Temporary workaround until openshift/operator-framework-olm#196 merged. Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
Temporary workaround until openshift/operator-framework-olm#196 merged. Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
Temporary workaround until openshift/operator-framework-olm#196 merged. Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
…ach block (#2387) Signed-off-by: Daniel Sover <dsover@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: a94b10b8cf7f0b2632eebdbd4fe85dd16520b89e
Signed-off-by: Daniel Sover <dsover@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 4c3c8f1b1bf6c64271f81a4e64043a081c9d73b7
…419) This commit introduces a change to the e2e tests that rely on a grpc catalogSource that is stored in an off cluster registry. These tests originally required that the following happen within a minute: 1. The catalogSource is installed and ready to serve. 2. The contents of the bundle are unpacked and placed in an installPlan. 3. The CSV is installed and in the ready state. The tests will now wait for the catalogSource to be ready to serve before moving onto steps 2 and 3. Signed-off-by: Alexander Greene <greene.al1991@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 700d282adbe09cc0b5d84d70411addb7400f9f79
c4d17e0 to
a03f87c
Compare
|
/retest |
|
/retest |
4 similar comments
|
/retest |
|
/retest |
|
/retest |
|
/retest |
|
@timflannagan: PR needs rebase. DetailsInstructions 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. |
|
@timflannagan: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Splitting this out into more granular commit ranges. See #203 for more details. |
Temporary workaround until openshift/operator-framework-olm#196 merged. Signed-off-by: Artyom Lukianov <alukiano@redhat.com>
No description provided.