Reviewed: https://review.openstack.org/409010
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=34f1201a2f1250d77ca21c51e89c2edd313c8597
Submitter: Jenkins
Branch:master
commit 34f1201a2f1250d77ca21c51e89c2edd313c8597
Author: “Richard
Date: Fri
Public bug reported:
eg. http://logs.openstack.org/11/410511/2/check/gate-neutron-vpnaas-
dsvm-api-ubuntu-xenial-nv/7e31cf8/logs/screen-neutron-vpnaas.txt.gz
2016-12-14 03:50:37.103 1970 ERROR oslo_messaging.rpc.server
[req-3b108eca-b4cb-470e-be8e-d20d2829974e tempest-BaseTestCase-373340779 -]
Public bug reported:
when use rally to test openstack,I meets a error that run 4times failure
1time.details info as follow:
Iteration Exception type Exception message
► 4 ClientException Unexpected API Error. Please report this at
http://bugs.launchpad.net/nova/ and attach
** Project changed: nova => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1649747
Title:
XenAPI: With ovs polling mode, Neutron gets the error of
Public bug reported:
Can not create a provider network if just config ml2_vlan_range like
"vlan_net".
cmd1: openstack network segment create net-name --physical-network vlan_net
--network f5cfe320-f5bb-41b1-b39f-ee5c32f8f356 --network-type vlan
cmd2: neutron net-create
Public bug reported:
When enabled polling mode for XenAPI, the neutron q-domua always get the
error of oslo_rootwrap.wrapper.FilterMatchNotExecutable. See the
following log.
With ovs polling mode, ovs will report data to neutron once any ovs DB
update. So there is chance to report partialy data
Reviewed: https://review.openstack.org/407311
Committed:
https://git.openstack.org/cgit/openstack/neutron-fwaas/commit/?id=37709b3e99eb29f359b4ed744a0fe691f24a3229
Submitter: Jenkins
Branch:master
commit 37709b3e99eb29f359b4ed744a0fe691f24a3229
Author: Ha Van Tu
Date:
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: networking-midonet
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Reviewed: https://review.openstack.org/349863
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=6ab20bc52392ea3eb4dcc1573fc842558eeb889e
Submitter: Jenkins
Branch:master
commit 6ab20bc52392ea3eb4dcc1573fc842558eeb889e
Author: Takashi NATSUME
Reviewed: https://review.openstack.org/406428
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=21bb77667007b0b140c17d9104204943c4a0f4cc
Submitter: Jenkins
Branch:master
commit 21bb77667007b0b140c17d9104204943c4a0f4cc
Author: Brian Haley
Date:
Reviewed: https://review.openstack.org/391113
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4a09c2210b3c07343411a06c676c2d85aa0e214f
Submitter: Jenkins
Branch:master
commit 4a09c2210b3c07343411a06c676c2d85aa0e214f
Author: Prashanth kumar reddy
Reviewed: https://review.openstack.org/385686
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a2d7ebd39b99db9c5728e2a256568b8bbbc4734f
Submitter: Jenkins
Branch:master
commit a2d7ebd39b99db9c5728e2a256568b8bbbc4734f
Author: EdLeafe
Date: Wed Oct 12
Reviewed: https://review.openstack.org/407147
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=4a5ecf1e29c3bdbb022f98a5fba41d4e7df56d88
Submitter: Jenkins
Branch:master
commit 4a5ecf1e29c3bdbb022f98a5fba41d4e7df56d88
Author: Timofey Durakov
Date:
Reviewed: https://review.openstack.org/401458
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=fd3bf3327cada36ef57eefebabc78a112298be8d
Submitter: Jenkins
Branch:master
commit fd3bf3327cada36ef57eefebabc78a112298be8d
Author: Sławek Kapłoński
Date:
Reviewed: https://review.openstack.org/409984
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=5d3ae79455d1e601a1a718a274796a2354bf31e8
Submitter: Jenkins
Branch:master
commit 5d3ae79455d1e601a1a718a274796a2354bf31e8
Author: Matt Riedemann
Date: Mon
Public bug reported:
https://review.openstack.org/401458
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/neutron" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
Public bug reported:
The following check jobs fail intermittently. When one fails the other
usually succeeds.
- gate-neutron-fwaas-v2-dsvm-tempest
- gate-neutron-fwaas-v2-dsvm-tempest-multinode-nv
Here is an example of the multinode failing but the singlenode
succeeding:
- singlenode fail:
Thanks, what I did to get it right, install devstack again on a new vm, so it
worked
** Changed in: glance
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
** Changed in: cloud-archive
Status: New => Fix Released
** Changed in: cloud-archive
Importance: Undecided => High
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
commit 9837cb15b84fea92ffce3306d14160a8c11b1c65 is included in mitaka
and above, so I'm marking this as fix released for python-cryptography
in Ubuntu. We'll target a fix for the Liberty cloud-archive.
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects:
** Project changed: neutron => octavia
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1577541
Title:
Neutron-LBaaS v2: TLS Listeners Functional Tests
Status in octavia:
In Progress
Public bug reported:
Running a "previously happy on Mitaka" cleanup script which included a:
neutron port-list --all-tenants --limit -1
command now returns an error under Newton:
stack@np-cp1-c0-m1-mgmt:~/rjones2$ neutron port-list --all-tenants --limit -1
Bad limit request: Limit must be an
** Project changed: neutron => octavia
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1646770
Title:
lbaas tempest test cases are not executing
Status in octavia:
In Progress
Bug
This is an upstream issue. Linking bug to nova.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: openstack-ansible
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1627044
Title:
Last chance call to neutron if VIF plugin notification is lost
Status in OpenStack Compute
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1642167
Title:
Move neutron.common.utils.wait_until_true to neutron-lib
Branch got created.
** Changed in: neutron
Status: New => Fix Released
** Changed in: networking-odl
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
The Keystone token flush job can get into a state where it will never
complete because the transaction size exceeds the mysql galara
transaction size - wsrep_max_ws_size (1073741824).
Steps to Reproduce:
1. Authenticate many times
2. Observe that keystone token flush job
The v3 documentation is still incorrect.
** Changed in: keystone
Status: Invalid => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1634568
Title:
this looks OK to me now...
stevemar@ubuntu:/opt/stack$ source ~/devstack/openrc admin admin
WARNING: setting legacy OS_TENANT_NAME to support cli tools.
<>
stevemar@ubuntu:/opt/stack$ openstack token issue
++---+
| Field | Value
Public bug reported:
I installed Keystone with the ubuntu guide
(http://docs.openstack.org/newton/install-guide-ubuntu/index.html), but
with postgresql backend.
At http://docs.openstack.org/newton/install-guide-ubuntu/keystone-
users.html I get following reported error:
python-neutronclient has been deprecated. Any changes will need to be
made in python-openstackclient.
** Changed in: python-neutronclient
Status: In Progress => Won't Fix
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Changed in:
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
I did an analysis on the change. The changes will have to be made on
neutron-server and neutronclient(CLI). Here are the list of changes that
will be done
Neutronclient side-
1. A new command to be added.
2. A new resource to be created
3. The resource will take subnet-id and return available
Public bug reported:
Seen here:
http://logs.openstack.org/04/409904/2/check/gate-grenade-dsvm-neutron-
multinode-live-migration-
nv/78de48c/logs/new/screen-n-api.txt.gz#_2016-12-13_03_02_15_500
2016-12-13 03:02:15.500 8323 INFO nova.api.openstack.wsgi [req-
54d8956d-3289-418b-a05f-4f85910d83d8
Public bug reported:
There are certain workloads that require the ability to define IPv4 Link
Local addresses dynamically, as defined in RFC3927.
The openvswitch_firewall service allows for IPv6 link local addresses
(likely because they are deterministic), but does not account for IPv4
Link
Public bug reported:
following jobs are failing
gate-neutron-vpnaas-dsvm-api-ubuntu-xenial-nv
gate-neutron-vpnaas-dsvm-functional-ubuntu-xenial
eg. http://logs.openstack.org/78/408878/1/check/gate-neutron-vpnaas-
dsvm-functional-ubuntu-xenial/31c0c21/console.html
2016-12-13 03:23:23.122072 | +
@John: I don't see that different drivers may have different validation rules
please see [0] and [1].
Could you please show an example when different rules are applied on per driver
basis?
[0]
https://github.com/openstack/neutron/blob/master/neutron/services/trunk/plugin.py#L281
[1]
@Vasyl Please read the linked documentation. The OVS driver requires
segmentation_id/type, and is rejecting your requests because of that.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
@John thanks for your notice. What is the neutron base case? I've
deployed Neutron with ovs and segmentation_id/type are required fields
when adding subports. Could you please an example of configuration when
they are generated automatically?
** Changed in: neutron
Status: Invalid => New
I have no idea what the issue here is, please update the description
with a stacktrace or how to recreate the problem. The bug title also
references a file that is not in the Keystone project.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because
Public bug reported:
Our api-ref in neutron-lib repo now should be made the different
parameters more meaningful.
Such as :
The "status" "status_1" ... "status_10", these parameters is not friendly.
Also "shared_X" and so on.
So we should correct them with some worthly parameter name.
**
Reviewed: https://review.openstack.org/385177
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=df4cf3e5db2166b67c9e95b381ec19ace10d0279
Submitter: Jenkins
Branch:master
commit df4cf3e5db2166b67c9e95b381ec19ace10d0279
Author: Sivasathurappan Radhakrishnan
These parameters are optional in the neutron base case, but can be
required by the driver. See https://github.com/openstack/openstack-
manuals/blob/master/doc/networking-guide/source/config-
trunking.rst#operation
** Changed in: neutron
Status: New => Invalid
--
You received this bug
Public bug reported:
I have project A with user Anna, who has a role representing nova admin
assigned (needed to allow creation of private flavors).
I have project B with user Ben, who has a role representing nova admin assigned
(needed to allow creation of private flavors).
Anna has no
Public bug reported:
According to Neutron trunk specification [0] segmentation_id and
segmentation_type are optional fields. But when we adding subport to
trunk requests without segmentation_id/segmentation_type are failing.
Example:
$ openstack network trunk set --subport port=port2 trunk10
** Changed in: glance
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1640442
Title:
glance image-tag-update, not updating a tag whose length is more
Public bug reported:
Description
===
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/designer.py#L61
sets the script path of an ethernet interface to ""
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/config.py#L1228
checks script for None. As it is not
Public bug reported:
issue : qos policy attached to network, qos_policy_id is reflecting on
neutron net-show , but not on the port with neutron port-show
(neutron) net-list
+--+--+-+
| id
Public bug reported:
When disassociate qos with network, the ml2 mechanism drivers will still
be notified that the network has the stale qos policy.
This bug can be observed after cd7d63bde92e47a4b7bd4212b2e6c45f08c03143
The same issue will not happen for port.
neutron --debug net-update
50 matches
Mail list logo