Comment 5 for bug 1715128

Copy from IRC:
[10:03] <Laney> cpaelzer: it's probably https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1715128
[10:04] <ubottu> Launchpad bug 1715128 in cloud-init (Ubuntu) "Crashes in convert_ec2_metadata_network_config on ScalingStack bos01 (ppc64el)" [Undecided,New]
[10:20] <cpaelzer> I opened bug 1715555 for what I saw, but the bug you listed makes sense to all I've found
[10:20] <ubottu> bug 1715555 in Auto Package Testing "ppc64el vagrant-mutate tests fail to access atlas.hashicorp.com" [Undecided,New] https://launchpad.net/bugs/1715555
[10:20] <cpaelzer> my issue boils down to proxies missing and the bug you referred is reporting just that as an issue
[10:21] <cpaelzer> I'm dupping mine - thanks for the info
[10:27] <cpaelzer> Laney: do we fake the EC2 datasource in our scalingstack?
[10:27] <cpaelzer> to provide the config data to cloud-init
[10:28] <Laney> I don't know how that stuff works
[10:28] <Laney> it's more or less the normal cloud images if that helps
[10:28] <cpaelzer> that is only the consumer
[10:28] <cpaelzer> how the config is passed is the interesting part in this case
[10:28] <cpaelzer> Laney: it would be great if you could add the full boot log containing all cloud-init output to the bug
[10:29] <wgrant> bos01 is a pretty standard kilo AFAIK
[10:29] <wgrant> We didn't do anything specially EC2ish while deploying it
[10:29] <cpaelzer> so it should be detected as openstack datasources then, which it is not
[10:29] <wgrant> How does cloud-init actually detect the datasource, though?
[10:30] <cpaelzer> Laney: if you could attach the output from the failing ppc as well as the working lcy01 or lgw01 that would be great
[10:30] <wgrant> If it uses DMI or something that might just not work on ppc64el with our relatively old setup
[10:31] <cpaelzer> wgrant: Laney: https://git.launchpad.net/cloud-init/tree/tools/ds-identify
[10:31] <wgrant> I have a religious objection to 1300 line shell scripts.
[10:32] <wgrant> Ah yes, lots of DMI bits in there.
[10:34] <Laney> https://bugs.launchpad.net/cloud-init/+bug/1715241?
[10:34] <ubottu> Launchpad bug 1715241 in cloud-init "ds-identify openstack returns not found on non-intel" [Medium,Confirmed]
[10:34] <cpaelzer> Laney: if you could provide those logs I'm sure smoser and rharper will find that most interesting later on and then has all the data to start finding what is wrong in the detection
[10:34] <wgrant> Aha
[10:34] <cpaelzer> It shoudl still find an openstack config drive no matter of DMI in your case
[10:34] <cpaelzer> (assumption)
[10:35] <wgrant> I have never seen an OpenStack that used configdrive.
[10:35] <wgrant> Oh you can do it when creating the VM, I see.
[10:35] <cpaelzer> which brings me back to my former question what you currently use to pass cloud init config info?
[10:35] <wgrant> Still never seen it used :)
[10:36] <wgrant> It uses the normal Nova metadata HTTP service
[10:36] <cpaelzer> thanks
[10:36] <cpaelzer> I'll copy this chat to the bug, together with the logs Laney can provide this should make some progress when US wakes up later