Public bug reported:
When using glance on swift with multitenant config and set
swift_store_admin_tenant tenants then such tenants are not set for container
when glance creates it. For example user is creating private image, glance will
not set proper ACLs. It will do it when user will share
Public bug reported:
Maybe glance wsgi server should log every request on INFO level as it is done
in nova or neutron. I was not find possiblity to enable it in glance.
Example log from neutron:
2015-01-13 06:31:11.944 16150 INFO neutron.wsgi [-] IP.ADDRESS - - [13/Jan/2015
06:31:11] GET
Public bug reported:
As was said in http://lists.openstack.org/pipermail/openstack-
operators/2015-June/007354.html even if policy.json is set to allow some
user with special role to see instances from different tenant this
settings are ignored and admin context is required.
** Affects: nova
Public bug reported:
In neutron in qos bw limit rule table in database and in API extension
parameter "max-burst-kbps" has got wrong units suggested. Burst should
be given in kb instead of kbps because according to for example ovs
documentation:
Public bug reported:
Currently QoS is supported by openvswitch agent (QosOVSAgentDriver) and by
sr-iov agent (QosSRIOVAgentDriver) on compute hosts.
There should be also similar agent for support LinuxBridge agent. It can set bw
limitations using "tc" which can be applied for ingress and egress
Public bug reported:
Currently fullstack tests (test_connectivity, qos) are only testing ovs
agent hosts. Support for linuxbridge agent should be added also in
fullstack tests IMO.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
licy will contain any rule which is
not supported by mechanism driver used for port binding or by mechanism drivers
used by specific binding:vnic_type if port is unbound.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos rfe
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1542
ce: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: linuxbridge ml2 qos
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
** Tags added: ml2
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
QoS traffic bandwidth limitation is applied for ingress instead of
egress traffic by Linuxbridge L2 agent.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Changed in: neutron
Assignee: (unassigned
Public bug reported:
Currently in QoS there is rule:
bandwidth_limit
and API options to manipulate with it are:
qos-bandwidth-limit-rule-create
qos-bandwidth-limit-rule-delete
qos-bandwidth-limit-rule-list
qos-bandwidth-limit-rule-show
qos-bandwidth-limit-rule-update
Those rules are only
traffic.
Such change will make consistent behaviour between Linuxbridge agent and
openvswitch agent. See on https://launchpad.net/bugs/1563720 for LB
implementation details.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: ovs
Public bug reported:
If in alembic db upgrade script function
alembic.migration.remove_fks_from_table() is used it will not remove unique
constraint for such foreign key if it was created.
There should be possibility to remove such constraints from db.
Because droping such constraints is
Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launc
** Project changed: oslo.context => 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/1660088
Title:
Huge number of deprecation warnings in oslo.context 2.12.0
Status in neutron:
Public bug reported:
Currently at least SR-IOV driver supports both QoS rules: bandwidth limit and
minimum bandwidth. User can set in one policy both of such rules and set higher
minimum bandwidth (best effor) then maximum available bandwidth for port.
IMO such behaviour will be undefined on
Public bug reported:
If QoS policy is removed from port when L2 agent is down, then it is not
removed after agent is up again. Such qos bandwidth limit rule is still
configured on port on L2 agent side (I tested ovs).
How to reproduce:
* Apply QoS policy with bandwidth limit rule to port
*
Public bug reported:
If iptables driver is used for Security groups (e.g. in Linuxbridge L2 agent)
there is an issue with update rules. When You have rule which allows some kind
of traffic (like ssh for example from some src IP address) and You have
established, active connection which match
Public bug reported:
Currently in config of metadata agent there is option to set IP address of nova
metadata service (nova_metadata_ip).
There can be situation that there is more than one nova-api service in cluster
and in such case if configured nova metadata IP will return e.g. error 500
API-ref docs merged: https://review.openstack.org/#/c/358344/
CLI docs merged: https://review.openstack.org/#/c/358345/
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: quotas
** Changed in: nova
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
TING chain.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos rfe
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Eng
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
Public bug reported:
If something like:
inspector = reflection.Inspector.from_engine(op.get_bind())
is used in alembic migration scripts in functions
expand_drop_exceptions() or contract_creation_exceptions() then there is
error like:
NameError: Can't invoke function 'get_bind', as the
--2017-06-28--
22-28-11-513301.txt.gz?level=ERROR#_2017-06-28_22_28_27_661
All QoS related full stack tests are failing because of this issue when running
on python 3.5.
On python 2.7 there is no such error.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos rfe
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to n
not allow to apply such rule to other ports.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notificatio
/TestQoSPolicyIsDefault.test_create_two_default_qos_policies_per_project
/neutron-server--2017-05-30--09-49-36-418810.txt.gz?level=TRACE
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: db fullstack gate-failure qos
** Changed
Public bug reported:
I see failed gate-neutron-docs-ubuntu-xenial in many jobs since
yesterday. It always fails with error like e.g. in
http://logs.openstack.org/60/469260/2/check/gate-neutron-docs-ubuntu-
xenial/e55b579/console.html#_2017-05-30_22_18_04_277430
** Affects: neutron
/gate-neutron-dsvm-fullstack-ubuntu-xenial/52a71ea/logs/dsvm-fullstack-logs/TestQoSPolicyIsDefault.test_update_default_status_conflict/neutron-server--2017-05-30--22-05-06-18.txt.gz#_2017-05-30_22_05_14_752
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq
turn false but few miliseconds later namespace already exists and
ip.netns.add() method fails.
It is in method ensure_namespace() in
https://github.com/openstack/neutron/blob/master/neutron/agent/linux/ip_lib.py#L204
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplons
I just tested it on my devstack (Neutron from Pike branch) with shade
client and it worked fine:
>>> import shade
>>> c = shade.openstack_cloud()
>>> c.list_qos_rule_types()
[Munch({u'type': u'dscp_marking'}), Munch({u'type': u'bandwidth_limit'})]
>>>
Public bug reported:
Update of "network:router_interface_distributed" ports cause problems
with delete QoS bandwidth limit rules. It can be observed in logs like:
http://logs.openstack.org/09/497009/4/check/gate-tempest-dsvm-neutron-
dvr-multinode-scenario-ubuntu-xenial-
Public bug reported:
Fullstack VM fixture has got "destroy()" method which is used to simulate
deletion of VM.
Unfortunately when such VM is managed by Linuxbridge agent and bridge device
don't have "delete_port()" method.
** Affects: neutron
Importance: Low
Public bug reported:
It looks that this test fails every time with same reason:
2017-12-13 05:29:35.846 | Captured traceback:
2017-12-13 05:29:35.848 | ~~~
2017-12-13 05:29:35.850 | Traceback (most recent call last):
2017-12-13 05:29:35.852 | File
Public bug reported:
When patch https://review.openstack.org/#/c/321001 was merged some UT in
projects like networking-midonet started failing. It is reported on
https://bugs.launchpad.net/networking-midonet/+bug/1731623
It looks that reason of this problem is that wrong OVO classes are
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: fullstack gate-failure qos
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1733649
Title:
fullstack
I think that it is made just by mistake. In commit message there was
info about removing "DocImpact" so it was "false-positive" IMO. If no,
please reopen it.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
I checked it once again and it looks that max_kbps attribute don't have
default value and is mandatory. So bug is only in OSC and patch for that
was already proposed.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
I agreed with Brian here and I removed neutron from affected projects
for now. This should be fixed on openstacksdk and openstackclient
** Changed in: python-openstacksdk
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
** Changed in: python-openstackclient
Assignee: (unassig
: Slawek Kaplonski (slaweq)
Status: New
** Tags: qos
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1770622
Title:
QoS bandwidth limit rule's max_kbps parameter should be mandatory
, 2 group
record(s), length 48
and that breaks somehow connectivity as packets are sent to backup node
instead of master one.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: l3-ha
--
You received this bug notificat
Public bug reported:
Fullstack and ovsfw scenario jobs are failing because of failure during loading
openvswitch kernel module. Example of failure:
* fullstack
http://logs.openstack.org/08/570008/3/check/neutron-fullstack/7df64f5/job-output.txt.gz
* ovsfw:
Public bug reported:
I saw that sometimes TestHAL3Agent.test_ha_router_restart_agents_no_packet_lost
fullstack test fails because there is really packet lost after agent's restart.
Example of such failure is on:
MAC learning table size:
ovs-vsctl set bridge other-config:mac-table-size=5
This should lower the CPU usage down substantially; allow a few seconds
for things to settle down.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags
Public bug reported:
Since few days I see that
tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest.test_tagged_attachment
in neutron-tempest-dvr job.
Example of failure: http://logs.openstack.org/90/572690/2/check/neutron-
tempest-dvr/45ec391/logs/testr_results.html.gz
It
: Critical
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1777506
Title:
neutron-rally job
It is exactly the same in master branch in neutron_tempest_plugin repo:
https://github.com/openstack/neutron-tempest-plugin/blob/7681a5cf5769211dc355e2bf8cd7499795f6de22/neutron_tempest_plugin/api/test_ports.py#L111
and I think that it's not failing only because it's skipped in gate job probably
** Project changed: neutron => tempest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1775947
Title:
tempest.api.compute.servers.test_device_tagging.TaggedAttachmentsTest
failing
then.
Solution is to use neutron-tempest-plugin-jobs-stable template from
neutron_tempest_repo in neutron/.zuul.conf file in stable/queens branch
** Affects: neutron
Importance: Critical
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure tempest
--
You
Public bug reported:
Example of failure: http://logs.openstack.org/95/572295/1/check/neutron-
fullstack/14122fa/logs/testr_results.html.gz
Happened about 50 times in last week:
Public bug reported:
Since some time we have quite often issue with unit test
neutron.tests.unit.objects.test_ports.PortBindingLevelDbObjectTestCase
.test_get_objects_queries_constant
It happens also for periodic jobs. Examples of failures from last week:
/testr_results.html.gz
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: fullstack linuxbridge
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net
://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%5C
%22neutron-
fullstack%5C%22%20AND%20message%3A%5C%22line%20264%2C%20in%20test_securitygroup%5C%22
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: fullstack sg
in Neutron control plane as it is quite common deployment
practice to use same external bridge for data plane and for control plane.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: ovs
** Changed in: neutron
For example in functional tests only MySQL and PostgreSQL backends are
tested:
https://github.com/openstack/neutron/blob/master/neutron/tests/functional/db/test_migrations.py
and I remember also that some time ago Ann Taraday said me in comment to
one of my patches that we don't support sqlite as
namespace
test-dbbb4045-363f-44cb-825b-17090f28df11, but it shouldn't
Example gate logs: http://logs.openstack.org/43/529143/3/check/neutron-
fullstack/d031a6b/logs/testr_results.html.gz
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Con
Public bug reported:
L2 extension manager which calls L2 extension drivers (like QoS) should handle
somehow exceptions from those drivers. For example ext_manager.delete_port(),
like in:
Public bug reported:
Sometimes fullstack test
neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork
fails because "ncat" process don't starts properly:
Captured traceback:
~~~
Traceback (most recent call last):
File "neutron/tests/base.py", line 132,
Public bug reported:
When Floating IP is created without QoS policy set and user want's to
add QoS policy to it with PUT request:
curl -g -i -X PUT
http://145.239.30.57:9696/v2.0/floatingips/bb2d8b79-5b09-4fe0-a8cf-
f6e011873ca2 -H "User-Agent: python-neutronclient" -H "Accept:
application/json"
Public bug reported:
It looks that connection to ovsdb is not mocked in test:
neutron.tests.unit.services.logapi.agent.test_log_extension.LoggingExtensionTestCase.test_handle_port_vm
and that cause problem with UT when openvswitch is not installed on
host:
Captured traceback:
sdb: Port
b191da42-6eca-4ba3-a12b-244b07e6fe45 is not managed by this agent..:
OVSFWPortNotFound: Port b191da42-6eca-4ba3-a12b-244b07e6fe45 is not managed by
this agent.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: ovs
Patch https://review.openstack.org/#/c/541512/ fixed this issue also
** Changed in: neutron
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1745386
and is covered in
https://bugs.launchpad.net/neutron/+bug/1747709)
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure ovs-fw
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You recei
Public bug reported:
Quite often tests like
neutron.tests.fullstack.test_connectivity.TestUninterruptedConnectivityOnL2AgentRestart.test_l2_agent_restart
are failing because of timeout while executing ovsdb commands.
Because of this issue test environment is not prepared and test fails.
Public bug reported:
Sometimes in tests like
"neutron.tests.fullstack.test_connectivity.TestOvsConnectivitySameNetworkOnOvsBridgeControllerStop.test_controller_timeout_does_not_break_connectivity_sigterm(VLANs,openflow-native)"
there is timeout error during waiting for all vms to be boot.
connected to this network, will automatically have added to iptables rule
to allow incoming dhcp traffic.
** Affects: neutron
Importance: Undecided
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: rfe
--
You received this bug notification because you are a membe
Public bug reported:
Functional test from neutron.tests.functional.db.migrations module are
sometimes failing in Neutron check queue.
Example of such failure: http://logs.openstack.org/50/533850/34/check
/neutron-functional/30ee01c/logs/testr_results.html.gz
** Affects: neutron
Importance:
Public bug reported:
I found it failed at least 3 times during last week:
http://logs.openstack.org/63/577463/4/check/neutron-tempest-dvr-ha-multinode-full/612982d/logs/testr_results.html.gz
ld be fixed in neutron's code instead of test as this isn't
test-only issue.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: l3-ha
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received t
irros it's not available.
So this test should be skipped if "image_is_advanced=False"
** Affects: neutron
Importance: Low
Assignee: Slawek Kaplonski (slaweq)
Status: In Progress
** Tags: tempest
** Changed in: neutron
Importance: Undecided => Low
--
Public bug reported:
Tests from module neutron.tests.functional.agent.l3.test_ha_router.L3HATestCase
are failing 100% times since few days in stable/queens branch.
Example of failure:
http://logs.openstack.org/78/593078/1/check/neutron-functional/28fe681/logs/testr_results.html.gz
** Affects:
Public bug reported:
Since few days all migration tests from DVR router fails.
Example of failure:
http://logs.openstack.org/37/382037/71/check/neutron-tempest-plugin-dvr-multinode-scenario/605ed17/logs/testr_results.html.gz
May be related somehow to https://review.openstack.org/#/c/589410/ but
Public bug reported:
Example of recent failures:
* http://logs.openstack.org/59/596959/1/check/neutron-tempest-plugin-
scenario-linuxbridge/f62f1c6/job-output.txt.gz
* http://logs.openstack.org/18/591818/3/check/neutron-tempest-plugin-
scenario-linuxbridge/212183e/job-output.txt.gz
*
Public bug reported:
Example of failure: http://logs.openstack.org/37/382037/73/gate
/openstack-tox-pep8/7f200e6/job-
output.txt.gz#_2018-09-06_17_48_34_700485
It is probably because of new eventlet = 0.24.0 used now.
** Affects: neutron
Importance: Critical
Assignee: Slawek Kaplonski
Public bug reported:
Filtering Port OVO objects based on security groups which ports are using don't
work properly. There was patch https://review.openstack.org/#/c/475283/ which
should provide such feature but it looks that it doesn't work.
Result of such filtering can be checked in results of
tests.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: fullstack gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchp
/testr_results.html.gz
Same issue appears sometimes in dvr scenario job but it is not so often
probably because it is multinode job and load on host is maybe lower so
instances can boot faster.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status
nchpad.net/neutron/+bug/1720205
[3]
http://logs.openstack.org/07/525607/12/check/neutron-tempest-plugin-scenario-linuxbridge/09f04f9/logs/screen-q-agt.txt.gz?level=WARNING
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: linuxbr
Public bug reported:
I checked results of neutron-tempest-dvr-ha-multinode-full for about 50
patches and I found that quite common reason of failures is problem with
SSH to instance via Floating IP address.
Example of such failed tests are:
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Changed in: neutron
Assignee: (unassigned) => Slawek Kaplonski (slaweq)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: ovs
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1763604
Title:
neutron-ovs-cleanup
As there is no hits in Neutron jobs in last 30 days I will remove
Neutron from affected projects for now. If we will hit it again, we can
add it back here
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
In about 40% of test runs tests like:
neutron_tempest_plugin.scenario.test_trunk.TrunkTest.test_trunk_subport_lifecycle,
example runs:
*
http://logs.openstack.org/03/560703/7/check/neutron-tempest-plugin-dvr-multinode-scenario/1f67afd/logs/testr_results.html.gz
*
Public bug reported:
In about 20-30% of runs neutron-rally-neutron job fails because global job's
timeout is reached.
Example failed runs:
*
http://logs.openstack.org/24/558724/11/check/neutron-rally-neutron/d891678/job-output.txt.gz
*
Public bug reported:
Periodic job neutron-dynamic-routing-dsvm-tempest-with-ryu-master-scenario-ipv4
is failing all the time since about 21.04.2018.
Example log from failed run:
other changes made to ext_net_A between
sharing and unsharing it.
Neutron should be able to unshare the network since the only tenant using it
(tenantB) is already covered by a specific RBAC rule created in step 5.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq
so it will be no
any race with other tests.
** Affects: neutron
Importance: Wishlist
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: fullstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron
As there is no any activity on this bug and Ocata is now in phase III of
support (only security bug fixes) I think that we should close this bug.
** Changed in: neutron
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
Example of failure logs:
http://logs.openstack.org/43/540943/7/check/neutron-fullstack/5746360/logs/testr_results.html.gz
but I saw it happen at least 3-4 times during last 2 days.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq
address from
device.
** Affects: neutron
Importance: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure l3-dvr-backlog
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https
/check/neutron-tempest-plugin-scenario-linuxbridge/b02500e/logs/testr_results.html.gz
** Affects: neutron
Importance: Critical
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure qos scenario
--
You received this bug notification because you
Public bug reported:
It looks that QoS for FIP in DVR router doesn't work.
Scenario test is failing all the time with error like:
http://logs.openstack.org/63/555263/3/check/neutron-tempest-plugin-dvr-multinode-scenario/e7c012f/logs/testr_results.html.gz
>From what I found in job logs it looks
I think that this issue is related more to how OpenStack client handles such
errors returned from API and You should open it against OSC in storyboard.
Neutron is reporting correctly that this rule type is not supported by this
backend.
** Changed in: neutron
Status: New => Invalid
**
: High
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: gate-failure unittest
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1779077
Title:
Unit test jobs
Public bug reported:
It happens now quite often that tempest related tests in neutron are failing
because of reaching global job timeout.
Example of such failure:
http://logs.openstack.org/61/566961/4/check/neutron-tempest-iptables_hybrid/c70896b/job-output.txt.gz
We need to investigate why
Public bug reported:
Fullstack test
neutron.tests.fullstack.test_securitygroup.TestSecurityGroupsSameNetwork.
test_securitygroup again fails quite often for iptables based firewall
driver.
Example of failure: http://logs.openstack.org/46/571546/7/gate/neutron-
Thx Eric, So I will remove neutron from affected projects then.
** 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/1795180
Title:
openstack client router list
All such issues were only spotted in one patch
https://review.openstack.org/#/c/610280/ and it looks for me that it could be
related to the change from this patch.
I don't think we have any issue with this test in fullstack jobs for now.
** Changed in: neutron
Status: New => Incomplete
It looks that in some cases such test can take longer than 300 seconds
and there are still failures there. See:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22in%20test_walk_versions%5C%22%20AND%20filename%3A%5C
%22job-output.txt%5C%22
** Changed in: neutron
1 - 100 of 760 matches
Mail list logo
