This doesn't look like a tempest bug to me, it looks like nova is
failing during the volume extend operation and that causes the test to
fail. For example, see:
http://logs.openstack.org/67/518967/2/check/legacy-tempest-dsvm-neutron-
** Also affects: oslo.concurrency
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1712463
Title:
taskflow not running under wsgi configuration
This isn't actually a bug in tempest, those are interfaces that will be
removed in a future version. The neutron tempest plugin is using them
which is causing the warning to be emitted. The issue is that the
neutron plugin code needs to be updated
** Changed in: tempest
Status: New =>
This isn't a tempest bug, it's also likely not a bug in keystone. It
looks like a configuration bug, apache returns 502 if mod_proxy is
unable to reach the server it's proxying to (or some other issue with
connecting to the proxy) This honestly looks like a dup of the bug that:
The fix: https://review.openstack.org/#/c/355960/ has landed and been
included in a release.
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
The binary dependencies required to run nova aren't really discoverable.
They aren't present in bindep.txt which would be the expected mechanism
for discovering them. (it's only used to install the unit test binary
requirements) This makes it difficult to figure out how to
Public bug reported:
The placement api is exposed only as a wsgi script however there is no
documentation in nova or example configuration on how to use it. While
this tends to fit into a standard mold providing users with this
guidance is very useful. Right now the docs just say deploy it
Public bug reported:
The neutron-sanity-check command has a hard dependency on ovs being
present on the system being checked, even if you have all the --noovs*
flags set. In my environment I'm running without ovs installed or
configured and I hit failures like:
Public bug reported:
The binary dependencies required to run neutron aren't present in
bindep.txt. This makes it difficult to figure out how to install neutron
from source in an environment since it's not clear what non-python
dependencies there are. We should add everything into bindep.txt to
Public bug reported:
When running neutron in an environment with a missing binary command run
by a linux agent the failure mode is far from clear. For example:
http://paste.openstack.org/show/604877/
Is what was logged on my system when I didn't have ipset installed. It's not
clear at all
Public bug reported:
When running test_stamp_pattern sometimes the test times out waiting for
the device to show up on the guest after the volume attach is issue. An
example traceback is:
Traceback (most recent call last):
File "tempest/test.py", line 103, in wrapper
** Changed in: tempest
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1586931
Title:
TestServerBasicOps: Test fails when deleting
This is really a nova bug, and not a tempest bug. Tempest exposes the
idempotent ids to enable tracking tests across renames. I don't feel
that the fact nova's cell job (which should be using config flags
instead of a giant regex anyway) isn't using this to identify tests in
its blacklist is
I see nothing in that stacktrace which is importing tempest. All the
code in this error is from the neutron repo
** Changed in: tempest
Status: New => Invalid
** Also affects: neutron
Importance: Undecided
Status: New
** No longer affects: tempest
--
You received this bug
Well I was gonna suggest the dashboard because it will show this
information, but the job is non-voting check only when it would fail so
that doesn't help. As a cool aside it does show that the change:
https://review.openstack.org/#/c/257493/ makes it noticeably slower:
Yes you are correct, this is not a tempest bug tempest made a request
and got a 500 response which is never correct. You should file the bug
against nova which is actually the cause of this failure:
http://logs.openstack.org/31/230031/2/check/gate-tempest-dsvm-full-
*** This bug is a duplicate of bug 1353962 ***
https://bugs.launchpad.net/bugs/1353962
Public bug reported:
Occasionally an overquota exception is raised by allocate_fixed_ip when
there is quite a large amount of free fixed_ip left.
For example in this tempest postgres job run:
I actually think the analysis in this bug is a bit off, looking at the
tests in question there is a bug in
tempest.api.compute.test_tenant_networks in that we should tell it to
create a network with set_network_resources() in the setupClass.
The fact its passing is actually a bug somewhere in
** Changed in: os-testr
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1482609
Title:
Intermittent py27 failure - TypeError:
Public bug reported:
Neutron does not support creating or using floating ips on an ipv6
network. When nova gets a create floating ip call and does the
passthrough call to neutron it will get a 400 response from neutron
saying there is not ipv4 subnet available. This goes unhandled by nova
and
Public bug reported:
Recently glance started logging tons of 404 tracebacks even when no
operations fail. For example:
http://logs.openstack.org/86/176786/2/gate/gate-tempest-dsvm-
full/31efa56/logs/screen-g-api.txt.gz?level=TRACE
in that gate run no tests failed and things just went along like
This bug his not in tempest, it's an internal error in nova. Tempest
interacts with nova exclusively through the REST API and is only
exposing this issue in nova.
** Changed in: tempest
Status: New = Invalid
** Also affects: nova
Importance: Undecided
Status: New
--
You
Keystone doesn't log the request ids either:
http://logs.openstack.org/48/165548/4/gate/gate-tempest-dsvm-neutron-
full/5cbdc8e/logs/apache/keystone.txt.gz?level=INFO#_2015-03-19_20_35_44_383968
request ids were only recently added to keystone with:
https://review.openstack.org/#/c/155901/ I
** No longer affects: 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/1179008
Title:
rename requires files to standard names
Status in OpenStack Telemetry (Ceilometer):
Fix
Looking through the failure logs this doesn't appear to be a tempest
issue. Tempest is just triggering a race in keystone.
** Changed in: tempest
Importance: High = Undecided
** Changed in: tempest
Status: New = Invalid
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1381379 ***
https://bugs.launchpad.net/bugs/1381379
This is not a tempest bug, neutron is returning a 500 because of an
unhandled exception. If you look in the neutron logs you'll see a
failure in the DB layer around the typing in Postgres. This failure
So I'm failing to see how this is a tempest bug, looking at the test
code it's testing exactly what it set out to. That deleting an external
network deletes all the resources (subnets, ports, etc) associated with
it. It looks like the behavior differs from what's expected on icehouse
neutron which
Public bug reported:
The .gitignore file for nova contains the line for the sample config
file, etc/nova/nova.conf.sample, twice.
** Affects: nova
Importance: Low
Assignee: Matthew Treinish (treinish)
Status: In Progress
--
You received this bug notification because you
Public bug reported:
During a tempest run occasionally a during the
tempest.api.compute.servers.test_delete_server.DeleteServersTestJSON.test_delete_server_while_in_verify_resize_state
test it will fail when the test attempts to delete a server in the
verify_resize state. The failure is
Public bug reported:
During a server create when the ec2 metadata triggers the async creation
of the network information for the server n-cpu times out waiting for
the rpc response from n-net causing the server to go into an error
state. See:
affects: tempest
status: fixreleased
** Changed in: tempest
Importance: Undecided = Critical
** Changed in: tempest
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Changed in: tempest
Status: Fix Committed = 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/1268274
Title:
KeyError in _get_server_ip
Status in OpenStack Neutron
** Changed in: tempest
Status: Fix Committed = 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/1254890
Title:
Timed out waiting for thing ... to become ACTIVE causes
** Changed in: tempest
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1294511
Title:
** Changed in: tempest
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1338844
Title:
FixedIpLimitExceeded: Maximum number of
Public bug reported:
Occasionally a neutron gate job fails because the node runs out of
memory. oom-killer is invoked and it starts killing processes to save
the node. (which just causes cascading issues) The kernel logs show that
oom-killer is being invoked by neutron-ns-meta.
An example of
Based on the age of the bug, and the lack of logs I don't think we'll be
able to make progress on this. We can open up a new bug with more detail
if we come across this again.
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member
) = Matthew Treinish (treinish)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1328738
Title:
tempest.api.image.v1.test_images.ListImagesTest fails in setup with
BadRequest - The HTTP URL
So the issue here was actually a bug in devstack-gate, which broke the
icehouse grenade jobs for tempest master which allowed this new test to
be added when it wouldn't work. It has been removed with:
So our enforcement strategy for tracking failures and traces in the logs
has changed since this was filed and this bug isn't valid any more
because of the change. But this looked liked a whitelist matching issue
when it still applied.
** Changed in: tempest
Status: New = Invalid
--
You
I've uploaded some of the logs from the test node that John mentioned
above that we held. That pastebin was just a grep of all the logs for
TRACE. I can upload any of the other service logs from the node, I just
figured these would be the most useful.
** Also affects: nova
Importance:
Public bug reported:
On a successful tempest run the following error message was in the nova
logs:
ERROR nova.network.manager [req-1ef0c266-bec4-4414-ae27-f6937e6baa2a
ListServersNegativeTestXML-tempest-117344783-user
ListServersNegativeTestXML-tempest-117344783-tenant] Unable to release
** Changed in: tempest
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1226337
Title:
** Changed in: swift
Status: New = Invalid
** Changed in: tempest
Status: New = 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/1224001
Title:
Russell, if you've got the change to unskip the bug how about you push
it out for review to close the tempest side.
** Changed in: tempest
Status: New = Invalid
** Changed in: tempest
Status: Invalid = New
** Changed in: tempest
Status: New = Triaged
** Changed in: tempest
** Changed in: tempest
Status: Confirmed = Invalid
** Changed in: tempest
Importance: Critical = Undecided
** Changed in: nova
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
46 matches
Mail list logo
