cfg.CONF.taas.enabled is not used
Bug #1501954 reported by
YAMAMOTO Takashi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tap-as-a-service |
Confirmed
|
Low
|
Unassigned |
Bug Description
the option seems to have no effect.
Changed in tap-as-a-service: | |
assignee: | nobody → lizhixin (lizhixin3016) |
Changed in tap-as-a-service: | |
assignee: | lizhixin (lizhixin3016) → Zhixin Li (lizhixin) |
Changed in tap-as-a-service: | |
assignee: | Zhixin Li (lizhixin) → nobody |
importance: | Undecided → Low |
status: | New → Confirmed |
To post a comment you must log in.
Isnt it because it is currently being created at one place, but not used anywhere?
reedip@ reedip- VirtualBox: /opt/stack/ tap-as- a-service$ grep -nr taas_enabled * taas/services/ taas/agents/ ovs/taas_ ovs_agent. py:44: self.taas_enabled = cfg.CONF. taas.enabled taas/services/ taas/agents/ ovs/taas_ ovs_agent. pyc matches reedip- VirtualBox: /opt/stack/ tap-as- a-service$
neutron_
Binary file neutron_
reedip@