Open Stack

# grep -R scheduler_host_manager /usr/lib/python2.7/dist-packages/nova
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py: 
cfg.StrOpt('scheduler_host_manager',
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py: 
   FLAGS.scheduler_host_manager)
Fichier binaire 
/usr/lib/python2.7/dist-packages/nova/scheduler/driver.pyc concordant
grep: /usr/lib/python2.7/dist-packages/nova/CA/reqs/.gitignore: Aucun 
fichier ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/.gitignore: Aucun fichier 
ou dossier de ce type
grep: /usr/lib/python2.7/dist-packages/nova/CA/projects/.gitignore: 
Aucun fichier ou dossier de ce type

If I comment the portion of code that raise the error (in 
_is_opt_registered(opts, opt) of cfg.py), I get the following error :

ClassNotFound: Class SimpleScheduler could not be found: cannot import 
name vnc

I have the same error if I replace --scheduler_driver by 
--scheduler_manager in nova.conf.

novnc is not installed because it give a configure error, but 
nova-vncproxy is well installed.

I suspect the error raised is not the original error, only side effect...
I joined the trace of nova-scheduler before and after the code comment.

What can I try now ?

Ben

Le 22/08/2012 17:00, Joseph Suh a écrit :
> Ben,
>
> It is possible to have the option specified in a code. Try grep -r on whole code.
>
> Thanks,
>
> Joseph
>
> ----- Original Message -----
> From: "Ben" <ben.div at gmail.com>
> To: "Joseph Suh" <jsuh at isi.edu>
> Cc: openstack at lists.launchpad.net
> Sent: Wednesday, August 22, 2012 10:47:35 AM
> Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option: scheduler_host_manager
>
> Hi Joseph,
>
> Thank you for your answer. Yes, but where could be that option ? It's
> not duplicated in my nova.conf file, and this is the file the
> nova-scheduler uses.
> My nova.conf file joined.
>
> Regards,
>
> Ben
>
>
> Le 22/08/2012 16:37, Joseph Suh a écrit :
>> Ben,
>>
>> As the error message suggests, it is due to a duplicated option of scheduler_host_manager. It is specified more than once somewhere.
>>
>> Thanks,
>>
>> Joseph
>>
>> ----- Original Message -----
>> From: "Ben" <ben.div at gmail.com>
>> To: openstack at lists.launchpad.net
>> Sent: Wednesday, August 22, 2012 8:27:39 AM
>> Subject: Re: [Openstack] Unable to start nova-scheduler : duplicate option:	scheduler_host_manager
>>
>> Hi,
>>
>> No idea for my scheduler problem ? It was working at the beginning (I
>> suppose because I could launch instances), but I did a lot of
>> modification, modifying networks, deleting nova db, rebuild it, etc.
>>
>> Any idea on what I can do to identify the problem ? Where can I find the
>> mentionned option except in nova.conf ?
>>
>> Ben
>>
>> Le 22/08/2012 00:46, Ben a écrit :
>>> Hi,
>>>
>>> I'm trying to setup a little nova cluster with 3 nodes :
>>>
>>> - 1 controller node running all services but compute
>>> - 2 compute nodes running compute and network only
>>>
>>> I have faced a lot of issues, but I can't understand this one. When I
>>> start nova-scheduler on controller node, the process dies instantly with
>>> this error :
>>>
>>> CRITICAL nova [-] duplicate option: scheduler_host_manager
>>>
>>> So I can't start an instance, it remains stuck in building state. I have
>>> checked my nova.conf file, and I only see this line :
>>>
>>> --scheduler_driver=nova.scheduler.simple.SimpleScheduler
>>>
>>> What does means this error, how can I solve it ?
>>>
>>> Thanks,
>>>
>>> Ben
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
-------------- next part --------------
--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
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.simple.SimpleScheduler
--s3_host=94.103.xx.xx
--ec2_host=94.103.xx.xx
--rabbit_host=94.103.xx.xx
--cc_host=94.103.xx.xx
--nova_url=http://94.103.xx.xx:8774/v1.1/
--routing_source_ip=94.103.xx.xx
--glance_api_servers=94.103.xx.xx:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.28
--sql_connection=mysql://novadbadmin:hiddenPass@94.103.xx.xx/nova
--ec2_url=http://94.103.xx.xx:8773/services/Cloud
--keystone_ec2_url=http://94.103.xx.xx:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--libvirt_type=kvm
--libvirt_use_virtio_for_bridges=true
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--vnc_enabled=true
--vncproxy_url=http://94.103.xx.xx:6080
--vnc_console_proxy_url=http://94.103.xx.xx:6080
# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br100
--fixed_range=192.168.28.0/25
--floating_range=94.103.136.55/29
--network_size=128
--flat_network_dhcp_start=192.168.28.2
--flat_injected=False
--force_dhcp_release
--iscsi_helper=tgtadm
--connection_type=libvirt
--root_helper=sudo nova-rootwrap
--verbose
--libvirt_use_virtio_for_bridges
--ec2_private_dns_show
--novnc_enable=true
--novncproxy_base_url=http://94.103.xx.xx:6080/vnc_auto.html
--vncserver_proxyclient_address=127.0.0.1
--vncserver_listen=0.0.0.0

-------------- next part --------------
A non-text attachment was scrubbed...
Name: trace.log
Type: text/x-log
Size: 4026 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20120822/427b048d/attachment.bin>