Azure data source assumes network is driven via dhcpclient
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned |
Bug Description
The Azure data source assumes that the network is set up by dhcpclient. During cloud-init initialization the following traceback is generated:
Traceback (most recent call last):
File "/usr/lib/
fabric_data = metadata_func()
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
return shim.register_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
'http://{0}/machine/
File "/usr/lib/
self.
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
fallback_
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
content = util.load_
File "/usr/lib/
with open(fname, 'rb') as ifh:
FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → Medium |
On SUSE the option of interest is in /var/lib/ wicked/ lease-eth0- dhcp-ipv4. xml