Skip to content

WIP: Sync latest#126

Closed
awgreene wants to merge 8 commits into
openshift:masterfrom
awgreene:sync-latest
Closed

WIP: Sync latest#126
awgreene wants to merge 8 commits into
openshift:masterfrom
awgreene:sync-latest

Conversation

@awgreene
Copy link
Copy Markdown
Contributor

@awgreene awgreene commented Jul 20, 2021

This PR was created to test a hunch that #122 is failing due to a bad values.yaml file.

joelanford and others added 7 commits July 19, 2021 12:09
…e negatives

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>

Upstream-repository: operator-registry
Upstream-commit: 95c5e3bca1ac3abb3bf00f6b7345ddbd047e1524
Signed-off-by: Ben Luddy <bluddy@redhat.com>

Upstream-repository: operator-lifecycle-manager
Upstream-commit: e731c70a5cd62ab1cab7658f1d17f810f525cd8e
Signed-off-by: Ankita Thomas <ankithom@redhat.com>

Upstream-repository: operator-registry
Upstream-commit: 9e88b877c8324d5fd027e512ad845b344cc4168a
Operator dependencies are expressed as properties, but there was
initially a notion of dependencies as distinct from properties. For
that reason, catalog-operator must support existing catalog images
that serve separate Bundle.dependencies and Bundle.properties fields
by translating the three legacy dependency types (olm.label,
olm.package, and olm.gvk) into their corresponding properties.

Signed-off-by: Ben Luddy <bluddy@redhat.com>

Upstream-repository: operator-lifecycle-manager
Upstream-commit: c918a85eb7ef0c1ea58ebf27fabd8d2393afe9b3
TLS can still be enabled via flags, but it now applies to all three
APIs since there is a single HTTP server per operator process.

The -profiling flag is deprecated and does nothing. The profiling APIs
are now always enabled, but they refuse to serve clients that do not
present a verifiable certificate (see the new flag -client-ca). This
effectively disables the profiling APIs when served over HTTP.

Co-authored-by: Vu Dinh <vudinh@outlook.com>
Co-authored-by: Alexander Greene <agreene@redhat.com>
Signed-off-by: Ben Luddy <bluddy@redhat.com>

Upstream-repository: operator-lifecycle-manager
Upstream-commit: f9381e0ce8e0addeb1abf55d44146a5e6e57074a
This line creates an info-level logger, writes a trace-level log to
it, and discards the logger reference. This looks like cruft and is
responsible for some heap churn.

Signed-off-by: Ben Luddy <bluddy@redhat.com>

Upstream-repository: operator-lifecycle-manager
Upstream-commit: 8c8b18bacbc8033ef9d2a8847e730b3aa17247e6
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 20, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awgreene

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci Bot requested review from benluddy and gallettilance July 20, 2021 21:35
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 20, 2021
@awgreene awgreene changed the title Sync latest WIP: Sync latest Jul 20, 2021
@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 20, 2021
@awgreene awgreene force-pushed the sync-latest branch 4 times, most recently from 8e05a67 to 2acdc65 Compare July 21, 2021 05:52
@ecordell
Copy link
Copy Markdown
Contributor

error running apply for deployment "openshift-operator-lifecycle-manager/olm-operator" (531 of 710): Deployment.apps "olm-operator" is invalid: spec.template.spec.containers[0].volumeMounts[2].name: Not found: "serving-cert"

Comment thread manifests/0000_50_olm_07-olm-operator.deployment.yaml Outdated
@awgreene
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-console-olm

@awgreene awgreene force-pushed the sync-latest branch 2 times, most recently from ca22f0d to 355d7d1 Compare July 21, 2021 14:20
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 21, 2021

@awgreene: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Rerun command
ci/prow/unit-registry 1e4a6be link /test unit-registry
ci/prow/e2e-aws-console-olm 1e4a6be link /test e2e-aws-console-olm
ci/prow/e2e-gcp 1e4a6be link /test e2e-gcp
ci/prow/e2e-aws-olm 1e4a6be link /test e2e-aws-olm

Full PR test history. Your PR dashboard.

Details

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.

@awgreene awgreene closed this Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants