The metadata cache expiration timeout was hardcoded to 15 seconds in versions older than kilo (OSP7). In kilo a new configuration option was added: 'metadata_cache_expiration', Time in seconds to cache metadata; 0 to disable metadata caching entirely (not recommended). Increasing this should improve response times of the metadata API when under heavy load. Higher values may increase memory usage and result in longer times for host metadata changes to take effect. introduced in: https://review.openstack.org/159264 This config option should be backported to OSP5 in order to provide the same flexibility and avoid premature cache expiration in cases where the metadata is highly static.
Verified as follows - No error observed during nova startup with the option metadata_cache_expiration defined in /etc/nova/nova.conf. ************ Version ************ [root@rhos-compute-node-02 ~(keystone_admin)]# yum list installed | grep openstack-nova openstack-nova-api.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-cert.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-common.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-compute.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-conductor.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-console.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-novncproxy.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle openstack-nova-scheduler.noarch 2014.1.5-27.el7ost @rhelosp-5.0-el7-puddle ******** Logs ******** [root@rhos-compute-node-02 ~(keystone_admin)]# [root@rhos-compute-node-02 ~(keystone_admin)]# [root@rhos-compute-node-02 ~(keystone_admin)]# [root@rhos-compute-node-02 ~(keystone_admin)]# grep "metadata_cache" /etc/nova/nova.conf metadata_cache_expiration = 15 [root@rhos-compute-node-02 ~(keystone_admin)]# P.S: Nova startup logs has been attached as a tar file
Created attachment 1131962 [details] Nova startup logs (tar)
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://rhn.redhat.com/errata/RHBA-2016-0361.html