From 3dc887fa78f8ada5265f3165e1931048496522b5 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Fri, 3 Sep 2021 13:55:27 -0700 Subject: [PATCH] Add release note upgrade version check handling change Change-Id: I0ade8663e4f3fcfb69ecc2ec0cd32df44fda57c3 --- ...ial-version-no-such-table-54c3c291050ae787.yaml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 releasenotes/notes/handle-initial-version-no-such-table-54c3c291050ae787.yaml diff --git a/releasenotes/notes/handle-initial-version-no-such-table-54c3c291050ae787.yaml b/releasenotes/notes/handle-initial-version-no-such-table-54c3c291050ae787.yaml new file mode 100644 index 0000000000..c05ba2aeed --- /dev/null +++ b/releasenotes/notes/handle-initial-version-no-such-table-54c3c291050ae787.yaml @@ -0,0 +1,14 @@ +--- +fixes: + - | + Fixes an issue in db schema version testing where objects with a initial + version, e.g. "1.0", are allowed to not already have their DB tables + pre-exist when performing the pre-upgrade compatability check for the + database. This allows the upgrade to proceed and update the database + schema without an explicit known list having to be maintained in Ironic. +other: + - | + Removes a ``NEW_MODELS`` internal list from the dbsync utility which + helped the tool navigate new models, however it was never used. Instead + the tool now utilizes the database version and appropriate base version + to make the appropriate decision in pre-upgrade checks.