[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

** Changed in: cinder (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple nova-volume services fails to create

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

** Changed in: cinder (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple nova-volume services fails to create volume on second

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

multiple volume services on a single host isn't something that's actually supported right now and won't be on Nova-Volume. The hack that Huang mentioned may work for you if you can get the networking squared away. ** Tags added: driver ** Changed in: cinder Status: Confirmed = Invalid

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

multiple volume services on a single host isn't something that's actually supported right now and won't be on Nova-Volume. The hack that Huang mentioned may work for you if you can get the networking squared away. ** Tags added: driver ** Changed in: cinder Status: Confirmed = Invalid

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

** Changed in: cinder Status: New = Confirmed ** Changed in: cinder (Ubuntu) Status: New = Confirmed ** Changed in: cinder (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

** Changed in: cinder Status: New = Confirmed ** Changed in: cinder (Ubuntu) Status: New = Confirmed ** Changed in: cinder (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Assigning to the Ubuntu package ** Package changed: ubuntu = cinder (Ubuntu) ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cinder in Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Assigning to the Ubuntu package ** Package changed: ubuntu = cinder (Ubuntu) ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple nova-volume services

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Hi Aimon, In your case, having two volume services running on same physical host requires a little bit of hack. Here's what I would do: 1) assign two IPs to the nova-volume physical host, say 172.16.0.1/24 and 172.16.0.2/24. You may also have to turn on arp_filter via echo

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

** Project changed: openstack-ci = cinder -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple nova-volume services fails to create volume on second storage server when using

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

I have now also tried: --volume_scheduler_driver=nova.scheduler.simple.SimpleScheduler And have exact same bad behavior when it hits the second sever. Could this be LUN number conflicts? They both default to LUN0. ** Description changed: OS: Ubuntu 12.04 Arch: amd64 - Nova Version:

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Ok after tracing the Nexenta logs I have found that the second Nexenta server is never contacted when the failure occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: Multiple

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Aha Ok it requires that the nova-volume services run on separate hosts! I realized this after looking at service table in db and seeing only one nova-volume entry. Having them on different hosts is not an option for us. I am going to write patch that allows override of hostname to in essence

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Note that both nova-volume servies are on same server.. From what I can tell it is doing round robin between the two services when I create volumes. I do notice that the service table in db only references one service.. Is this to be expected? ** Also affects: ubuntu Importance: Undecided

[Bug 1039763] Re: Multiple nova-volume services fails to create volume on second storage server when using Nexenta driver

Note that if I switch the order in which they start, the second one to start is always one to fail creation. Both work ok on their own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039763 Title: