Skip to content

Conversation

dtantsur
Copy link
Member

Ironic does not support downgrades, its dbsync script will fail.
Make exception for going from latest to a numeric version. The expected
scenario is a user following latest for some time, then deciding to
settle on a specific version once everything they need is available.

Depends on:

Signed-off-by: Dmitry Tantsur dtantsur@protonmail.com

@dtantsur dtantsur changed the title Disallow downgrades when an external database is used ⚠️ Disallow downgrades when an external database is used Mar 18, 2025
@metal3-io-bot metal3-io-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 18, 2025
@dtantsur dtantsur force-pushed the no-downgrade branch 3 times, most recently from 6fa465f to 12d89bd Compare March 18, 2025 15:10
@tuminoid
Copy link
Member

/hold
Since it contains the database PR too. We don't get this merged with that included. but as two separate ones.

@metal3-io-bot metal3-io-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 19, 2025
@dtantsur
Copy link
Member Author

/hold cancel

Rebased

@metal3-io-bot metal3-io-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 19, 2025
@elfosardo
Copy link
Member

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elfosardo

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:

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

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 19, 2025
@dtantsur dtantsur added this to the IrSO - v0.3 milestone Mar 21, 2025
Ironic does not support downgrades, its dbsync script will fail.
Make exception for going from latest to a numeric version. The expected
scenario is a user following latest for some time, then deciding to
settle on a specific version once everything they need is available.

Signed-off-by: Dmitry Tantsur <dtantsur@protonmail.com>
@tuminoid
Copy link
Member

Needs rebase?

@dtantsur
Copy link
Member Author

Needs rebase?

Not really, seems to be fresh?

@tuminoid
Copy link
Member

Needs rebase?

Not really, seems to be fresh?

That was reference to the golangci-lint issue we had. I thought it failed due the linter cleanup PR/version mismatch.

Copy link
Member

@tuminoid tuminoid left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@metal3-io-bot metal3-io-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 25, 2025
@metal3-io-bot metal3-io-bot merged commit 882535a into metal3-io:main Mar 25, 2025
14 checks passed
@dtantsur dtantsur deleted the no-downgrade branch March 25, 2025 09:22
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. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants