Need to convince cloud-init we really want Ec2 datasource
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Low
|
Unassigned | ||
diskimage-builder |
Fix Released
|
Undecided
|
Simon Leinen |
Bug Description
cloud-init was recently changed to be more selective about the types of data source it wants to access. See https:/
When we add the "Ec2" datasource to images, we should also generate a workaround that suppresses the warning. According to the warning itself, this can be achieved by adding a file /etc/cloud/
#cloud-config
datasource:
Ec2:
strict_id: false
An alternative would be to live with the warnings, and hope that DIB users select other datasources in preference of Ec2, for example OpenStack and/or ConfigDrive.
Another option would be to convince the cloud-init developers that OpenStack clouds can be expected to provide the Ec2 metadata service, and that there's no need to issue warnings about that.
Related branches
- Server Team CI bot: Approve (continuous-integration)
- Chad Smith: Approve
- cloud-init Commiters: Pending requested
-
Diff: 373 lines (+318/-10)2 files modifiedcloudinit/sources/DataSourceEc2.py (+44/-10)
tests/unittests/test_datasource/test_ec2.py (+274/-0)
Changed in cloud-init: | |
importance: | Medium → Low |
Fix proposed to branch: master /review. openstack. org/457015
Review: https:/