Fix log owner on computes during overcloud deploy runs

[1] switched to run nova-manage discovery as non root user. In case of
updates there can be already a nove-manage log owned by root from previous
runs. This change make sure we change the owner of nova-manage log to
nova:nova on overcloud deploy runs on the computes

[1] https://review.opendev.org/#/c/652039/13/deployment/nova/nova-compute-container-puppet.yaml

Closes-Bug: #1832482

Change-Id: Ie6d3f5262f7eb20ef92b07f2f359d88cb77b8752
This commit is contained in:
Martin Schuppert 2019-06-12 12:11:56 +02:00
parent 49f16c09db
commit ccabc8f8e6
2 changed files with 11 additions and 0 deletions

View File

@ -559,6 +559,8 @@ outputs:
- {get_attr: [ContainersCommon, container_config_scripts]}
- {get_attr: [NovaComputeCommon, container_config_scripts]}
docker_config:
step_2:
get_attr: [NovaLogging, docker_config, step_2]
step_3:
nova_statedir_owner:
image: &nova_compute_image {get_param: DockerNovaComputeImage}

View File

@ -0,0 +1,9 @@
---
fixes:
- |
[1] switched to run nova-manage discovery as non root user. In case of
updates there can be already a nove-manage log owned by root from previous
runs. This change make sure we change the owner of nova-manage log to
nova:nova on overcloud deploy runs on the computes
[1] https://review.opendev.org/#/c/652039/13/deployment/nova/nova-compute-container-puppet.yaml