CRITICAL nova [-] No module named quantum.manager

Just for information i am using following repo for quantum installation
apt-get install python-software-properties
add-apt-repository ppa:openstack-ubuntu-testing/folsom-trunk-testing
add-apt-repository ppa:openstack-ubuntu-testing/folsom-deps-staging

http://docs.openstack.org/trunk/openstack-network/admin/content/install_ubuntu.html

What value is set to network_manager in your nova.conf?
I guess network_manager in your nova.conf is "quantum.manager" or something.

network_manager in nova.conf has no meaning In Folsom quantum, but this configuration parameter must point a valid python module like "nova.network.manager.VlanManager".

Since You seems to have create your config file from the Essex version,
commenting out or removing "network_manager" line from nova.conf may help you.

It would be better we should add a note about network_manager in nova.conf in the Folsom version of quantum admin guide.

This is my nova.conf file

[DEFAULT]
dhcpbridge_flagfile=/etc/nova/nova.conf
dhcpbridge=/usr/bin/nova-dhcpbridge
logdir=/var/log/nova
state_path=/var/lib/nova
lock_path=/var/lock/nova
force_dhcp_release=True
iscsi_helper=tgtadm
connection_type=libvirt
root_helper=sudo nova-rootwrap /etc/nova/rootwrap.conf
#verbose=True
verbose=false
ec2_private_dns_show_ip=True
api_paste_config=/etc/nova/api-paste.ini
volumes_path=/var/lib/nova/volumes
allow_admin_api=true
use_deprecated_auth=false

###############################
# VOLUMES
################################
#volume_driver=nova.volume.driver.ISCSIDriver
#volume_group=nova-volumes
#volume_name_template=volume-%08x
#iscsi_helper=tgtadm

########################################
# AUTHENTICATION
########################################
auth_strategy=keystone

#######################################
#URL Configuration
#######################################
s3_host=10.83.18.208
ec2_host=10.83.18.208
rabbit_host=172.24.31.1
nova_url=http://10.83.18.208:8774/v1.1/
iscsi_ip_prefix=192.168.0.0
ec2_url=http://10.83.18.208:8773/services/Cloud
keystone_ec2_url=http://10.83.18.208:5000/v2.0/ec2tokens
1:38 PM #####################
#Glance server
#####################
glance_api_servers=10.83.18.208:9292
image_service=nova.image.glance.GlanceImageService

############################
# DATABASE
#############################
sql_connection=mysql://nova:nova@10.83.18.208/nova

##################################
#noVNC configuration
##################################
novnc_enable=true
novncproxy_base_url=http://10.83.18.208:6080/vnc_auto.html
vncserver_proxyclient_address=10.83.18.208
vncserver_listen=10.83.18.208

##################################
#network Configuration
##################################

#network_manager=nova.network.quantum.manager.QuantumManager
public_interface=eth0
fixed_range=192.168.0.0/16
floating_range=10.83.128.0/25
my_ip=10.83.18.208
linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
force_dhcp_release=True
firewall_driver=nova.virt.libvirt.firewall.IptablesFirewallDriver

#########################
# SCHEDULER
#########################
scheduler_driver=nova.scheduler.simple.SimpleScheduler

####################################
# COMPUTE
###################################
libvirt_type=kvm
compute_driver=libvirt.LibvirtDriver
instance_name_template=instance-%08x
api_paste_config=/etc/nova/api-paste.ini
allow_resize_to_same_host=True
  ###########################
#Quantum Configuration
###########################
network_api_class=nova.network.quantumv2.api.API
quantum_url=http://172.24.31.1:9696
quantum_auth_strategy=keystone
quantum_admin_tenant_name=service
quantum_admin_username=quantum
quantum_admin_password=quantum
quantum_admin_auth_url=http://172.24.31.1:35357/v2.0

network_api_class=nova.network.quantumv2.api.API
quantum_admin_username=quantum
quantum_admin_password=quantum
quantum_admin_auth_url=http://10.83.18.208:35357/v2.0/
quantum_auth_strategy=keystone
quantum_admin_tenant_name=service
quantum_url=http://10.83.18.208:9696/

libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver

###########################################
#Quo...

Your nova.conf works for me. nova-compute starts successfully with your nova.conf.
Do you still fail to start nova-compute with this conf?

If I enabled the line network_manager in nova.conf, I got the same error as yours:
2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute driver 'libvirt.LibvirtDriver'
2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager

P.S.
I tested with git version. I tried the ubuntu package version later.

Thanks for testing this file, can i go with this file for production setup
and can i also need to run nova-network and nova-volume service also along
with quantum and cinder

On Mon, Oct 8, 2012 at 10:39 PM, Akihiro Motoki
<email address hidden>wrote:

> Your nova.conf works for me. nova-compute starts successfully with your
> nova.conf.
> Do you still fail to start nova-compute with this conf?
>
> If I enabled the line network_manager in nova.conf, I got the same error
> as yours:
> 2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute driver
> 'libvirt.LibvirtDriver'
> 2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager
>
> P.S.
> I tested with git version. I tried the ubuntu package version later.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1063689
>
> Title:
> CRITICAL nova [-] No module named quantum.manager
>
> Status in OpenStack Community Project:
> New
> Status in OpenStack Quantum (virtual network service):
> New
>
> Bug description:
> Hi All,
>
> I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
> Quantum and facing the same issue in a Folsom
>
> root@us000901:/var/log/quantum# tail -f /var/log/nova/nova-compute.log
> 2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
> 2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for us000901
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram
> (MB): 63874
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free disk
> (GB): 275
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
> 2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for us000901
> 2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host status
> 2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
> 2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute driver
> 'libvirt.LibvirtDriver'
> 2012-10-08 15:38:07 CRITICAL nova [-] No module named quantum.manager
>
> My quantum-server is running
> root@us000901:~# /etc/init.d/quantum-server status
> Rather than invoking init scripts through /etc/init.d, use the service(8)
> utility, e.g. service quantum-server status
>
> Since the script you are attempting to invoke has been converted to an
> Upstart job, you may also use the status(8) utility, e.g. status
> quantum-server
> quantum-server start/running, process 5996
> root@us000901:~#
>
> and i am stuck here the config is working properly in EsseX
> (essex+openvswitch+quantum)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openstack-community/+bug/1063689/+subscriptions
>

--
ViVek Raghuwanshi
Mobile -+91-09595950504

Skype - vivek_raghuwanshi

Hi there,

I'm not certain why I am included on the note here - please check to see who should be getting this note instead of me.

Many thanks,

Jean Marie

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of vivekraghuwanshi
Sent: Monday, October 08, 2012 11:23 AM
To: Martini, Jean Marie
Subject: Re: [Bug 1063689] Re: CRITICAL nova [-] No module named quantum.manager

Thanks for testing this file, can i go with this file for production setup and can i also need to run nova-network and nova-volume service also along with quantum and cinder

On Mon, Oct 8, 2012 at 10:39 PM, Akihiro Motoki
<email address hidden>wrote:

> Your nova.conf works for me. nova-compute starts successfully with
> your nova.conf.
> Do you still fail to start nova-compute with this conf?
>
> If I enabled the line network_manager in nova.conf, I got the same
> error as yours:
> 2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute
> driver 'libvirt.LibvirtDriver'
> 2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager
>
> P.S.
> I tested with git version. I tried the ubuntu package version later.
>
> --
> You received this bug notification because you are subscribed to the
> bug report.
> https://bugs.launchpad.net/bugs/1063689
>
> Title:
> CRITICAL nova [-] No module named quantum.manager
>
> Status in OpenStack Community Project:
> New
> Status in OpenStack Quantum (virtual network service):
> New
>
> Bug description:
> Hi All,
>
> I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
> Quantum and facing the same issue in a Folsom
>
> root@us000901:/var/log/quantum# tail -f /var/log/nova/nova-compute.log
> 2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
> 2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for us000901
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram
> (MB): 63874
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free
> disk
> (GB): 275
> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
> 2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-]
> Compute_service record updated for us000901
> 2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host status
> 2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
> 2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute
> driver 'libvirt.LibvirtDriver'
> 2012-10-08 15:38:07 CRITICAL nova [-] No module named
> quantum.manager
>
> My quantum-server is running
> root@us000901:~# /etc/init.d/quantum-server status
> Rather than invoking init scripts through /etc/init.d, use the service(8)
> utility, e.g. service quantum-server status
>
> Since the script you are attempting to invoke has been converted to an
> Upstart job, you may also use the status(8) utility, e.g. status
> quantum-server
> quantum-server start/running, process 5996
> root@us000901:~#
>
> and i am stuck here the config is working properly in EsseX
> ...

I think the Launchpad spam is due to the bug creators inclusion of the "openstack community project" as a source of the bug. I'm not sure what the project is, or who is subscribed.

It sounds like this is a misconfig issue. Consider filing something against the openstack-manual projct and tagging it with 'quantum' if you have suggestions for improving the docs to avoid such misconfigs in the future.

In general, such an issue is best filed as a question to Launchpad answers, not as a bug.

thanks Jean Marie, somebody assigned this bug to the wrong team, taht's
why you and others got it. I have fixed the issue now.

/stef

On Mon 08 Oct 2012 11:00:09 AM PDT, jean marie martini wrote:
> Hi there,
>
> I'm not certain why I am included on the note here - please check to see
> who should be getting this note instead of me.
>
> Many thanks,
>
> Jean Marie
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of vivekraghuwanshi
> Sent: Monday, October 08, 2012 11:23 AM
> To: Martini, Jean Marie
> Subject: Re: [Bug 1063689] Re: CRITICAL nova [-] No module named quantum.manager
>
> Thanks for testing this file, can i go with this file for production
> setup and can i also need to run nova-network and nova-volume service
> also along with quantum and cinder
>
> On Mon, Oct 8, 2012 at 10:39 PM, Akihiro Motoki
> <email address hidden>wrote:
>
>> Your nova.conf works for me. nova-compute starts successfully with
>> your nova.conf.
>> Do you still fail to start nova-compute with this conf?
>>
>> If I enabled the line network_manager in nova.conf, I got the same
>> error as yours:
>> 2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute
>> driver 'libvirt.LibvirtDriver'
>> 2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager
>>
>> P.S.
>> I tested with git version. I tried the ubuntu package version later.
>>
>> --
>> You received this bug notification because you are subscribed to the
>> bug report.
>> https://bugs.launchpad.net/bugs/1063689
>>
>> Title:
>> CRITICAL nova [-] No module named quantum.manager
>>
>> Status in OpenStack Community Project:
>> New
>> Status in OpenStack Quantum (virtual network service):
>> New
>>
>> Bug description:
>> Hi All,
>>
>> I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
>> Quantum and facing the same issue in a Folsom
>>
>> root@us000901:/var/log/quantum# tail -f /var/log/nova/nova-compute.log
>> 2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>> 2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-]
>> Compute_service record updated for us000901
>> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram
>> (MB): 63874
>> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free
>> disk
>> (GB): 275
>> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free VCPUS: 8
>> 2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-]
>> Compute_service record updated for us000901
>> 2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host status
>> 2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
>> 2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute
>> driver 'libvirt.LibvirtDriver'
>> 2012-10-08 15:38:07 CRITICAL nova [-] No module named
>> quantum.manager
>>
>> My quantum-server is running
>> root@us000901:~# /etc/init.d/quantum-server status
>> Rather than invoking init scripts through /etc/init.d, use the service(8)
>> utility, e.g. service quantum-server status
>>
>> Since the script you are attempting to invoke has been converted to an
>>...

Thanks

Sorry for assigning this bug in a wrong team, i am taking care of this in
feature.

Regards
ViVek

On Tue, Oct 9, 2012 at 12:05 AM, Stefano Maffulli <
<email address hidden>> wrote:

> thanks Jean Marie, somebody assigned this bug to the wrong team, taht's
> why you and others got it. I have fixed the issue now.
>
> /stef
>
> On Mon 08 Oct 2012 11:00:09 AM PDT, jean marie martini wrote:
> > Hi there,
> >
> > I'm not certain why I am included on the note here - please check to see
> > who should be getting this note instead of me.
> >
> > Many thanks,
> >
> > Jean Marie
> >
> > -----Original Message-----
> > From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> vivekraghuwanshi
> > Sent: Monday, October 08, 2012 11:23 AM
> > To: Martini, Jean Marie
> > Subject: Re: [Bug 1063689] Re: CRITICAL nova [-] No module named
> quantum.manager
> >
> > Thanks for testing this file, can i go with this file for production
> > setup and can i also need to run nova-network and nova-volume service
> > also along with quantum and cinder
> >
> > On Mon, Oct 8, 2012 at 10:39 PM, Akihiro Motoki
> > <email address hidden>wrote:
> >
> >> Your nova.conf works for me. nova-compute starts successfully with
> >> your nova.conf.
> >> Do you still fail to start nova-compute with this conf?
> >>
> >> If I enabled the line network_manager in nova.conf, I got the same
> >> error as yours:
> >> 2012-10-09 02:03:18 INFO nova.compute.manager [-] Loading compute
> >> driver 'libvirt.LibvirtDriver'
> >> 2012-10-09 02:03:18 CRITICAL nova [-] No module named quantum.manager
> >>
> >> P.S.
> >> I tested with git version. I tried the ubuntu package version later.
> >>
> >> --
> >> You received this bug notification because you are subscribed to the
> >> bug report.
> >> https://bugs.launchpad.net/bugs/1063689
> >>
> >> Title:
> >> CRITICAL nova [-] No module named quantum.manager
> >>
> >> Status in OpenStack Community Project:
> >> New
> >> Status in OpenStack Quantum (virtual network service):
> >> New
> >>
> >> Bug description:
> >> Hi All,
> >>
> >> I am using Ubuntu 12.04 and using Folsom release with OpenVSwitch and
> >> Quantum and facing the same issue in a Folsom
> >>
> >> root@us000901:/var/log/quantum# tail -f
> /var/log/nova/nova-compute.log
> >> 2012-10-08 15:35:56 AUDIT nova.compute.resource_tracker [-] Free
> VCPUS: 8
> >> 2012-10-08 15:35:56 INFO nova.compute.resource_tracker [-]
> >> Compute_service record updated for us000901
> >> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free ram
> >> (MB): 63874
> >> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free
> >> disk
> >> (GB): 275
> >> 2012-10-08 15:37:04 AUDIT nova.compute.resource_tracker [-] Free
> VCPUS: 8
> >> 2012-10-08 15:37:04 INFO nova.compute.resource_tracker [-]
> >> Compute_service record updated for us000901
> >> 2012-10-08 15:37:04 INFO nova.compute.manager [-] Updating host
> status
> >> 2012-10-08 15:38:06 INFO nova.service [-] Caught SIGTERM, exiting
> >> 2012-10-08 15:38:07 INFO nova.compute.manager [-] Loading compute
> >> driver 'libvirt.LibvirtDriver'
> >> 2012-10-08 15:38:07 CRITICAL n...

remove network-manager tag from nova.conf file works for me and now nova is working fine, if you are using quantum for networking just remove network-manager from nova.conf

http://pastebin.com/nBTkbL6p

Hi All i am pasting my nova.conf file which works well with Folsom+OpenvSwitch+Quantum+Cinder

hope this will helps you all just modified the IP and RabbitMQ password as per your configuration.

http://pastebin.com/nBTkbL6p