The issue there was that if the datasource persisted an object; then init-net stage would
use the existing object on disk and not use the fallback path.
For OVF, at local time, it will run _get_data over the datasource list, which after reboot per this bug, it not return True; so I believe then that the fallback path should trigger as expected.
For Ec2 or other datasource which do persist objects it's not clear what a fallback scenario looks like.
@Pengpeng
Have you tried testing this bug with PR #229 applied?
I suspect that it might just work since DataSourceOVF does not persist an obj.pkl
Per comment:
https:/ /github. com/canonical/ cloud-init/ pull/229/ commits/ 82d039b0496902c eef4e73586e5332 95903e2e31# r397500586
The issue there was that if the datasource persisted an object; then init-net stage would
use the existing object on disk and not use the fallback path.
For OVF, at local time, it will run _get_data over the datasource list, which after reboot per this bug, it not return True; so I believe then that the fallback path should trigger as expected.
For Ec2 or other datasource which do persist objects it's not clear what a fallback scenario looks like.