Comment 6 for bug 1715128

Further discussion:

[11:11] <apw> cpaelzer, if this is going to take days to fix, can we not revert the whole of the cloud-init update somehow
[11:11] <apw> cpaelzer, given it is cratering testing
[11:11] <cpaelzer> apw: absolutely
[11:12] <cpaelzer> apw: I planned to jump into the cloud-init standup today to dsicuss options
[11:12] <cpaelzer> apw: a CURVER+reallyOLDVER might be a temporary fix in this case
[11:12] <cpaelzer> but since this is around data source identification in scaling stack we have to understand what really is going on)
[11:13] <wgrant> Well we know now
[11:13] <cpaelzer> my current theory is that scaling stack tries to mimic ec2, but doesn't do perfectly (a common case btw)
[11:13] <wgrant> https://bugs.launchpad.net/cloud-init/+bug/1715241
[11:13] <ubot5`> Ubuntu bug 1715241 in cloud-init "ds-identify openstack returns not found on non-intel" [Medium,Confirmed]
[11:13] <wgrant> ds-identify simply doesn't work outside x86.
[11:13] <wgrant> Since it relies on DMI
[11:14] <cpaelzer> IM-veryH-o I'm not 100% convinced that is the issue affecting the current case
[11:14] <apw> they use dmi ... openstack "for the win"
[11:14] <cpaelzer> hmm, yeah you might be right ont hat bug actually
[11:15] <cpaelzer> yet I wonder why this should now be different than before
[11:15] <cpaelzer> anyway smoser and rharper will ahve all the current context later today
[11:16] <wgrant> Becaise cloud-init used to poll all datasources
[11:16] <cpaelzer> Maybe it comes together with fail-detect EC2 + new ipv6 code that can fault if no EC2 data is actually provided
[11:16] <wgrant> there was work this cycle to speed up cloud-init by using ds-identify to skip irrelevant sourcea
[11:17] <cpaelzer> The polling -> detect change happened a while ago, that is why I wonder the recent update breaking it in this case
[11:17] <cpaelzer> I'm rather up to date on the ds-identify move
[11:17] <cpaelzer> just thought that would have been in artful for a while now, which is why I expect it to be partially bad for a while but e.g. the ipv6 code added now making this a hard fail
[11:18] <wgrant> it is either that it has just switched to EC2, or EC2 used to work but doesn't any more
[11:19] <wgrant> but it *should* be using OpenStack on that cloud, so fixing ds-identify would probably work
[11:19] <cpaelzer> ack
[11:19] <cpaelzer> I think copying that discussion context to the current bug is worth too