Public bug reported: This is a follow-up to this SmartOS change: http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/957
It seems to me that we shouldn't run dmidecode on arm in AltCloud as well and do something like: http://bazaar.launchpad.net/~strikov/cloud-init/altcloud-dmidecode-fix/revision/959 I put this check for arm to get_cloud_type() not get_data() to avoid blocking of CLOUD_INFO_FILE path on arm. ** Affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1285686 Title: AltCloud: Do not run dmidecode on arm32/64 Status in Init scripts for use on cloud images: New Bug description: This is a follow-up to this SmartOS change: http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/957 It seems to me that we shouldn't run dmidecode on arm in AltCloud as well and do something like: http://bazaar.launchpad.net/~strikov/cloud-init/altcloud-dmidecode-fix/revision/959 I put this check for arm to get_cloud_type() not get_data() to avoid blocking of CLOUD_INFO_FILE path on arm. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1285686/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
