desired azure cleanups
Bug #1615822 reported by
Scott Moser
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Won't Fix
|
Low
|
Brent Baude |
Bug Description
When doing some recent cleanups of azure datasource, we found a couple desires
a.) it'd be nice if cloud-init automatically used 'fabric' if no agent (waagent) was available.
b.) I didn't understand why we have a test test_exception_
if we failed to fetch data, why do we just log exception rather than raising error.
Changed in cloud-init: | |
status: | New → Confirmed |
importance: | Undecided → Low |
assignee: | nobody → Brent Baude (bbaude) |
Changed in cloud-init: | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
On 22/08/16 21:36, Launchpad Bug Tracker wrote: fetching_ fabric_ data_doesnt_ propagate
> b.) I didn't understand why we have a test test_exception_
> if we failed to fetch data, why do we just log exception rather than raising error.
09:15:33 Odd_Bloke | smoser: I haven't looked at it, but my fetching_ fabric_ data_doesnt_ propagate is sources. find_source, that isn't
recollection of test_exception_
that data sources shouldn't raise exceptions.
09:22:17 Odd_Bloke | Reading cloudinit.
true.
09:22:22 Odd_Bloke | But I believe that was the motivation behind it.
Also worth noting that we log the exception and immediately return
False, so the effect is identical to not catching it.