mariadb_recovery didn't set restart policy when recreate mariadb container.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla-ansible |
Fix Released
|
High
|
Mark Goddard | ||
Rocky |
Fix Released
|
High
|
Mark Goddard | ||
Stein |
Fix Released
|
High
|
Mark Goddard | ||
Train |
Fix Released
|
High
|
Mark Goddard | ||
Ussuri |
Fix Released
|
High
|
Mark Goddard |
Bug Description
In default, every Openstack container will set restart policy, and the default value is 'unless-stopped' if not change restart policy value inside all.yml
When doing mariadb_recovery process, the container will re-create and start new mariadb process. But we found that the re-created container didn't set restart policy when check mariadb container using docker inspect.
Expected result after mariadb_recovery:
"RestartPolicy": {
"Name": "unless-stopped",
"MaximumRet
},
Actual result after mariadb_recovery:
"RestartPolicy": {
"Name": "",
"MaximumRet
},
OS: Ubuntu 18.04
Docker version: 19.03.3
Kolla-Ansible version: stable/rocky
Docker image install type: source
Changed in kolla-ansible: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in kolla-ansible: | |
milestone: | 9.0.0 → none |
Fix proposed to branch: master /review. opendev. org/693329
Review: https:/