The metedata definitions are missing from the database. It can be loaded by: glance-manage --config-file /etc/glance/glance-api.conf db_load_metadefs
@Avi: Can you confirm you have to do this manually when installing Glance with triple-o?
These Tempest tests didn't exist in the Newton release, and have been merged in December 2016. Therefore this pops up now, and tests fail in Ocata because "glance-manage db_load_metadefs" is not executed. We need to add this to puppet-glance therefore. I'm working on a patch for puppet-glance right now.
Proposed upstream patch to fix this: https://review.openstack.org/447480
Upstream bug: https://bugs.launchpad.net/tripleo/+bug/1664995
Patch merged on master and stable/ocata -> POST.
# rpm -q puppet-glance puppet-glance-10.3.0-2.el7ost.noarch Test that data was upload to DB [stack@undercloud-0 ~]$ glance md-namespace-list +------------------------------------------+ | namespace | +------------------------------------------+ | OS::Cinder::Volumetype | | OS::Software::WebServers | | OS::Software::Runtimes | | OS::Software::DBMS | | OS::OperatingSystem | | OS::Glance::Signatures | | OS::Glance::CommonImageProperties | | OS::Compute::XenAPI | | OS::Compute::Watchdog | | OS::Compute::VMware | | OS::Compute::VMwareQuotaFlavor | | OS::Compute::VMwareFlavor | | OS::Compute::VirtCPUTopology | | OS::Compute::Trust | | OS::Compute::RandomNumberGenerator | | OS::Compute::Quota | | OS::Compute::Libvirt | | OS::Compute::LibvirtImage | | OS::Compute::InstanceData | | OS::Compute::Hypervisor | | OS::Compute::HostCapabilities | | OS::Compute::GuestShutdownBehavior | | OS::Compute::GuestMemoryBacking | | OS::Compute::CPUPinning | | OS::Compute::AggregateNumInstancesFilter | | OS::Compute::AggregateIoOpsFilter | | OS::Compute::AggregateDiskFilter | | CIM::VirtualSystemSettingData | | CIM::StorageAllocationSettingData | | CIM::ResourceAllocationSettingData | | CIM::ProcessorAllocationSettingData | +------------------------------------------+
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:1245