Merge ~jocha/cloud-init:jocha-reboot-bugfix-2 into cloud-init:master
Status: | Merged |
---|---|
Approved by: | Chad Smith |
Approved revision: | 40962b66cd13f48fbf21b46f9acc25bed1cd0d42 |
Merge reported by: | Chad Smith |
Merged at revision: | aae494c39f4c6f625e7409ca262e657d085dd5d1 |
Proposed branch: | ~jocha/cloud-init:jocha-reboot-bugfix-2 |
Merge into: | cloud-init:master |
Diff against target: |
286 lines (+134/-57) 2 files modified
cloudinit/sources/DataSourceAzure.py (+15/-6) tests/unittests/test_datasource/test_azure.py (+119/-51) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Chad Smith | Approve | ||
Server Team CI bot | continuous-integration | Approve | |
Douglas Jordan | Pending | ||
Review via email: mp+344192@code.launchpad.net |
This proposal supersedes a proposal from 2018-04-24.
Commit message
azure: Add reported ready marker file.
This change is for Azure VM Preprovisioning. A bug was found when after
azure VMs report ready the first time, during the time when VM is polling
indefinitely for the new ovf-env.xml from Instance Metadata Service
(IMDS), if a reboot happens, we send another report ready signal to the
fabric, which deletes the reprovisioning data on the node.
This marker file is used to fix this issue so that we will only send a
report ready signal to the fabric when no marker file is present. Then,
create a marker file so that when a reboot does occur, we check if a
marker file has been created and decide whether we would like to send the
repot ready signal.
LP: #1765214
I think I messed up my previous branch (jocha- reboot- bugfix) when I did "git pull --rebase" as it had all the commits from others listed as unmerged commits on my branch (jocha- reboot- bugfix) . So I decided to start a new branch (jocha- reboot- bugfix- 2) of the latest master and cherry picked my changes on top of it.
Thanks Chad for the feedback. I agree with all the comments and have resolved it.