Merge ~smoser/cloud-init:bug/1649652-curtin-routes-rendered into cloud-init:master
Proposed by
Scott Moser
Status: | Merged |
---|---|
Merged at revision: | 9411d800b703a0c7d4e10138039ecaa765c91661 |
Proposed branch: | ~smoser/cloud-init:bug/1649652-curtin-routes-rendered |
Merge into: | cloud-init:master |
Diff against target: |
57 lines (+46/-0) 1 file modified
tests/unittests/test_net.py (+46/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
cloud-init Commiters | Pending | ||
Review via email: mp+313475@code.launchpad.net |
To post a comment you must log in.
There was an error fetching revisions from git servers. Please try again in a few minutes. If the problem persists, contact Launchpad support.
Mike,
Yeah, thats true.
The fix here does verify that the content is better than it was in that bug report though.
We need full round trip rendering and reading to do the whole thing the right way.
That said, the network config that was provided in the bug, and I think correctly simplified here, has static routes that are not attached to an interface. There is no specific link between the
'route' type and the subnet that it should be off of.
we could arguably work backwards and find the right subnet to hang the static route off of, but at the moment we dont do that. Additionally, there could well be two devices with an 'address' that would contain the route's 'gateway'.
Again, I agree that this test is minimalistic.
You have thoughts on what the route info should look like?
(we should probably move this discussion at least to the bug).