Both issue still happening even with nova network when you try to access
the machine via floating IP, after rebuild or reboot.
** Changed in: nova
Status: Invalid = New
** Changed in: tempest
Status: In Progress = New
--
You received this bug notification because you are a member
Public bug reported:
Failed to rebuild a server with neutron and floating_ip.
n-cpu error:
Setting instance vm_state to ERROR
Traceback (most recent call last):
File /opt/stack/new/nova/nova/compute/manager.py, line 5078, in
_error_out_instance_on_exception
yield
File
May be important fact, the above operations are done as admin, but the
public network belongs to the 'demo' user.
As demo user the above series are working.
If this is permission issue, maybe one of the operations needs to be denied
even before the first boot,
if it ok in permission view point
It looks like a nova issue, adding nova to the afflicted projects.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: tempest
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Is tempest did anything incorrectly ?
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: tempest
Status: New = Incomplete
--
You received this bug notification because you are a member of
10 results in logstash with Current status: HARD_REBOOT .
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
** Project changed: tempest = 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/1239891
Title:
tempest.api.object_storage.test_account_services.AccountTest fails
under
** Also affects: glance
Importance: Undecided
Status: New
** Also affects: swift
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
Public bug reported:
In this grenade job
http://logs.openstack.org/63/62463/3/gate/gate-grenade-dsvm/4a94d81/console.html
One process tries to list ALL security groups :
2013-12-19 06:42:11.519 15319 INFO tempest.common.rest_client [-] Request: GET
Public bug reported:
This test is not gating with neutron at the moment, but I see it is
failing very frequently, it is part of the full tempest run, but not
part of the smoke runs.
The tempest exception and request is attached.
Exception:
NotFound: Object not found
Details: itemNotFound
Public bug reported:
The issue seen with nova network.
test_reboot_server_hard tempest test failed.
http://logs.openstack.org/58/68058/3/check/check-tempest-dsvm-full/5b5e95d/console.html
2014-02-02 10:26:05.058 | Traceback (most recent call last):
2014-02-02 10:26:05.058 | File
** Also affects: tempest
Importance: Undecided
Status: New
** Changed in: tempest
Importance: Undecided = Critical
** Changed in: tempest
Assignee: (unassigned) = Attila Fazekas (afazekas)
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Changed in: nova
Status: Confirmed = Invalid
** Changed in: neutron
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/1274121
Title:
The server must be always delete-able (unless it is lock-ed).
One of the reason of removing the whitebox tests was, the servers become always
delectable.
** Changed in: nova
Status: Invalid = New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
When listing ~4096 instances, the nova API (n-api) service has high CPU(100%)
usage because it does individual SELECTs,
for every server's block_device_mapping.
Please use more efficient way for getting the block_device_mapping, when
multiple instance queried.
This line
Public bug reported:
Keystone defines the project/user/domain IDs as varchar(64), but neutron
uses varchar(255) on every resources.
But the tenant id actually generated by keystone is 32 character.
Please change to the tenant id lengths to =64 =32.
The record size has impact on the memory
Public bug reported:
Keystone uses 32 byte/character domain/user/project id , which contains
a hexadecimal representation of 128 bit (16 byte) integer.
Please reduce the filed size at least to 32 byte varchar, it helps to
the db for using the caches (disk/ memory/ record per physical sector..)
Public bug reported:
creating a datetime object is more expensive then any other type used in
the database.
Creating the datetime object is expensive especially for mysql drivers,
because creating the object from a datetime string representation is
expensive.
When listing 4k instances with
*** This bug is a duplicate of bug 1194579 ***
https://bugs.launchpad.net/bugs/1194579
** Changed in: nova
Status: Invalid = New
--
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/1357677
Title:
Instances failes to boot from volume
Status in OpenStack
Public bug reported:
Neutron at the moment have very limited capabilities for handling in
tenant network multicast/unknown/broadcast traffic.
Not just the ARP/DHCP traffic need to be considered, for example
applications like inifinispan can and prefers to use multicast for
communication.
vxlan
Public bug reported:
Steps to reproduce as admin:
1. create an aggregate (ID 1)
$ nova aggregate-create foo
2. curl -i http://127.0.0.1:8774/v2/`keystone token-get | awk '/ tenant_id
/{print $4}'`/os-aggregates/1/action -X POST -H Content-Type:
application/json -H X-Auth-Token: `keystone
Since basically the ichehouse of openstack expected to work with havana
config, and the grenade expected do to nothing special, I'll remove
grenade from the affected components.
Since the root cause of this issue not really keystone, it is more like
a gating confgi issue, I remove keystone as
Public bug reported:
http://logs.openstack.org/30/92630/1/check/check-neutron-dsvm-
functional/209a36f/console.html
check-neutron-dsvm-functional failed on a stable/icehouse change.
neutron.tests.functional.agent.linux.test_async_process.TestAsyncProcess.test_async_process_respawns
AFAIK Detecting a not accelerated qemu as hypervisor is not an easy task
even on a booted system [1].
When the image is UEC (the kernel image) is separated, nova would be able to
pass no_timer_check as kernel parameter.
This is only required when the CONF.libvirt.virt_type=qemu.
Linux
message:ServiceCatalogException AND tags:horizon_error.txt 11 hit in
7 days.
Public bug reported:
This test boots two server almost at the same time (starting the second
instance before 1 first active),
waits until both server is ACTIVE.
Than creates the first snapshot create:
** Also affects: nova
Importance: Undecided
Status: New
--
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/1316926
Title:
failed to reach ACTIVE status and task
http://logs.openstack.org/76/71476/16/check/check-tempest-dsvm-neutron-
heat-slow-icehouse/d066094/logs/screen-q-vpn.txt.gz
Normally two reuters needs to be created in heat job.
But only one created by the q-svc.
e6da91c3-01b0-4963-9359-96a3cdf4b824 not found.
** Also affects: neutron
check-grenade-dsvm-icehouse gate job failed with this bugs signature:
http://logs.openstack.org/99/91899/2/check/check-grenade-dsvm-
icehouse/d18de65/logs/old/screen-n-cpu.txt.gz?level=ERROR#_2014-06-04_04_25_35_546
** Changed in: nova
Status: Invalid = Confirmed
--
You received this
The net 10.0.3.0 used by both the host and by test_neutron_resources.
test_neutron_resources must use a different range.
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
http://logs.openstack.org/59/99559/4/check/check-tempest-dsvm-postgres-
full/be6a190/console.html.gz#_2014-06-13_21_20_11_328
The volume attache did not happen in normal time.
(The failed change is completely unrelated to this).
** Affects: nova
Importance: Undecided
Public bug reported:
Fedora-x86_64-20-20140407-sda has 2 GiB virtual size.
$ nova boot fed_1G_2 --image Fedora-x86_64-20-20140407-sda --flavor 1
--key-name mykey
$ nova show fed_1G_2
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1311500
Title:
Nova 'os-security-group-default-rules' API does not
Public bug reported:
Public bug reported:
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1329546
Title:
Upon rebuild instances might never get to Active state
The same logstash query founds this error in another jobs, and they are
runtime issues.
http://logs.openstack.org/94/105194/2/check/check-tempest-dsvm-postgres-
full/f029225/logs/screen-n-net.txt.gz#_2014-07-07_17_24_19_012
** Also affects: nova
Importance: Undecided
Status: New
--
Public bug reported:
q-svc frequently tries to iterate on None Type.
The job can succeed even if this issue happens.
message: Exception during message handling AND message:NoneType AND
message:object is not iterable AND filename:logs/screen-q-svc.txt
Public bug reported:
$subjecyt style exception appears both in successful and failed jobs.
message: Exception during message handling AND message:Pool AND
message:could not be found AND filename:logs/screen-q-svc.txt
Public bug reported:
message: KeyError: 'image_id' AND tags:screen-n-api.txt
The issue first appeared at 2014-07-17T16:36:43.000.
Public bug reported:
The issue usually not fatal, but nova MUST not return 500 on these
requests.
http://logs.openstack.org/73/104673/6/check/check-tempest-dsvm-neutron-full/a1ee0ee/logs/screen-n-api.txt.gz#_2014-07-22_17_15_25_548
2014-07-22 17:15:25.547 AUDIT
Public bug reported:
message: Failed to terminate process AND
message:'InstanceNotRescuable' AND message: 'Exception during message
handling' AND tags:screen-n-cpu.txt
The above log stash-query reports back only the failed jobs, the 'Failed to
terminate process' close other failed rescue tests,
Public bug reported:
VM creation failed due to a `shortage` in fixed IP.
The fixed range is /24, tempest normally does not keeps up more than ~8
VM.
message: FixedIpLimitExceeded AND filename:logs/screen-n-net.txt
Public bug reported:
As admin, I cannot list all neutron security groups with nova.
# neutron security-group-list
+--+-+--+
| id | name| description
|
Public bug reported:
screen-n-sch.txt:
2014-02-24 22:43:41.502 WARNING nova.scheduler.filters.compute_filter
[req-ff34935c-c472-47df-ac4a-1286a7944b17 demo demo] ram:6577 disk:75776
io_ops:9 instances:14 has not been heard from in a while
2014-02-24 22:43:41.502 INFO nova.filters
Public bug reported:
http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/logs/screen-n-cpu.txt.gz?#_2014-03-07_21_40_48_264
http://logs.openstack.org/43/76643/2/check/check-tempest-dsvm-postgres-full/f0dc486/console.html.gz#_2014-03-07_22_05_12_857
** Project changed: openstack-ci = nova
--
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/1291835
Title:
Repeated volume attche can cause u'message': u'The supplied device
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1291694
Title:
test_add_list_remove_router_on_l3_agent is unstable
Public bug reported:
logstash:
message:failed: Maximum attempts reached AND build_branch:master
Is a very frequent issue again.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Log stash:
message: Object GET failed AND filename:logs/screen-g-api.txt
53 failure in the past 7 days.
http://logs.openstack.org/43/76543/1/gate/gate-tempest-dsvm-full/30a3ee1/console.html#_2014-03-14_18_26_47_575
Test runner worker pid: 1541
** Changed in: neutron
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1182883
Title:
List servers matching a regex fails with Quantum
Status in
** Also affects: ceilometer
Importance: Undecided
Status: New
--
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/1271706
Title:
Misleading warning about MySQL
** Also affects: heat
Importance: Undecided
Status: New
--
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/1271706
Title:
Misleading warning about MySQL
Public bug reported:
# nova-manage db archive_deleted_rows 10 fails with postgresql, when
I do not have at least 10 rows for archive.
# nova delete 27d7de76-3d41-4b37-8980-2a783f8296ac
# nova list
** Also affects: neutron
Importance: Undecided
Status: New
** 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/1251784
Title:
nova+neutron scheduling
Public bug reported:
After parsing a lot of log files related to check failure, looks like the q-vpn
at the time when I would expect to add
floating ip , it destroys the router's qg- and qr- interfaces.
However after the floating ip deletion request the q-vpn service
restores the qg-, qr-
Public bug reported:
This is likely some download/install related issue.
http://logs.openstack.org/18/92018/3/gate/gate-neutron-python27/b57b3c6/console.html
The py26 version of this job was successful.
** Affects: neutron
Importance: Undecided
Status: New
** Affects:
tempest change: https://review.openstack.org/#/c/62702/
** Changed in: tempest
Status: In Progress = 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/1112912
Title:
Public bug reported:
http://logs.openstack.org/08/92608/1/gate/gate-tempest-dsvm-postgres-
full/57b137a/console.html.gz
2014-05-09 21:44:09.857 | Captured traceback:
2014-05-09 21:44:09.858 | ~~~
2014-05-09 21:44:09.858 | Traceback (most recent call last):
2014-05-09
Public bug reported:
http://logs.openstack.org/52/73152/8/check/check-tempest-dsvm-
full/9352c04/console.html.gz#_2014-05-13_18_12_38_547
At client side the only way to know an instance action is doable is to
making sure the status is a permanent status like ACTIVE or SHUTOFF and
no action in
Public bug reported:
Public bug reported:
In this [1] grenade job, both test_get_ca_certificate and
test_get_certificates failed [2].
The 404 also visible in the keystone log [3] .
I do not knew why the CA cart not always visible, but is should.
[1]
This test just recently merged https://review.openstack.org/#/c/87750/,
looks like the grenade is not ruining on tempest changes.
** Also affects: grenade
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
** Also affects: tempest
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1320670
Title:
404 on GET /v3/OS-SIMPLE-CERT/ca at grenade
Status
** Changed in: tempest
Status: Fix Released = New
** Changed in: tempest
Importance: Undecided = Critical
** Changed in: tempest
Status: New = Triaged
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
It looks like a nova issue.
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: tempest
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
It is a base class since long.
With python2.6 when I use nosetests the skip exceptions from
setUpClasses are considered as ERRORs instead of skip.
** Changed in: tempest
Status: New = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering
** Changed in: nova
Status: Invalid = New
--
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/1006725
Title:
Incorrect error returned during Create Image and multi
Public bug reported:
All nova conductor worker process attempts to join to the service on the same
host. It does not seams required.
If you have 48 conductor worker on a node, it means it tries to maintain the
membership with all 48 worker.
Since the workers are started almost at the same
This bug points to the number of queries made, you do not really need to
measure anything to see doing 4096 query in a loop is bad instead if
doing only one (or smaller group).
for id in ids:
SELECT attr from table where ID=id;
vs.
SELECT attr from table where ID in ids;
Mysql default max
Public bug reported:
servicegroup_driver = mc
memcached_servers = blabla # blabla does not exists
Neither n-cpu or n-api log indicates any connection issue or give any
clue the join was unsuccessful, the n-cpu logs the same two DEBUG line
regardless to the success.
The services are reported
Public bug reported:
MemcachedDriver get_all method calls the is_up for every record which requests
for a single key, instead of using a more efficient get_multi
https://github.com/linsomniac/python-memcached/blob/master/memcache.py#L1049
which is able to retrieve multiple records with a
** Changed in: neutron
Status: Expired = New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1342961
Title:
Exception during message handling: Pool FOO could not be found
Status
Restoring it new since it still happens very frequently. Tempest just
using 4 client in parallel and spent most if it's time in sleep.
Is there any way to make neutron to handle the load, for example by
increasing the number of workers ?
** Changed in: neutron
Status: New = Opinion
--
Public bug reported:
/usr/lib64/python2.7/site-
packages/sqlalchemy/sql/default_comparator.py:35: SAWarning: The IN-
predicate on instances.uuid was invoked with an empty sequence. This
results in a contradiction, which nonetheless can be expensive to
evaluate. Consider alternative strategies
23349 TRACE nova.openstack.common.policy
https://github.com/openstack/nova/blob/e53cb39c298d84a6a8c505c70bf7ceff43173947/etc/nova/policy.json#L165
** Affects: nova
Importance: Undecided
Assignee: Attila Fazekas (afazekas)
Status: In Progress
--
You received this bug
Public bug reported:
I see similar message in non dvr setups as mentioned in #1371696.
Public bug reported:
After #1356679 the debug logging became too verbose.
Logging the policy rule checking is useful when you are editing the
policy.json, but for general usage it is too verbose.
http://logs.openstack.org/53/130753/1/check/check-tempest-dsvm-neutron-
Public bug reported:
ml2_vxlan_allocations, ml2_gre_allocations, ml2_vlan_allocations tables
has field named 'allocated'.
These tables frequently used by similar queries:
SELECT ml2_vxlan_allocations.vxlan_vni AS ml2_vxlan_allocations_vxlan_vni,
ml2_vxlan_allocations.allocated AS
Public bug reported:
xen driver uses the os_type property which is not in
https://github.com/openstack/glance/blob/master/etc/schema-image.json.
libvirt has several additional properties
https://wiki.openstack.org/wiki/LibvirtCustomHardware .
The default schema specification should not
Public bug reported:
When neutron configured with, in regular devstack job it Fails to create
several networks in regular tempest run.
iniset /etc/neutron/neutron.conf DEFAULT api_workers 4
http://logs.openstack.org/82/140482/2/check/check-tempest-dsvm-neutron-
** No longer affects: tempest/havana
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1253896
Title:
Attempts to verify guests are running via SSH fails. SSH connection to
guest does
Public bug reported:
Looks like there are 2 reason for seeing 500 errors on not existing ec2
security group delete attempt:
* Unexpected TypeError raised: expected string or buffer
* Unexpected UnboundLocalError raised: local variable 'group' referenced
before assignment
Since it is server
Change for changing the global requirements
https://review.openstack.org/#/c/146049/.
Adding nova for implementing HMAC-V4 support.
Nova expects a 'Signature' named header, which is now part of the
'Authorization'.
The issue can be reproduced with euca2ools:
# source
Public bug reported:
The conductor is consuming messages form single queue which has performance
limitation due to various reasons.:
- per queue lock
- Some broker also limiting same part of the message handling to single CPU
thread/queue
- Multiple broker instances needs to synchronise to
Public bug reported:
Problem.: Neutron agents does a lot of periodic task which leads an rpc call +
database transaction, which does not even provide a new information, because
nothing changed.
This behaviour in scale can be called as `DDOS attack`, generally this kind of
architecture is bad
Public bug reported:
(Loop1)
https://github.com/openstack/nova/blob/af2d6c9576b1ac5f3b3768870bb15d9b5cf1610b/nova/scheduler/driver.py#L55
(Loop2)
https://github.com/openstack/nova/blob/af2d6c9576b1ac5f3b3768870bb15d9b5cf1610b/nova/servicegroup/drivers/zk.py#L177
Iterating the hosts through
Public bug reported:
The AMQP broker preserves the exchanges, they are replaced to all broker even
in non HA mode.
A transient exchange can disappear ONLY when the user explicitly requests it's
deletion or when the full rabbit cluster dies.
More efficient to declare exchanges only when it is
Adding cloud-init as affacted project, because it also behavaes in this
way.
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
I consider it as keystone bug.
Keystone should handle this like the default domain.
https://github.com/openstack/keystone/blob/master/keystone/common/sql/migrate_repo/versions/034_havana.py#L282
.
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
The `iscsi_targets` and `volumes` table was used with nova-volumes,
which is deprecated and removed, but the related tables are still created.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
$ nova-manage db archive_deleted_rows 1
command fails with integrity error.
No-one wants to preserve those records in shadow table,
Instead of fixing the archiving issue the tables should be removed.
Later an archive to /dev/null function should be added to the nova
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: ceilometer
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
https://github.com/openstack/nova/blob/5b77c108f14f2bcd42fecfcd060331e57a2e07dd/nova/compute/resource_tracker.py#L554
is always true, since the nova.pci.stats.PciDeviceStats is different
object even if it has an equivalent content.
Please compare the resources properly and
Public bug reported:
update_available_resource (nova/compute/manager.py) can be considered
as expensive at scale, its frequency should be configurable.
Please add a config option for the update_available_resource frequency.
** Affects: nova
Importance: Undecided
Status: New
*** This bug is a duplicate of bug 1382064 ***
https://bugs.launchpad.net/bugs/1382064
** This bug has been marked a duplicate of bug 1382064
Failure to allocate tunnel id when creating networks concurrently
--
You received this bug notification because you are a member of Yahoo!
** Project changed: tempest = nova
--
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/1447945
Title:
check-tempest-dsvm-postgres-full fails with mismatch_error
Status in
Public bug reported:
keystone token responses contains both the InternalURL and adminURL for
non admin user (demo).
This information should not be exposed to a non-admin user.
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because
Public bug reported:
The nova instances table contains internal_id field, Looks like it is
always NULL and never referenced.
The ec2 API uses a variable with same name for snapshots and volumes,
but not for instance id.
For the ec2 id - uuid mapping now a separated table is responsible:
1 - 100 of 124 matches
Mail list logo
