Using dimensions always trigger container restart.
Bug #2070494 reported by
Pedro Henrique Pereira Martins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
kolla-ansible | Status tracked in Dalmatian | |||||
Antelope |
Fix Released
|
Medium
|
Unassigned | |||
Bobcat |
Fix Released
|
Medium
|
Unassigned | |||
Caracal |
Fix Released
|
Medium
|
Unassigned | |||
Dalmatian |
Fix Released
|
Medium
|
Pedro Henrique Pereira Martins |
Bug Description
When using short notations like `1g` or `512m` to define the
container dimensions, we are always getting the container to
being restarted in each kolla-ansible run, even with no real
changes in the container configs.
Changed in kolla-ansible: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/886500 /opendev. org/openstack/ kolla-ansible/ commit/ a086b780dc7884f 441683143400c94 1a9400c5a5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit a086b780dc7884f 441683143400c94 1a9400c5a5
Author: Pedro Henrique <email address hidden>
Date: Tue Jun 20 11:21:20 2023 -0300
Fix the docker container dimensions comparison for short notation
When using short notations like `1g` or `512m` to define the
container dimensions, we are always getting the container to
being restarted in each kolla-ansible run, even with no real
changes in the container configs.
Change-Id: Ic8e2dd42b95a8f 5c2141a820c5564 2a3ed7beabd
Closes-Bug: #2070494