juju does not propogate maas static routes in containers
Bug #1653708 reported by
Richard Harding
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.1 |
Fix Released
|
High
|
John A Meinel |
Bug Description
MAAS supports adding static route information (defined in a MAAS' subnet) and Juju does not handle any form of propogating that information to the containers that Juju creates and manages.
Changed in juju: | |
milestone: | none → 2.2.0 |
tags: | added: 4010 |
Changed in juju: | |
milestone: | 2.2.0 → 2.1.1 |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → John A Meinel (jameinel) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Changed in juju: | |
milestone: | 2.2-alpha2 → 2.2-alpha1 |
status: | Fix Released → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Static routes seem like a very bad outcome when the underlying network is dynamic. People will be adding subnets and spaces all the time, machines (and containers) need to discover that, or you will be stuck with having to know what a machine knew at the time of deployment :)
So I thought we had agreed that MAAS would offer a very simple source of routes (RIP?) and hosts would be told to listen to that. Which would mean that routes could be updated dynamically.