diff options
| author | Scott Moser <smoser@ubuntu.com> | 2018-12-03 22:06:47 +0000 |
|---|---|---|
| committer | Server Team CI Bot <josh.powers+server-team-bot@canonical.com> | 2018-12-03 22:06:47 +0000 |
| commit | adbd950af07a4b613a14bd83049915abdd6ca348 (patch) | |
| tree | a99770cbb3f7a92fb5752e706ea4bb6928a833cf /cloudinit/tests/test_dhclient_hook.py | |
| parent | cb44ad6f42ac015d7d8eaf2ab0bb5ab125ed04b6 (diff) | |
| download | vyos-cloud-init-adbd950af07a4b613a14bd83049915abdd6ca348.tar.gz vyos-cloud-init-adbd950af07a4b613a14bd83049915abdd6ca348.zip | |
NoCloud: Allow top level 'network' key in network-config.
NoCloud's 'network-config' file was originally expected to contain
network configuration without the top level 'network' key. This was
because the file was named 'network-config' so specifying 'network'
seemed redundant.
However, JuJu is currently providing a top level 'network' config when
it tries to disable networking ({"network": {"config": "disabled"}).
Other users have also been surprised/confused by the fact that
a network config in /etc/cloud/cloud.cfg.d/network.cfg differed from
what was expected in 'network-config'.
LP: #1798117
Diffstat (limited to 'cloudinit/tests/test_dhclient_hook.py')
0 files changed, 0 insertions, 0 deletions