Description of problem: image_service parameter in nova.conf is no longer used Version-Release number of selected component (if applicable): Current puppet-nova How reproducible: Everytime Steps to Reproduce: 1. Deploy overcloud and check DEFAULT section in nova.conf Actual results: nova.conf contains image_service option in [DEFAULT] section. Expected results: nova.conf doesn't contain image_service option in [DEFAULT] section. Additional info: From 3aaa0b103447d56f8d3b259c693cd9a3a8dcbe36, image_service option is no longer available. ~~~ commit 3aaa0b103447d56f8d3b259c693cd9a3a8dcbe36 Author: Brian Waldon <bcwaldon> Date: Mon Jun 25 14:06:08 2012 -0700 Cleanup of image service code * Remove image_service flag * Move nova.image.fake to nova.tests.image.fake * Move nova.image.get_default_image_service to nova.image.glance.get_default_image_service * Move nova.image.get_image_service to nova.image.glance.get_remote_image_service * Related to bp integrate-python-glanceclient Change-Id: Iea6db7898328a9060fb88586e042efbc0a4351fc diff --git a/nova/flags.py b/nova/flags.py index c427a7e945..bb769c4dd1 100644 --- a/nova/flags.py +++ b/nova/flags.py @@ -322,9 +322,6 @@ global_opts = [ cfg.StrOpt('firewall_driver', default='nova.virt.firewall.IptablesFirewallDriver', help='Firewall driver (defaults to iptables)'), - cfg.StrOpt('image_service', - default='nova.image.glance.GlanceImageService', - help='The service to use for retrieving and searching images.'), ~~~
Hi Keigo, I will try to backport it till stable/queens upstream and will backport to OSP13 once it lands in upstream releases.
Hello Rajesh, Could you consider to backport a fix in upstream stable/queens brach into RHOSP13? Best Regads, Keigo Noha
Hi Keigo, The fix is already proposed to RHOSP13 as well as merged.
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/RHBA-2018:3587