undercloud - IPv6 - router created by undercloud conflict with infrastructure router
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Harald Jensås |
Bug Description
---- When ----
Router is created for IPv6 provsioning network to quote code[1] comment:
"""
# If the subnet is IPv6 we need to start a router so that router
# advertisments are sent out for stateless IP addressing to work.
"""
---- Then ----
The router created using the subnet_id will automatically select the IP address configured as the subnets gateway when the router interface is added. This will cause a conflict when there is an actual router in the infrastructure.
One solution is to first create a port, and then attach that to the router.
But is this router really neccecary? Would'nt the router in the infrastructure be responsible for doing the router advertisements?
NOTE:
The code[1] is not idempotent, it will try to re-create the
router on each undercloud install re-run.
This should be fixed as well.
Changed in tripleo: | |
assignee: | nobody → Harald Jensås (harald-jensas) |
Fix proposed to branch: master /review. opendev. org/685030
Review: https:/