Public bug reported: Hello, all.
Meta ======= OS: Ubuntu 16.04.2 (up-to-date 20-04-2017) Kernel: 4.8.0-46-generic Ostack Version: Ocata (from Cloud Archive) Nova Version: 15.0.2-0ubuntu1~cloud0 Hypervisor: QEMU/KVM 1:2.8+dfsg-3ubuntu2~cloud0 libvirt version: 2.5.0-3ubuntu5~cloud0 ZeroMQ Version: 4.2.1 (from Debian Sid) Python-zmq version: 16.0.2 (from Debian Sid) Redis Version: 3.2.8+Sentinel Description ============== I trying to deploy the OpenStack Ocata with ZeroMQ as message service and Redis as matchmaker. Main functions is working, but I cannot to create any VM. Expected result ================== nova boot starts, VMs successfully creates. Actual result ================ nova boot starts, VM gets the 'Scheduling' state, scheduler is successfully choose the compute node, but then nova-conductor writes that sentinel command is unknown: http://paste.ubuntu.com/24426756/ nova.conf: http://paste.ubuntu.com/24426770/ I think nova-conductor tries connect to Redis Server instead of Sentinel. Thanks. ** Affects: nova Importance: Undecided Status: New -- 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/1685227 Title: nova-conductor doesn't work with Redis Sentinel. Status in OpenStack Compute (nova): New Bug description: Hello, all. Meta ======= OS: Ubuntu 16.04.2 (up-to-date 20-04-2017) Kernel: 4.8.0-46-generic Ostack Version: Ocata (from Cloud Archive) Nova Version: 15.0.2-0ubuntu1~cloud0 Hypervisor: QEMU/KVM 1:2.8+dfsg-3ubuntu2~cloud0 libvirt version: 2.5.0-3ubuntu5~cloud0 ZeroMQ Version: 4.2.1 (from Debian Sid) Python-zmq version: 16.0.2 (from Debian Sid) Redis Version: 3.2.8+Sentinel Description ============== I trying to deploy the OpenStack Ocata with ZeroMQ as message service and Redis as matchmaker. Main functions is working, but I cannot to create any VM. Expected result ================== nova boot starts, VMs successfully creates. Actual result ================ nova boot starts, VM gets the 'Scheduling' state, scheduler is successfully choose the compute node, but then nova-conductor writes that sentinel command is unknown: http://paste.ubuntu.com/24426756/ nova.conf: http://paste.ubuntu.com/24426770/ I think nova-conductor tries connect to Redis Server instead of Sentinel. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1685227/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
