Improper configuration of security group driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
Won't Fix
|
Low
|
Sergey Kolekonov | ||
5.0.x |
Won't Fix
|
Low
|
Sergey Kolekonov |
Bug Description
{
"build_id": "2014-07-
"ostf_sha": "9c0454b2197756
"build_number": "375",
"auth_
"api": "1.0",
"nailgun_sha": "aed9ca4c68fee0
"production": "docker",
"fuelmain_sha": "09acf940bc60b8
"astute_sha": "b16efcec6b4af1
"feature_
"mirantis"
],
"release": "5.1",
"fuellib_sha": "0e60fb01a46006
}
Symptoms:
openvswitch-
WARNING neutron.
ion doesn't match with enable_
The agent is started with parameters --config-
Grepping over configs give the following:
neutron.
plugin.
plugins/
When agent is started the value from plugin.ini overwrites value from neutron.conf producing wrong configuration:
DEBUG neutron.
nt.firewall.
tags: | added: neutron |
Changed in mos: | |
milestone: | none → 5.1 |
assignee: | nobody → MOS Neutron (mos-neutron) |
importance: | Undecided → High |
Changed in mos: | |
assignee: | MOS Neutron (mos-neutron) → Sergey Kolekonov (skolekonov) |
no longer affects: | mos/6.0.x |
Changed in mos: | |
status: | Confirmed → Won't Fix |
no longer affects: | mos/5.1.x |
Well, for controller, it should not be enabled. I guess. And for compute nodes it is overriden by plugin configuration. So why is this bug set to High? Is it breaking anything? It looks like - not. So I am lowering the priority to low as it is only a matter of artifacts in log files.