Hi Gary,
Almost the same I have posted another way of the fix.
https://review.openstack.org/#/c/49942/
Both try to fix the same issue.
Gary's one changes neutronclient itself and mine chnages quantumclient proxy.
I am not sure which is the direction, but at least one of them should
be merged
Regarding https://review.openstack.org/#/c/49942/ (against
quantumclient branch),
the gate for quantumclient branch of python-neutronclient seems broken.
It seems the script expects master branch of python-neutronclient.
I am not sure what is the right direction to propose patch to
quantumclient
...@vmware.commailto:gkot...@vmware.com
Subject: Re: [openstack-dev] Gate issues - what you can do to help
I'm tracking that with this bug:
https://bugs.launchpad.net/openstack-ci/+bug/1234181
There are a lot of sys.exit(1) calls in the neutron code on stable/grizzly (and
in master too
2013/10/3 Gary Kotton gkot...@vmware.com:
Please see https://review.openstack.org/#/c/49483/
That's s/quantum/neutron/ on stable - I'm confused why is that, it
should have been quantum everywhere in Grizzly.
Could you please expand your reasoning in the commit message? It also
doesn't help,
On 10/3/13 11:59 AM, Alan Pevec ape...@gmail.com wrote:
2013/10/3 Gary Kotton gkot...@vmware.com:
Please see https://review.openstack.org/#/c/49483/
That's s/quantum/neutron/ on stable - I'm confused why is that, it
should have been quantum everywhere in Grizzly.
Please see below:
Hi,
This seems to be my bad. I have abandoned the patch and am still looking
into the problems.
Thanks
Gary
On 10/3/13 12:14 PM, Gary Kotton gkot...@vmware.com wrote:
On 10/3/13 11:59 AM, Alan Pevec ape...@gmail.com wrote:
2013/10/3 Gary Kotton gkot...@vmware.com:
Please see
Hi,
I think that I may have stumbled upon the problem, but need the help from
someone on the infra team. Then again I may just be completely mistaken.
Prior to the little hiccup we have at the moment VM's that were used for
devstack on the infra side would have 1 interface:
2013-09-10
On 2013-10-03 06:54:10 -0700 (-0700), Gary Kotton wrote:
I think that I may have stumbled upon the problem, but need the help from
someone on the infra team.
[...]
I'm manually launching the test script on a fresh VM now and should
have something shortly.
--
Jeremy Stanley
The problems occur when the when the the following line is invoked:
https://github.com/openstack-dev/devstack/blob/stable/grizzly/lib/quantum#L302
But that line is reached only in case baremetal is enabled which isn't
the case in gate, is it?
Cheers,
Alan
Hi,
I would like to share what Gary and I investigated, while it is not
addressed yet.
The cause is the failure of quantum-debug command in setup_quantum_debug
(https://github.com/openstack-dev/devstack/blob/stable/grizzly/stack.sh#L996).
We can reproduce the issue in local environment by
Hi,
quantumclient is now fixed for stable/grizzly but there are issues
with check-tempest-devstack-vm-neutron job where devstack install is
dying in the middle of create_quantum_initial_network() without trace
e.g.
...@vmware.com,
Cc: OpenStack Development Mailing List
openstack-dev@lists.openstack.org
Date: 10/02/2013 10:45 AM
Subject:Re: [openstack-dev] Gate issues - what you can do to help
Hi,
quantumclient is now fixed for stable/grizzly but there are issues
with check-tempest-devstack-vm
1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
requirements conflict with neutron client from earlier in the week is still
not resolved on stable/*.
Also there's an issue with quantumclient and Nova stable/grizzly:
Alan Pevec wrote:
1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
requirements conflict with neutron client from earlier in the week is still
not resolved on stable/*.
Also there's an issue with quantumclient and Nova stable/grizzly:
Yes, it should. I'll mark the bug as a stable backport
Thanks
On 10/1/13 10:51 AM, Alan Pevec ape...@gmail.com wrote:
Hi Gary,
2013/9/29 Gary Kotton gkot...@vmware.com:
Not related to the stable branches, but related to trunk. At the moment
I am
working on
On 10/01/2013 12:02 AM, Alan Pevec wrote:
1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
requirements conflict with neutron client from earlier in the week is still
not resolved on stable/*.
Also there's an issue with quantumclient and Nova stable/grizzly:
I met the same problem, I hope the situation is getting better. What can I
help?
2013-09-29 07:05:55.248 | Traceback (most recent call last):
2013-09-29 07:05:55.248 | File
/home/jenkins/workspace/gate-nova-python27/nova/tests/api/openstack/compute/contrib/test_quantum_security_groups.py,
line
@lists.openstack.org
Date: Sunday, September 29, 2013 11:15 AM
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Gate issues - what you can do to help
I met the same problem, I hope the situation is getting better. What can
1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
requirements conflict with neutron client from earlier in the week is still
not resolved on stable/*.
Also there's an issue with quantumclient and Nova stable/grizzly:
Right now the gate is extremely full, there are a number of reasons for
that. What's more important right now is to try not to make it worse
while we get resolution on things.
1) Please *do not* Approve or Reverify stable/* patches. The pyparsing
requirements conflict with neutron client from
On 09/28/2013 12:08 AM, Gareth wrote:
On Fri, Sep 27, 2013 at 9:43 PM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
Right now the gate is extremely full, there are a number of reasons
for that. What's more important right now is to try not to make it
worse
21 matches
Mail list logo
