OVS based security groups parameter not populated correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Kamil Sambor |
Bug Description
Description of problem:
When deploying the overcloud I used a yaml file that contains parameters related to neutron that needs to be updated on the overcloud nodes:
parameter_defaults:
NeutronServ
NeutronOVSF
What happens is that NeutronOVSFirew
/etc/neutron/
/etc/neutron/
instead on one:
/etc/neutron/
Version-Release number of selected component (if applicable):
[root@undercloud-0 ~]# rpm -qa | grep -i neutron
python-
openstack-
puppet-
openstack-
python2-
openstack-
openstack-
python2-
python2-
[root@undercloud-0 ~]# rpm -qa | grep tripleo
openstack-
openstack-
openstack-
ansible-
openstack-
openstack-
puppet-
openstack-
python-
How reproducible:
100%
Steps to Reproduce:
1. before deploying the overcloud add the following to a yaml file and add it to the deploy command using -e <path to file>
parameter_defaults:
NeutronServ
NeutronOVSF
2. Run the overcloud deploy
3.
Actual results:
duplicate parameters with different values applied to different configuration files
Expected results:
only one parameter change in only one file with the correct value
Additional info:
Changed in tripleo: | |
assignee: | nobody → Kamil Sambor (ksambor) |
Changed in tripleo: | |
importance: | Undecided → Medium |
milestone: | none → rocky-rc2 |
tags: | added: rocky-backport-potential |
Fix proposed to branch: master /review. openstack. org/597387
Review: https:/