This should probably be an oslo.messaging bug report only now I don't really have any insight as to whether there's a real bug here, but it sounds plausible so marking Confirmed
** Changed in: nova Status: New => Invalid ** Tags removed: conductor console ** Tags added: zmq ** Changed in: oslo.messaging Status: New => Confirmed ** Changed in: oslo.messaging Importance: Undecided => Low -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1290772 Title: MatchMakerRedis doesn't work [zeromq] Status in OpenStack Compute (Nova): Invalid Status in Messaging API for OpenStack: Confirmed Bug description: I was testing zeromq with redis. I installed all packages from ubuntu cloud repository[havana]. I added the following lines in nova.conf. ... rpc_zmq_matchmaker = nova.openstack.common.rpc.matchmaker_redis.MatchMakerRedis rpc_backend = nova.openstack.common.rpc.impl_zmq ... I get the following error 2014-03-11 09:57:58.671 11201 ERROR nova.openstack.common.threadgroup [-] Command # 1 (SADD scheduler.ubuntu scheduler.ubuntu.ubuntu) of pipeline caused error: Operation against a key holding the wrong kind of value The same error is reported in the following services: nova-conductor nova-consoleauth nova-scheduler The problem seems to come from the matchmaker using the same key to register a set of hosts and the hosts themselves. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1290772/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp