In order to leverage the stable-maint efforts upstream, we should do a "pseudo-rebase" up to the latest interesting commit on stable/liberty upstream (given that a 12.0.1 tag has not yet been cut by upstream, and is unlikely to be so in the immediate future). This would include at least the following commits (starred) from stable/upstream: 05e54eb Add -constraints sections for CI jobs 1a688e3 Remove the TestRemoteObject class 94d6b69 Omnibus stable fix for upstream requirements breaks * 29f70e7 Scheduler: honor the glance metadata for hypervisor details * e0647dd servicegroup: stop zombie service due to exception * 1f94018 Imported Translations from Zanata * cf197ec xen: mask passwords in volume connection_data dict * 626139e Handle DB failures in servicegroup DB driver * 0ff44c9 Fix Nova's indirection fixture override * f04cf8c Updated from global requirements 70fbad4 Add first reno-based release note 999267c Add "unreleased" release notes page 5207013 Add reno for release notes management * d3fe7e4 cells is a sad panda about scheduler hints * 474e7bb Fix attibute error when cloning raw images in Ceph * cc19164 Exclude all BDM checks for cells * 50db2a5 Image meta: treat legacy vmware adapter type values * 9a1ff88 Switch to post-versioning * e6d3b85 update .gitreview for stable/liberty
Verified that the fixed in version or later has been included in RHOS8 packaging. [root@lynx13 ~(keystone_admin)]# yum list installed | grep openstack-nova openstack-nova-api.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-cert.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-common.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-compute.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-conductor.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-console.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-novncproxy.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0 openstack-nova-scheduler.noarch 1:12.0.1-2.el7ost @RH7-RHOS-8.0
*** Bug 1287696 has been marked as a duplicate of this bug. ***
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/RHEA-2016-0603.html