summaryrefslogtreecommitdiff
path: root/releasenotes/notes/fix-step-priority-overrides-edecff2a6c68dcac.yaml
diff options
context:
space:
mode:
authorJulia Kreger <juliaashleykreger@gmail.com>2023-03-06 10:48:07 -0800
committerMark Goddard <mark@stackhpc.com>2023-03-15 15:42:54 +0000
commit978a09f08d8e8372739f9a6436431815c1a96237 (patch)
treed4602af9f7519bf41e27c7b5b0f2c8fc674988c0 /releasenotes/notes/fix-step-priority-overrides-edecff2a6c68dcac.yaml
parent3c248bbb89ad8fc193279bd2052ed70f919f4b8f (diff)
downloadironic-978a09f08d8e8372739f9a6436431815c1a96237.tar.gz
Fix online upgrades for Bios/Traitsstable/xena
... And tags, but nobody uses tags since it is not available via the API. Anyhow, the online upgrade code was written under the assumption that *all* tables had an "id" column. This is not always true in the ironic data model for tables which started as pure extensions of the Nodes table, and fails in particular when: 1) A database row has data stored in an ealier version of the object 2) That same object gets a version upgrade. In the case which discovered this, BIOSSetting was added at version 1.0, and later updated to include additional fields which incremented the version to 1.1. When the upgrade went to evaluate and iterate through the fields, the command failed because the table was designed around "node_id" instead of "id". Story: 2010632 Task: 47590 Change-Id: I7bec6cfacb9d1558bc514c07386583436759f4df (cherry picked from commit cbe5f86ce7c100f834701cf43f7b9b1bfdfb9ea5)
Diffstat (limited to 'releasenotes/notes/fix-step-priority-overrides-edecff2a6c68dcac.yaml')
0 files changed, 0 insertions, 0 deletions