** Changed in: cloud-archive
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker to agent fails
To manage notif
Marking Artful as Won't Fix since it's nearly EOL.
** Changed in: neutron-dynamic-routing (Ubuntu Artful)
Status: Fix Committed => 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/175012
This bug was fixed in the package neutron-dynamic-routing -
2:11.0.0-0ubuntu2~cloud0
---
neutron-dynamic-routing (2:11.0.0-0ubuntu2~cloud0) xenial-pike; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron-dynamic-routing (2:11.0.0-0ubuntu2) artful; urgency=med
This bug was fixed in the package neutron-dynamic-routing -
2:12.0.0-0ubuntu1.1~cloud0
---
neutron-dynamic-routing (2:12.0.0-0ubuntu1.1~cloud0) xenial-queens;
urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron-dynamic-routing (2:12.0.0-0ubuntu1.1) bionic; ur
If it needs testing in artful in order to get fixes into Pike UCA, then
IMO your process is broken. I think I spent more than enough time on
this, if you insist to prefer keeping to distribute faulty packages, so
be it.
--
You received this bug notification because you are a member of Ubuntu
Bugs
This bug was fixed in the package neutron-dynamic-routing -
2:12.0.0-0ubuntu1.1
---
neutron-dynamic-routing (2:12.0.0-0ubuntu1.1) bionic; urgency=medium
* d/p/fix-failure-when-adding-a-speaker-to-an-agent.patch: Cherry-picked
from upstream stable/queens branch to ensure adding s
Thank you for the testing. I will release 2:12.0.0-0ubuntu1.1 from
bionic-proposed to bionic-updates based on this result.
2:11.0.0-0ubuntu2 in artful-proposed still needs verifying, so I'll
reset the tag for that. We can release it to artful-updates after
someone can confirm testing for 2:11.0.0-
I successfully use neutron-dynamic-routing-common, python-neutron-
dynamic-routing and neutron-bgp-dragent in version 2:12.0.0-0ubuntu1.1
(from bionic-proposed) on bionic to provide BGP peerings with Neutron
network routes.
Host with bgp-dragent:
> lsb_release -a
No LSB modules are available.
Di
For the SRU verification to be valid, we need testers to test the exact
same binaries that are supposed to be released into -updates. The reason
for that is that the build environment can be different for different
binaries, even though the sources might be the same. The build
environment can then
I did test 2:11.0.0-0ubuntu2~cloud0 and 2:12.0.0-0ubuntu1.1~cloud0 on
Xenial. The packages seem to be identical to those in Artful and Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Tit
For Ubuntu, could somebody please confirm the package version strings
that were tested for Artful and Bionic? Before I release the tested
packages in Artful and Bionic, I want to make sure that what I'm
releasing is definitely what was tested, and specifying the package
version strings avoids any c
@Chris: The test were done successfully, I just missed that tag when
updating yesterday, sorry. Should be ready to release both artful and
bionic, as well as the corresponding UCA updates.
** Tags removed: verification-failed-bionic
** Tags added: verification-done-bionic
--
You received this bu
It looks like this might be mis-tagged verification-failed-bionic, but
it's not entirely clear to me. Can someone please confirm that this
*does* work on bionic, and then we can release the artful and bionic
packages?
Thanks!
--
You received this bug notification because you are a member of Ubun
** Tags removed: verification-needed verification-needed-artful
verification-pike-needed verification-queens-failed
** Tags added: verification-done verification-done-artful
verification-pike-done verification-queens-done
--
You received this bug notification because you are a member of Ubuntu
@Jens,
Apologies for the delay. Of course, you were correct all along. The
neutron-server node had the older version of the package. Though I
looked at that 10 times I failed to process it. My further apologies for
dragging you along for this process. This bug is resolved as far as I am
concerned.
I still fail to reproduce this locally. Can you describe the steps that are
needed to setup your CI environment? Do you see the error only in your CI or
also when you follow the steps in [1] manually?
Is this an aio setup or are neutron-api and neutron-bgp-dragent running in
different environmen
@Jens,
Some points of clarification. It is possible this is a different but
related bug. First off, no upgrade is occuring. This is a CI environment
[0] in which I do a fresh deployment of neutron and neutron-bgp-dragent
on Xenial with the Queens UCA. The deployment and initial configuration,
incl
@Dr. Jens, Thanks for testing. I'd prefer the user manually restart
neutron-server. It doesn't feel right to have neutron-dynamic-routing
postinst do a restart of neutron-server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@David: Did you also restart neutron-server after upgrading the neutron-
dynamic-routing packages? Omitting that step was the only way I could
reproduce your error during my testing on bionic.
@Corey: Do we need to place that restart into the postinst script to
make it automatic?
--
You received
@David: I have not been able to reproduce the error on xenial with
queens UCA. Your logs look like you are running without the patch
applied. Can you doublecheck that you did install the patched packages?
Can you set "debug=true" in /etc/neutron/bgp_dragent.ini and post logs
from that?
>From my PO
I've tagged the verification of this bug as failed since restart of
neutron-bgp-dragent results in a missing auth_type when attempting to
recreate the peer. add_bgp_peer_to_bgp_speaker() gets a KeyError
exception for 'auth_type' as can be seen in David's results in the
previous comment.
I cross-ch
I still see this failure when the neutron-bgp-dragent is restarted.
Bionic proposed: 12.0.0-0ubuntu1.1
The initial setup works fine:
2018-05-07 17:15:59.099 17215 INFO bgpspeaker.api.base
[req-9692824c-b285-4304-86d2-00f46df8a216 - - - - -] API method core.start
called with args: {'router_id':
Ah, o.k., well for stable/pike this is actually the only patch from
11.0.0 to 11.0.1, so maybe we can keep your version there, except that
it may be confusing to users.
In 12.0.1 there is only https://review.openstack.org/544866 which I
think may be relevant for upgrades.
Anyway if you build new
@Jens, we just don't have full test coverage for neutron-dynamic-routing
quite yet on our end so I was trying to keep the stable delta to a
minimum. If by any chance you could test corresponding releases for us
then I can prepare some stable point releases.
--
You received this bug notification b
@Corey: There are releases 11.0.1 and 12.0.1 containing the patch, so I
don't understand why you cherry-picked it instead of using the new
releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175012
Hello Dr., or anyone else affected,
Accepted neutron-dynamic-routing into artful-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/neutron-dynamic-routing/2:11.0.0-0ubuntu2 in a few hours, and then in
the -proposed repository.
Please help us by testing
Hello Dr., or anyone else affected,
Accepted neutron-dynamic-routing into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/neutron-dynamic-routing/2:12.0.0-0ubuntu1.1 in a few hours, and then in
the -proposed repository.
Please help us by testi
This bug was fixed in the package neutron-dynamic-routing -
2:12.0.0-0ubuntu2
---
neutron-dynamic-routing (2:12.0.0-0ubuntu2) cosmic; urgency=medium
* d/p/fix-failure-when-adding-a-speaker-to-an-agent.patch: Cherry-picked
from upstream stable/queens branch to ensure adding speak
I've uploaded new versions of neutron-dynamic-routing with the cherry-
picked patch to cosmic, bionic, and artful where the package is awaiting
acceptance from the unapproved queues:
https://launchpad.net/ubuntu/cosmic/+queue?queue_state=1&queue_text=
https://launchpad.net/ubuntu/bionic/+queue?que
** Also affects: neutron-dynamic-routing (Ubuntu Cosmic)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker to ag
** No longer affects: neutron-dynamic-routing (Ubuntu Cc-series)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker to agent fails
To manage notifications
** Also affects: neutron-dynamic-routing (Ubuntu Cc-series)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750121
Title:
Dynamic routing: adding speaker t
** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/pike
Importance: Undecided
Status: New
** Also affects: cloud-archive/queens
Importance: Undecided
33 matches
Mail list logo
