There is nothing more than a log message that we can do in upstream.
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1586025
Title:
metadata: review fallback to neutronclient on RPC messaging failure
Status in neutron:
Fix Released
Bug description:
Till Kilo we used neutronclient library to get data from neutron-
server to metadata agent. Since Kilo we correctly introduced rpc
communication between server and metadata agent - with fallback
mechanism for those who upgrade agents first. That could lead to
situation where server is still on Juno which don't have rpc api
needed by Kilo agent. In such situation, we start again using neutron-
client.
https://github.com/openstack/neutron/blob/stable/liberty/neutron/agent/metadata/agent.py#L131
The fallback mechanism stayed there and got to Liberty, where it's not
needed anymore. Also there is a problem here, because we fallback on
any exception that comes from rpc communication. So for new Liberty
deployments, that are not supposed to configure metadata agent with
credentials for neutron api (as since kilo it's not used), on any
error that happens on rpc, it switches to unconfigured neutron client
till metadata agent is restarted.
We should just remove the fallback mechanism as we did in Mitaka:
https://review.openstack.org/#/c/231065/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1586025/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
