diff options
| author | Dmitry Tantsur <dtantsur@protonmail.com> | 2020-09-25 14:09:43 +0200 |
|---|---|---|
| committer | Dmitry Tantsur <dtantsur@protonmail.com> | 2020-09-28 17:15:28 +0200 |
| commit | d3872cfcdd26f6c46d262588e0d79eeab5d4be1c (patch) | |
| tree | d50ece9365d33f85dfb0011c2b8194f83a13a186 /releasenotes | |
| parent | ac19e6050d6347c51841d09b2e84fb2833b84aa5 (diff) | |
| download | ironic-d3872cfcdd26f6c46d262588e0d79eeab5d4be1c.tar.gz | |
Fix a race condition in the hash ring code
We're handling hash rings and updated_at differently: one
is stored on the class level, the other - on instance. Apparently,
there is a race there, resulting in updated_at never updated.
Store hash rings and updated_at in one tuple, so that they're
always loaded and stored together.
Also remove double loading of the hash ring in _get_ring that
could contribute to the problem.
Change-Id: Ib659014e07549ae3d5ec7e69da318301f5994ca8
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/hash-ring-6ce212ab86c2592d.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/hash-ring-6ce212ab86c2592d.yaml b/releasenotes/notes/hash-ring-6ce212ab86c2592d.yaml new file mode 100644 index 000000000..ee75d93cc --- /dev/null +++ b/releasenotes/notes/hash-ring-6ce212ab86c2592d.yaml @@ -0,0 +1,5 @@ +--- +fixes: + - | + Fixes a potential race in the hash ring code that could result in the + hash rings never updated after their initial load. |