Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Openstack image oem_id does not match coreos-metadata provider #1917
When using coreos images for openstack default
Container Linux Version
Cisco Metacloud (Openstack). I believe we are currently using Icehouse release.
Sort of a workaround found in #1413 .
Apr 17, 2017
This is mostly expected behavior. The reason coreos-metadata cannot use the cmdline in the case of OpenStack is due to it needing to support both config-drive and the network metadata service. Container Linux Configs are designed to abstract this problem for you (though investigating this shows that ct doesn't properly invoke coreos-metadata).