According to Sergey Belous it may be caused by the following commit (which we have in 9.1):
rpodolyaka@rpodolyaka-pc:~/src/neutron$ git branch -a --contains e0f46f19f79169eaa63b33745233a4706b870b66
remotes/gerrit/stable/mitaka
remotes/mirantis/9.0/mitaka
remotes/mirantis/stable/mitaka
remotes/origin/stable/mitaka
rpodolyaka@rpodolyaka-pc:~/src/neutron$ git show e0f46f19f79169eaa63b33745233a4706b870b66
commit e0f46f19f79169eaa63b33745233a4706b870b66
Author: Miguel Lavalle <email address hidden>
Date: Sun May 1 23:51:23 2016 +0000
Don't load DNS integration in l3_router_plugin
In this patchset we stop the l3_router_plugin from loading the DNS integration
extension. The DNS integration extension should only be configured by the
operator by adding 'dns' to the 'extension_driver' list in ml2_conf.ini
Change-Id: I1321d9821973fe918005a8c2f3dd751af9affe38
Closes-Bug: #1574694
(cherry picked from commit 56962922cc439409bcecd808a1e9bbec2c3756f7)
In other words, this very extension was enabled by chance prior to 9.1. Instead operators are expected to explicitly enable it in ml2_conf.ini. Now that we've fixed this in 9.1, it affects mixed 9.0/9.1 environments.
The workaround is to explicitly enable this extension on all controller nodes.
According to Sergey Belous it may be caused by the following commit (which we have in 9.1):
rpodolyaka@ rpodolyaka- pc:~/src/ neutron$ git branch -a --contains e0f46f19f79169e aa63b33745233a4 706b870b66 gerrit/ stable/ mitaka mirantis/ 9.0/mitaka mirantis/ stable/ mitaka origin/ stable/ mitaka rpodolyaka- pc:~/src/ neutron$ git show e0f46f19f79169e aa63b33745233a4 706b870b66 aa63b33745233a4 706b870b66
remotes/
remotes/
remotes/
remotes/
rpodolyaka@
commit e0f46f19f79169e
Author: Miguel Lavalle <email address hidden>
Date: Sun May 1 23:51:23 2016 +0000
Don't load DNS integration in l3_router_plugin
In this patchset we stop the l3_router_plugin from loading the DNS integration
extension. The DNS integration extension should only be configured by the
operator by adding 'dns' to the 'extension_driver' list in ml2_conf.ini
Change-Id: I1321d9821973fe 918005a8c2f3dd7 51af9affe38 9bcecd808a1e9bb ec2c3756f7)
Closes-Bug: #1574694
(cherry picked from commit 56962922cc43940
In other words, this very extension was enabled by chance prior to 9.1. Instead operators are expected to explicitly enable it in ml2_conf.ini. Now that we've fixed this in 9.1, it affects mixed 9.0/9.1 environments.
The workaround is to explicitly enable this extension on all controller nodes.