summaryrefslogtreecommitdiff
path: root/cloudinit/config
diff options
context:
space:
mode:
authorChris Patterson <cpatterson@microsoft.com>2022-01-20 17:46:49 -0500
committerGitHub <noreply@github.com>2022-01-20 16:46:49 -0600
commit6f0e881847822223fb96925b229322120772fa94 (patch)
tree8d42fdf8a9de7b88b8f16d27a32e54839ddb3b73 /cloudinit/config
parent109c2bbd9eb9a3b0612098bb010317191c436ad2 (diff)
downloadvyos-cloud-init-6f0e881847822223fb96925b229322120772fa94.tar.gz
vyos-cloud-init-6f0e881847822223fb96925b229322120772fa94.zip
sources/azure: drop unused case in _report_failure() (#1200)
According to the documentation in the tests: ``` We expect 3 calls to report_failure_to_fabric, because we try 3 different methods of calling report failure. The different methods are attempted in the following order: 1. Using cached ephemeral dhcp context to report failure to Azure 2. Using new ephemeral dhcp to report failure to Azure 3. Using fallback lease to report failure to Azure ``` Case 1 and 2 make sense. If networking is established, use it. Should failure occur using current network configuration, retry with fresh DHCP. Case 3 suggests that we can fall back to a lease file and retry. Given that: 1. The wireserver address has never changed to date. 2. The wireserver address should be in the DHCP lease. 3. Parsing the lease file does not improve connectivity over the prior attempts. ...we can safely remove this case without regression. Signed-off-by: Chris Patterson <cpatterson@microsoft.com>
Diffstat (limited to 'cloudinit/config')
0 files changed, 0 insertions, 0 deletions