Merge ~jasonzio/cloud-init:handleUnsetNetCfg into cloud-init:master
Status: | Merged |
---|---|
Approved by: | Ryan Harper |
Approved revision: | e0463108ae336485771ea5527a0f6aa3d691b7ba |
Merge reported by: | Server Team CI bot |
Merged at revision: | not available |
Proposed branch: | ~jasonzio/cloud-init:handleUnsetNetCfg |
Merge into: | cloud-init:master |
Diff against target: |
13 lines (+1/-1) 1 file modified
cloudinit/sources/DataSourceAzure.py (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Ryan Harper | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Review via email: mp+365377@code.launchpad.net |
Commit message
Azure: Treat _unset network configuration as if it were absent
When the Azure datasource persists all of its metadata to the
instance directory, it deliberately sets the self.network_config
value to be the sources.UNSET value. The goal is to ensure that
each time the system boots, fresh network configuration data is
fetched from the cloud platform so that any control plane changes
will take effect. When a VM is first created, there's no pickled
instance to restore, so self._network_
in self.network_
suffered from LP: #1801364 which prevented ds from being stored
in obj.pkl in the instance directory, so subsequent reboots always
regenerated their network configuration.
Commit 0dc3a77f41f4544
new bug in which self.network_
self._network_
the config was unpickled, that value was _unset, thus breaking
the assumption.
LP: #1823084
PASSED: Continuous integration, rev:e0463108ae3 36485771ea5527a 0f6aa3d691b7ba /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 659/
https:/
Executed test runs:
SUCCESS: Checkout
SUCCESS: Unit & Style Tests
SUCCESS: Ubuntu LTS: Build
SUCCESS: Ubuntu LTS: Integration
IN_PROGRESS: Declarative: Post Actions
Click here to trigger a rebuild: /jenkins. ubuntu. com/server/ job/cloud- init-ci/ 659/rebuild
https:/