[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1676966
Public bug reported:
This bug tracker is for errors with the documentation, use the following
as a template and remove or add fields as you see fit. Convert [ ] into
[x] to check boxes:
- [X] This doc is inaccurate in this way:
The Neutron install doc for QUEENS points to an incorrect port for
Reviewed: https://review.openstack.org/576368
Committed:
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=363fc4070df1af54a3c1a0c7b974fe032155dab6
Submitter: Zuul
Branch:master
commit 363fc4070df1af54a3c1a0c7b974fe032155dab6
Author: Hunt Xu
Date: Tue Jun 19 13:31:34
Public bug reported:
Too many DBDeadlockError and IP address collision during port creating
ENV:
Neutron stable/queens (12.0.1)
CentOS 7 (3.10.0-514.26.2.el7.x86_64)
This is a edge scenario testing after we meet bug:
https://bugs.launchpad.net/neutron/+bug/1777965
We have 3 neutron-server
Public bug reported:
ENV:
Neutron stable/queens (12.0.1)
CentOS 7 (3.10.0-514.26.2.el7.x86_64)
Ceph v10.2.9 Jewel
Exception:
2018-06-20 14:21:52.070 140217 ERROR oslo_middleware.catch_errors
DBDeadlock: (pymysql.err.InternalError) (1205, u'Lock wait timeout exceeded;
try restarting
Reviewed: https://review.openstack.org/571309
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=75da4da4761d70dca00fda042e284dcbf54d3627
Submitter: Zuul
Branch:master
commit 75da4da4761d70dca00fda042e284dcbf54d3627
Author: Lance Bragstad
Date: Mon Jun 4 20:49:14
Public bug reported:
neutron is not dropping the radvd privileges and causes that radvd run with
full privileges, that can be considered as a serious risk.
In addition, some distributions like SUSE, by default runs radvd process as a
non privileged user by default, causing radvd failure to
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Reviewed: https://review.openstack.org/553857
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=0372d82c2c5ae5651b00c5ab9e1cf5c77a8f87d9
Submitter: Zuul
Branch:master
commit 0372d82c2c5ae5651b00c5ab9e1cf5c77a8f87d9
Author: Chris Dent
Date: Fri Mar 16 16:54:14 2018 +
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Public bug reported:
It appears the landing of [1] into stable/queens has broken some
consumers, at least vmware-nsx.
When running with [1] in neutron/queens, we now get:
security_group_rule is already registered
Loaded quota_driver: .
Loaded quota_driver: .
create failed: No details.:
Marking this as invalid since there isn't anything we can do in master
short of revert the removal of UUID, issue a fix, backport it, then
remove the UUID token provider again. We also can't issue a fix directly
to stable branches according to stable policy.
I think the work-around is the best
Public bug reported:
Currently, both the registered_limit and limit tables use a UUID as the
primary key:
http://paste.openstack.org/raw/723936/
Instead of using this pattern, we can optimize for performance by using
an auto-incrementing primary key as the "internal_id" of the limit or
Public bug reported:
Unified limits consists of registered limits and limits, which are
project-specific. Both types are isolated into separate database tables
(keystone.registered_limit and keystone.limit). The following is the
existing schema for both tables:
Public bug reported:
According QoS documentation
https://docs.openstack.org/neutron/queens/admin/config-qos.html in order
to get the desired BW limit, user must set Burst value which is bigger
than 80% of provided by user BW.
--- Configuring the proper burst value is very important. If the burst
Reviewed: https://review.openstack.org/574917
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=5ceca4d9d1041345ccfeab675c8e8216050f7135
Submitter: Zuul
Branch:master
commit 5ceca4d9d1041345ccfeab675c8e8216050f7135
Author: Swaminathan Vasudevan
Date: Tue Jun 12
Reviewed: https://review.openstack.org/576535
Committed:
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=a46f7d601568a56437a0cc84c32917da9dc591bc
Submitter: Zuul
Branch:master
commit a46f7d601568a56437a0cc84c32917da9dc591bc
Author: Hunt Xu
Date: Tue Jun 19 22:34:59
Reviewed: https://review.openstack.org/575222
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=c8d5a71da69512c272c6106e837a7f2ffac87032
Submitter: Zuul
Branch:master
commit c8d5a71da69512c272c6106e837a7f2ffac87032
Author: Matt Riedemann
Date: Wed Jun 13 16:23:17 2018
Public bug reported:
[Description about Error]
I created an image and tried to update "visibility" of the image.
As a result, updating was failed.
I could update "visibility" by openstack CLI and glance CLI.
So I think that this is a bug of horizon.
[Version]
I could reproduce this error at
46 matches
Mail list logo
