vCenter nova compute service fails to start because base_dir_name config not registered but used by vmops.py

Bug #1126078 reported by kirankv
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Sean Chen

Bug Description

When VC nova driver is started, it fails with the following error

INFO nova.virt.driver Loading compute driver 'vmwareapi.VMwareVCDriver'
CRITICAL nova
no such option: base_dir_name
Traceback (most recent call last):
  File "nova-compute", line 82, in <module>
   db_allowed=False)
  File "/opt/stack/nova/nova/service.py", line 534, in create
   db_allowed=db_allowed)
  File "/opt/stack/nova/nova/service.py", line 413, in __init__
    self.manager = manager_class(host=self.host, *args, **kwargs)
File "/opt/stack/nova/nova/compute/manager.py", line 323, in __init__
    self.driver = driver.load_compute_driver(self.virtapi, compute_driver)
  File "/opt/stack/nova/nova/virt/driver.py", line 879, in load_compute_driver
    virtapi)
  File "/opt/stack/nova/nova/openstack/common/importutils.py", line 51, in import_object_ns
    return import_class(import_value)(*args, **kwargs)
  File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 348, in __init__
    super(VMwareVCDriver, self).__init__(virtapi)
  File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 150, in __init__
    self._volumeops, self._cluster_name)
  File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 87, in __init__
   self._instance_path_base = VMWARE_PREFIX + CONF.base_dir_name
  File "/opt/stack/nova/nova/openstack/common/cfg.py", line 1152, in __getattr__
    return self._get(name)
  File "/opt/stack/nova/nova/openstack/common/cfg.py", line 1456, in _get
    value = self._substitute(self._do_get(name, group))
  File "/opt/stack/nova/nova/openstack/common/cfg.py", line 1472, in _do_get
    info = self._get_opt_info(name, group)
  File "/opt/stack/nova/nova/openstack/common/cfg.py", line 1572, in _get_opt_info
    raise NoSuchOptError(opt_name, group)
NoSuchOptError: no such option: base_dir_name

Tags: vmware
kirankv (vkkumar-live)
Changed in nova:
assignee: nobody → kirankv (vkkumar-live)
assignee: kirankv (vkkumar-live) → nobody
kirankv (vkkumar-live)
Changed in nova:
assignee: nobody → kirankv (vkkumar-live)
Changed in nova:
assignee: kirankv (vkkumar-live) → Divakar Padiyar Nandavar (divakar-padiyar-nandavar)
Changed in nova:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

Fix proposed to branch: master
Review: https://review.openstack.org/22018

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/22046

tags: added: vmware
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/22577

Changed in nova:
assignee: Divakar Padiyar Nandavar (divakar-padiyar-nandavar) → Sean Chen (opencompute)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/22577
Committed: http://github.com/openstack/nova/commit/1998730f5233c13da1510814290f42673aa46fbb
Submitter: Jenkins
Branch: master

commit 1998730f5233c13da1510814290f42673aa46fbb
Author: Sean Chen <email address hidden>
Date: Thu Feb 21 10:02:29 2013 -0800

    import base_dir_name config option into vmwareapi

    Fixes Bug 1126078

    Change-Id: Ic834c9289ca0bcefbf8077939d07728daa98366f

Changed in nova:
status: In Progress → Fix Committed
Revision history for this message
Brad Knowles (bknowles) wrote :

Folks,

So, this fix has been committed to master, but has that code actually been pushed out to the repos yet? I did an `apt-get update && apt-get upgrade` and I didn't see this change having taken place in the version of this file on my system.

I can manually add this one line -- that's no problem -- but I want to make sure I understand whether or not I should have gotten this automatically.

Thanks!

Revision history for this message
Sean Chen (opencompute) wrote :

It's on the master branch

https://github.com/openstack/nova/commits/master/nova/virt/vmwareapi/vmops.py

Can you check again? Which branch are you using?

Revision history for this message
Brad Knowles (bknowles) wrote :

Sean,

I'm not using devstack or anything like that. I'm using the packaged versions as provided via the repo at http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/precise-updates/grizzly/

I found the snippet in master, and I was able to manually apply that to the vmops.py file that I have. But now I'm wondering what other changes may also be in master that I do not have, and what would be the best way to get them?

Revision history for this message
Sean Chen (opencompute) wrote :

We will need to check grizzly schedule, I wonder when the official release branch will be created.

Thierry Carrez (ttx)
Changed in nova:
milestone: none → grizzly-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: grizzly-rc1 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.