glance-cache-cleaner/pruner is executed in multiple containers at the same time
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Takashi Kajinami |
Bug Description
Description
===========
When GlanceCacheEnabled is true, the following glance-cache commands are executed by the glance_api_cron container.
The glance_api_cron container is deployed on every controller node, thus if a deployment has multiple controller nodes, then the cron job can be executed at the exactly same timing in multiple nodes.
This is not ideal and can cause conflict/
Steps to reproduce
==================
* Deploy overcloud node with multiple controller nodes and GlanceCacheEnabled: true
* Check cron jobs in glance_api_cron container
Expected result
===============
* The glance-
Actual result
===============
* The glance-
Environment
===========
* N/A
Logs & Configs
==============
* N/A
Changed in tripleo: | |
importance: | Undecided → Medium |
assignee: | nobody → Takashi Kajinami (kajinamit) |
Changed in tripleo: | |
status: | New → In Progress |
tags: | added: wallaby-backport-potential |
Reviewed: https:/ /review. opendev. org/c/openstack /tripleo- heat-templates/ +/847112 /opendev. org/openstack/ tripleo- heat-templates/ commit/ 376a8a46c3ee898 639cab4016ba150 342cf83a1a
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 376a8a46c3ee898 639cab4016ba150 342cf83a1a
Author: Takashi Kajinami <email address hidden>
Date: Wed Jun 22 09:31:01 2022 +0900
Glance: Avoid simultaneous clean/pruner job
This change introduces randomized delays to cache clean/pruner job
commands so that these commands are not executed simultaneously in
multiple nodes.
Closes-Bug: #1979271 /review. opendev. org/846601 fe85e76206291be 50b77bfe6eb
Depends-on: https:/
Change-Id: Icf8727779de746