Public bug reported:
Metaadata isolated configured. Network and subnet created - ( no --no-gateway
option but the network is not connected to a router - there is no router). VM
booted - metadata is OK and we have a static route passed to the VM.
Created a router and attached a network port to it ( same network) . Created a
new VM and still qdhcp will handle the metadata even though we have the network
configured with DG ( /var/lib/neutron/dhcp/XYZ/opts has a static route for
169.254.169.254 and passes it to the new VMs- This is OK ONLY before we added
the network to the router) . After dhcp agent reboot the route to qdhcp is
removed from /var/lib/neutron/dhcp/XYZ/opts and router will handle metadata.
I strongly believe that if we made no change in the dhcp-agent.ini file, agent
restart ( systemctl restart neutron-dhcp-agent) should not affect behavior in
any way.
Additionally,
The static route should be removed from /var/lib/neutron/dhcp/XYZ/opts right
after the network "XYZ" was added to the router.
BR
Alex
Version- Kilo
** Affects: neutron
Importance: Undecided
Status: New
** Tags: metadata
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1549860
Title:
neutron metadata- after adding a network port to a neutron router,
static route is still sent to new VMs
Status in neutron:
New
Bug description:
Metaadata isolated configured. Network and subnet created - ( no
--no-gateway option but the network is not connected to a router - there is no
router). VM booted - metadata is OK and we have a static route passed to the
VM.
Created a router and attached a network port to it ( same network) . Created
a new VM and still qdhcp will handle the metadata even though we have the
network configured with DG ( /var/lib/neutron/dhcp/XYZ/opts has a static route
for 169.254.169.254 and passes it to the new VMs- This is OK ONLY before we
added the network to the router) . After dhcp agent reboot the route to qdhcp
is removed from /var/lib/neutron/dhcp/XYZ/opts and router will handle metadata.
I strongly believe that if we made no change in the dhcp-agent.ini file,
agent restart ( systemctl restart neutron-dhcp-agent) should not affect
behavior in any way.
Additionally,
The static route should be removed from /var/lib/neutron/dhcp/XYZ/opts right
after the network "XYZ" was added to the router.
BR
Alex
Version- Kilo
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1549860/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
