Skip to content

OCPBUGS-42114: add optional schema migrations; default to olm.bundle.object instead of olm.csv.metadata#874

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
perdasilva:perdasilva/bugfix/OCPBUGS-42114
Sep 25, 2024
Merged

OCPBUGS-42114: add optional schema migrations; default to olm.bundle.object instead of olm.csv.metadata#874
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.15from
perdasilva:perdasilva/bugfix/OCPBUGS-42114

Conversation

@perdasilva
Copy link
Copy Markdown
Contributor

Fix-up of #870

Allow disabling of migrations for bundles and sqlite DBs
intro new migrations package
schema migration optional; default to olm.bundle.object
review resolutions
use a type to protect migration interactions
review revisions

Upstream-repository: operator-registry
Upstream-commit: c80e8751e716c069017b55279a0f29d0254d426a

…of olm.csv.metadata (#1384)

* Allow disabling of migrations for bundles and sqlite DBs

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

* intro new migrations package

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

* schema migration optional; default to olm.bundle.object

Signed-off-by: Jordan Keister <jordan@nimblewidget.com>

* review resolutions

Signed-off-by: Jordan Keister <jordan@nimblewidget.com>

* use a type to protect migration interactions

Signed-off-by: Jordan Keister <jordan@nimblewidget.com>

* review revisions

Signed-off-by: Jordan Keister <jordan@nimblewidget.com>

---------

Signed-off-by: Joe Lanford <joe.lanford@gmail.com>
Signed-off-by: Jordan Keister <jordan@nimblewidget.com>
Co-authored-by: Joe Lanford <joe.lanford@gmail.com>
Upstream-repository: operator-registry
Upstream-commit: c80e8751e716c069017b55279a0f29d0254d426a
Signed-off-by: Per Goncalves da Silva <pegoncal@redhat.com>
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 24, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-42114, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-41540 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-41540 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

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

Details

In response to this:

Fix-up of #870

Allow disabling of migrations for bundles and sqlite DBs
intro new migrations package
schema migration optional; default to olm.bundle.object
review resolutions
use a type to protect migration interactions
review revisions

Upstream-repository: operator-registry
Upstream-commit: c80e8751e716c069017b55279a0f29d0254d426a

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2024
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 24, 2024

@perdasilva: all tests passed!

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-sigs/prow repository. I understand the commands that are listed here.

@emmajiafan
Copy link
Copy Markdown

/lgtm
/label qe-approved
/label cherry-pick-approved

@openshift-ci openshift-ci Bot added qe-approved Signifies that QE has signed off on this PR cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Sep 25, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@perdasilva: This pull request references Jira Issue OCPBUGS-42114, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-41540 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-41540 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jfan@redhat.com), skipping review request.

Details

In response to this:

Fix-up of #870

Allow disabling of migrations for bundles and sqlite DBs
intro new migrations package
schema migration optional; default to olm.bundle.object
review resolutions
use a type to protect migration interactions
review revisions

Upstream-repository: operator-registry
Upstream-commit: c80e8751e716c069017b55279a0f29d0254d426a

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 25, 2024
@perdasilva
Copy link
Copy Markdown
Contributor Author

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 25, 2024
@openshift-merge-bot openshift-merge-bot Bot merged commit 2a0924f into openshift:release-4.15 Sep 25, 2024
@openshift-ci-robot
Copy link
Copy Markdown

@perdasilva: Jira Issue OCPBUGS-42114: All pull requests linked via external trackers have merged:

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

Details

In response to this:

Fix-up of #870

Allow disabling of migrations for bundles and sqlite DBs
intro new migrations package
schema migration optional; default to olm.bundle.object
review resolutions
use a type to protect migration interactions
review revisions

Upstream-repository: operator-registry
Upstream-commit: c80e8751e716c069017b55279a0f29d0254d426a

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.15.0-202409251138.p0.g2a0924f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Copy Markdown
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.15.0-202409251138.p0.g2a0924f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Copy Markdown
Contributor

Fix included in accepted release 4.15.0-0.nightly-2024-09-26-223722

@grokspawn
Copy link
Copy Markdown
Contributor

/cherrypick release-4.14

@openshift-cherrypick-robot
Copy link
Copy Markdown

@grokspawn: #874 failed to apply on top of branch "release-4.14":

Applying: add optional schema migrations; default to olm.bundle.object instead of olm.csv.metadata (#1384)
Using index info to reconstruct a base tree...
M	staging/operator-registry/alpha/action/migrate.go
M	staging/operator-registry/alpha/action/migrate_test.go
M	staging/operator-registry/alpha/action/render.go
M	staging/operator-registry/alpha/action/render_test.go
M	staging/operator-registry/alpha/template/semver/semver.go
M	staging/operator-registry/cmd/opm/alpha/template/basic.go
M	staging/operator-registry/cmd/opm/alpha/template/semver.go
M	staging/operator-registry/cmd/opm/migrate/cmd.go
M	staging/operator-registry/cmd/opm/render/cmd.go
M	staging/operator-registry/pkg/api/api_to_model.go
M	staging/operator-registry/pkg/registry/registry_to_model.go
M	staging/operator-registry/pkg/server/server_test.go
M	vendor/github.com/operator-framework/operator-registry/alpha/action/migrate.go
M	vendor/github.com/operator-framework/operator-registry/alpha/action/render.go
M	vendor/github.com/operator-framework/operator-registry/alpha/template/semver/semver.go
M	vendor/github.com/operator-framework/operator-registry/cmd/opm/alpha/template/basic.go
M	vendor/github.com/operator-framework/operator-registry/cmd/opm/alpha/template/semver.go
M	vendor/github.com/operator-framework/operator-registry/cmd/opm/migrate/cmd.go
M	vendor/github.com/operator-framework/operator-registry/cmd/opm/render/cmd.go
M	vendor/github.com/operator-framework/operator-registry/pkg/api/api_to_model.go
M	vendor/github.com/operator-framework/operator-registry/pkg/registry/registry_to_model.go
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
Auto-merging vendor/github.com/operator-framework/operator-registry/pkg/registry/registry_to_model.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/pkg/registry/registry_to_model.go
Auto-merging vendor/github.com/operator-framework/operator-registry/pkg/api/api_to_model.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/pkg/api/api_to_model.go
Auto-merging vendor/github.com/operator-framework/operator-registry/cmd/opm/render/cmd.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/cmd/opm/render/cmd.go
Auto-merging vendor/github.com/operator-framework/operator-registry/cmd/opm/migrate/cmd.go
Auto-merging vendor/github.com/operator-framework/operator-registry/cmd/opm/alpha/template/semver.go
Auto-merging vendor/github.com/operator-framework/operator-registry/cmd/opm/alpha/template/basic.go
Auto-merging vendor/github.com/operator-framework/operator-registry/alpha/template/semver/semver.go
Auto-merging vendor/github.com/operator-framework/operator-registry/alpha/action/render.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/alpha/action/render.go
Auto-merging vendor/github.com/operator-framework/operator-registry/alpha/action/migrate.go
CONFLICT (content): Merge conflict in vendor/github.com/operator-framework/operator-registry/alpha/action/migrate.go
Auto-merging staging/operator-registry/pkg/server/server_test.go
CONFLICT (content): Merge conflict in staging/operator-registry/pkg/server/server_test.go
Auto-merging staging/operator-registry/pkg/registry/registry_to_model.go
CONFLICT (content): Merge conflict in staging/operator-registry/pkg/registry/registry_to_model.go
Auto-merging staging/operator-registry/pkg/api/api_to_model.go
CONFLICT (content): Merge conflict in staging/operator-registry/pkg/api/api_to_model.go
Auto-merging staging/operator-registry/cmd/opm/render/cmd.go
CONFLICT (content): Merge conflict in staging/operator-registry/cmd/opm/render/cmd.go
Auto-merging staging/operator-registry/cmd/opm/migrate/cmd.go
Auto-merging staging/operator-registry/cmd/opm/alpha/template/semver.go
Auto-merging staging/operator-registry/cmd/opm/alpha/template/basic.go
Auto-merging staging/operator-registry/alpha/template/semver/semver.go
Auto-merging staging/operator-registry/alpha/action/render_test.go
CONFLICT (content): Merge conflict in staging/operator-registry/alpha/action/render_test.go
Auto-merging staging/operator-registry/alpha/action/render.go
CONFLICT (content): Merge conflict in staging/operator-registry/alpha/action/render.go
Auto-merging staging/operator-registry/alpha/action/migrate_test.go
CONFLICT (content): Merge conflict in staging/operator-registry/alpha/action/migrate_test.go
Auto-merging staging/operator-registry/alpha/action/migrate.go
CONFLICT (content): Merge conflict in staging/operator-registry/alpha/action/migrate.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 add optional schema migrations; default to olm.bundle.object instead of olm.csv.metadata (#1384)

Details

In response to this:

/cherrypick release-4.14

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-sigs/prow repository.

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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.