Cherry Pick: OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write #431

dtfranz · 2023-01-20T19:33:19Z

Cherry-pick of #429

OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write

Signed-off-by: dtfranz [email protected]

OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write Signed-off-by: dtfranz <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 2a49a4dddeb3e0fc38b44925bf9bd0d3931d4ff4

openshift-ci · 2023-01-20T19:33:22Z

@dtfranz: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Merge pull request #429 from dtfranz/metrics-map-mutex

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 · 2023-01-20T19:33:45Z

@dtfranz: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Cherry Pick: OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write

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-robot · 2023-01-20T19:33:47Z

@dtfranz: This pull request references Jira Issue OCPBUGS-5523, which is invalid:

expected the bug to target the "4.10.z" version, but it targets "4.13.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
expected Jira Issue OCPBUGS-5523 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Cherry-pick of #429

OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write

Signed-off-by: dtfranz [email protected]

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 · 2023-01-20T19:33:50Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dtfranz
Once this PR has been reviewed and has the lgtm label, please assign dinhxuanvu for approval by writing /assign @dinhxuanvu in a comment. For more information see the Kubernetes Code Review Process.

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

Details

Needs approval from an approver in each of these files:

OWNERS

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

openshift-ci · 2023-01-20T22:35:25Z

@dtfranz: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Cherry Pick: OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write

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-robot · 2023-01-20T22:35:25Z

@dtfranz: This pull request references Jira Issue OCPBUGS-5523, which is invalid:

expected the bug to target the "4.10.z" version, but it targets "4.13.0" instead
expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
expected Jira Issue OCPBUGS-5523 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

Details

In response to this:

Cherry-pick of #429

OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write

Signed-off-by: dtfranz [email protected]

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 · 2023-01-20T22:36:09Z

@dtfranz: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

Cherry Pick: OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write

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-robot · 2023-01-20T22:36:09Z

@dtfranz: This pull request references Jira Issue OCPBUGS-6260, which is invalid:

expected Jira Issue OCPBUGS-6260 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

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.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Cherry-pick of #429

OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write

Signed-off-by: dtfranz [email protected]

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.

dtfranz · 2023-01-20T22:38:52Z

/jira refresh

openshift-ci-robot · 2023-01-20T22:38:55Z

@dtfranz: This pull request references Jira Issue OCPBUGS-6260, which is invalid:

expected dependent Jira Issue OCPBUGS-5523 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-5523 to target a version in 4.11.0, 4.11.z, but it targets "4.13.0" 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.

Details

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.

awgreene · 2023-02-01T21:26:01Z

/retest
/jira refresh

openshift-ci-robot · 2023-02-01T21:26:04Z

@awgreene: This pull request references Jira Issue OCPBUGS-6260, which is invalid:

expected dependent Jira Issue OCPBUGS-5523 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is ON_QA instead
expected dependent Jira Issue OCPBUGS-5523 to target a version in 4.11.0, 4.11.z, but it targets "4.13.0" 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.

Details

In response to this:

/retest
/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.

perdasilva · 2023-02-03T09:09:54Z

/retest

perdasilva · 2023-02-03T14:06:54Z

/retest

openshift-ci · 2023-02-03T16:42:58Z

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

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-olm	`436e9ce`	link	true	`/test e2e-gcp-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.

dtfranz · 2023-02-03T18:57:51Z

Closing this PR in favor of #436 which was created successfully from auto cherry-pick. This PR was created manually since the cherry-pick failed initially.

openshift-ci-robot · 2023-02-03T18:57:54Z

@dtfranz: This pull request references Jira Issue OCPBUGS-6260. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Cherry-pick of #429

OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write

Signed-off-by: dtfranz [email protected]

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.

…penshift#431) Upstream-repository: api Upstream-commit: 48d8867b4e27cf90fef4b60037952a8e40a296c7

Merge pull request openshift#429 from dtfranz/metrics-map-mutex

436e9ce

OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write Signed-off-by: dtfranz <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 2a49a4dddeb3e0fc38b44925bf9bd0d3931d4ff4

dtfranz changed the title ~~Merge pull request #429 from dtfranz/metrics-map-mutex~~ Cherry Pick: OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write Jan 20, 2023

openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 20, 2023

openshift-ci bot requested review from anik120 and joelanford January 20, 2023 19:33

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 20, 2023

dtfranz changed the title ~~Cherry Pick: OCPBUGS-5523: Catalog, fatal error: concurrent map read and map write~~ Cherry Pick: OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write Jan 20, 2023

dtfranz closed this Feb 3, 2023

grokspawn pushed a commit to grokspawn/operator-framework-olm that referenced this pull request Jul 15, 2025

(ci) - Add stale config to close PRs and issues which are inactivity (o…

f18d459

…penshift#431) Upstream-repository: api Upstream-commit: 48d8867b4e27cf90fef4b60037952a8e40a296c7

grokspawn pushed a commit to grokspawn/operator-framework-olm that referenced this pull request Jul 15, 2025

(ci) - Add stale config to close PRs and issues which are inactivity (o…

fafe73a

…penshift#431) Upstream-repository: api Upstream-commit: 48d8867b4e27cf90fef4b60037952a8e40a296c7

grokspawn pushed a commit to grokspawn/operator-framework-olm that referenced this pull request Jul 15, 2025

(ci) - Add stale config to close PRs and issues which are inactivity (o…

cc6a373

…penshift#431) Upstream-repository: api Upstream-commit: 48d8867b4e27cf90fef4b60037952a8e40a296c7

grokspawn pushed a commit to grokspawn/operator-framework-olm that referenced this pull request Jul 16, 2025

(ci) - Add stale config to close PRs and issues which are inactivity (o…

34fa60d

…penshift#431) Upstream-repository: api Upstream-commit: 48d8867b4e27cf90fef4b60037952a8e40a296c7

Cherry Pick: OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write #431

Cherry Pick: OCPBUGS-6260: Catalog, fatal error: concurrent map read and map write #431

Uh oh!

Conversation

dtfranz commented Jan 20, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci bot commented Jan 20, 2023

Uh oh!

openshift-ci bot commented Jan 20, 2023

Uh oh!

openshift-ci-robot commented Jan 20, 2023

Uh oh!

openshift-ci bot commented Jan 20, 2023

Uh oh!

openshift-ci bot commented Jan 20, 2023

Uh oh!

openshift-ci-robot commented Jan 20, 2023

Uh oh!

openshift-ci bot commented Jan 20, 2023

Uh oh!

openshift-ci-robot commented Jan 20, 2023

Uh oh!

dtfranz commented Jan 20, 2023

Uh oh!

openshift-ci-robot commented Jan 20, 2023

Uh oh!

awgreene commented Feb 1, 2023

Uh oh!

openshift-ci-robot commented Feb 1, 2023

Uh oh!

perdasilva commented Feb 3, 2023

Uh oh!

perdasilva commented Feb 3, 2023

Uh oh!

openshift-ci bot commented Feb 3, 2023

Uh oh!

dtfranz commented Feb 3, 2023

Uh oh!

openshift-ci-robot commented Feb 3, 2023

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

dtfranz commented Jan 20, 2023 •

edited

Loading