As Amrith stated, you need to look at the Neutron logs as the message about
port binding suggests:
PortBindingFailed: Binding failed for port
26b727dd-52b4-4b34-b484-6ea3fd571c8d,
please check neutron logs for more information.
On Mon, Nov 13, 2017 at 8:22 AM, Debojyoti Das wrote:
> Hi All,
>
>
The Keystone v2 removal also broke Trove's gate. Trove's functional
and scenario tests had Keystone v2 hard codings and also relied on a >
4 year old 'compat' client package in the python-troveclient that did
not have V3 support.
Both cases required a lot of scrambling find all the v2 hard coding
Thanks. I will try to fix the legacy-trove-functional.
On Sat, Oct 14, 2017 at 12:58 AM, Andreas Jaeger wrote:
> On 2017-10-14 03:30, Sam Matzek wrote:
>> The legacy-trove-functional-dsvm-mysql and
>> legacy-trove-legacy-functional-dsvm-mysql jobs are running the wrong
>&g
more details and links
to the zuulv3-issues etherpad.
I'm not familiar enough with the job definitions to be able to work on
the fix reviews for these but would like to learn.
Sam Matzek
On Fri, Oct 13, 2017 at 2:57 PM, Jeremy Stanley wrote:
> The tl;dr is that we're planning to r
This is also one of several errors hitting the Trove gate. This
review should workaround the issue for now.
https://review.openstack.org/#/c/508344/3
On Mon, Oct 2, 2017 at 1:44 PM, Eric K wrote:
> Since the transition to zuul3, this error began and prevents the devstack
> setup from finishing
For reading the code I use Eclipse Mars with PyDev installed on
Windows 7. This allows me to CTRL-click on methods calls to link to
their source, etc. I also use this for some amount of code
modification and can run some amount of unit tests after pip
installing a lot of dependencies. This is mo
On Wed, Mar 2, 2016 at 8:25 PM, Adam Young wrote:
> On 02/29/2016 01:49 PM, Andrew Laski wrote:
>>
>>
>> On Mon, Feb 29, 2016, at 01:18 PM, Dan Smith wrote:
Forgive my ignorance or for playing devil's advocate, but wouldn't the
main difference between notifications and hooks be that
For what it's worth Glance API also has to deal with file I/O blocking
all greenthreads and has CooperativeReaders/Writers that yield around
the file I/O to mitigate starvation. A while ago I hit an issue with
5 concurrent VM snapshots starving Nova compute eventlets due to the
excessive file IO o
On Fri, Jan 8, 2016 at 11:54 AM, Sam Matzek wrote:
> On Fri, Jan 8, 2016 at 8:31 AM, Flavio Percoco wrote:
>> On 29/12/15 07:41 -0600, Sam Matzek wrote:
>>>
>>> On Thu, Dec 24, 2015 at 7:49 AM, Mikhail Fedosin
>>> wrote:
>>>>
>>>> Hel
On Fri, Jan 8, 2016 at 8:31 AM, Flavio Percoco wrote:
> On 29/12/15 07:41 -0600, Sam Matzek wrote:
>>
>> On Thu, Dec 24, 2015 at 7:49 AM, Mikhail Fedosin
>> wrote:
>>>
>>> Hello, it's another topic about glance v2 adoption in Nova, but it's
>
On Thu, Dec 24, 2015 at 7:49 AM, Mikhail Fedosin wrote:
> Hello, it's another topic about glance v2 adoption in Nova, but it's
> different from the others. I want to declare that there is a set of commits,
> that make Nova version agnostic and allow to work with both glance apis. The
> idea of the
attachments operation. More info is placed inline.
On Fri, Dec 11, 2015 at 8:41 PM, Anne Gentle
wrote:
>
>
> On Fri, Dec 11, 2015 at 8:38 PM, Anne Gentle
> wrote:
>>
>>
>>
>> On Fri, Dec 11, 2015 at 7:33 PM, Matt Riedemann
>> wrote:
>>>
The CRUD operations for Nova volume attachments have inconsistencies
between documentation and implementation. Additionally, the read/get
operation is implemented twice under different URIs. What is Nova's
direction for volume attachment APIs and how should the following
discrepancies be resolved
13 matches
Mail list logo