Public bug reported:
# nova-manage cell_v2
An error has occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/oslo_config/cfg.py", line 3179,
in __getattr__
return getattr(self._conf._namespace, name)
AttributeError: '_Namespace' object has no attribute
Public bug reported:
My today master version of keystone log is full with:
2019-07-15 10:47:25.316828 As of the Stein release, the domain API now
understands how to handle
2019-07-15 10:47:25.316831 system-scoped tokens in addition to project-scoped
tokens, making the API more
2019-07-15 10:47:
Public bug reported:
Mar 22 09:09:30 controller-02 glance-api[23536]:
/opt/stack/glance/glance/location.py:189: DeprecationWarning: Using or
importing the ABCs from 'collections' instead of from 'collections.abc' is
deprecated, and>
Mar 22 09:09:30 controller-02 glance-api[23536]: class
Stor
Public bug reported:
'nova-manage cell_v2 discover_hosts' usage should not be needed,
the compute nodes at start up time could ask for registration
and not repeat it during the n-cpu process lifetime.
In case of you have 30k compute node and restarting
them every two week in average, it would ge
Public bug reported:
Neutron ovs agent some cases have this in his log:
The rpc_response_max_timeout supposed to have a default value:
I wonder is the issue related to https://bugs.launchpad.net/cinder/+bug/1796759,
where the oslo.messaging change affected 2 other component.
Feb 18 14:33:12 f2
Nova expected to wait for all connected port to become active on instance
creation before reporting the instance active.
No additional user/tempest wait is required, no random port status flipping is
allowed.
** Also affects: nova
Importance: Undecided
Status: New
--
You received th
Adding nova, nova also using brctl for example in the
NeutronLinuxBridgeInterfaceDriver ,
yes, pyroute2 might be an alternative to the ip commands as well, however the
bridge create/enslave is not most documented part.
** Also affects: nova
Importance: Undecided
Status: New
--
You re
Public bug reported:
bridge-utils (brctl) is obsolete, no modern software should depend on it.
Used in: neutron/agent/linux/bridge_lib.py
http://man7.org/linux/man-pages/man8/brctl.8.html
Please use `ip` for basic bridge operations,
than we can drop one obsolete dependency..
** Affects: neutron
Searching for keywords in the neutron change log:
https://bugs.launchpad.net/neutron/+bug/1757089
** 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:
** 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/1690374
Title:
remotefs fails to make Nova-assisted snap
Public bug reported:
Nova returns with 5xx response instead of 4xx in case of user error.
In this case it is clearly user issue, the user can know the 10.0.0.3 ip
address already allocated from the subnet and it cannot be allocated
twice.
nuva must return with 409/Conflict status code and state
Public bug reported:
The issue is very similar to the one already discussed at
https://bugs.launchpad.net/keystone/+bug/1334368 ,
http://lists.openstack.org/pipermail/openstack-dev/2014-July/039140.html .
# curl -v -X HEAD
http://172.17.1.18:5000/v3/roles/7acb026c29a24fb2a1d92a4e5291de24/impl
Public bug reported:
The 'Default' domain was created with 'default' id, but for all other
domain I got some random string as an id.
The domain names are unique, and compared in a case intensive way,
therefore lowercase names can be ids.
** Affects: keystone
Importance: Undecided
S
Public bug reported:
I have a newton setup with 3 api(controller) node.
TenantUsagesTestJSON.test_list_usage_all_tenants failed once , the
failure looks similar to one described in the already fixed in
https://bugs.launchpad.net/nova/+bug/1487570 , but it is different api
call so it can have simi
Public bug reported:
The following check https://review.openstack.org/#/c/326927/6/neutron/db/api.py
, does not works when I am using:
MySQL-python (1.2.5)
oslo.db (4.13.3)
SQLAlchemy (1.1.0)
2016-10-06 04:39:20.674 16262 ERROR neutron.api.v2.resource OperationalError:
(_mysql_exceptions.Operat
Public bug reported:
On newton it looks like:
$ nova image-list
WARNING: Command image-list is deprecated and will be removed after Nova 15.0.0
is released. Use python-glanceclient or openstackclient instead.
ERROR (VersionNotFoundForAPIMethod): API version 'API Version Major: 2, Minor:
37' is n
Public bug reported:
1. iniset keystone.conf DEFAULT admin_token deprecated
2. reload keystone (systemctl restart httpd)
3. curl -g -i -X GET http://192.168.9.98/identity_v2_admin/v2.0/users -H
"User-Agent: python-keystoneclient" -H "Accept: application/json" -H
"X-Auth-Token: deprecated"
I kn
Public bug reported:
When you download this image with curl, you get a qcow2 file, NOT a gz file.
https://fedorapeople.org/groups/magnum/fedora-21-atomic-5.qcow2
When you use
glance --os-image-api-version=1 image-create --copy-from
https://fedorapeople.org/groups/magnum/fedora-21-atomic-5.qcow2
Public bug reported:
curl -H 'Host: 127.0.0.1:35357' -H 'Accept-Encoding: gzip, deflate' -H
'X-Subject-Token: ' -H 'Accept: application/json' -H 'X
-Auth-Token: ' -H 'Connection: keep-alive' -H 'User-Agent:
python-keystoneclient' http://localhost:35357/v3/auth/tokens
Keystone on behalf of the sa
Public bug reported:
The image_cache_manager periodic task running on behalf of the n-cpu.
image_cache_manager queries all instances which uses the same file-system as
him.
(The message may contain all compute nodes in the region, if they are using the
same shared pNFS)
https://github.com/ope
Public bug reported:
https://github.com/openstack/neutron-
lbaas/blob/b868d6d3ef0066a1ac4318d7e91b4d7a076a2e61/neutron_lbaas/drivers/haproxy/namespace_driver.py#L327
arping can take relative long time (>2 sec), while the global lock is
held.
The gratuitous arping should not block other threads.
** 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 O
*** 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!
Engineer
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 you
Public bug reported:
Just the not deleted members needs to be selected, an instance group can
gather many-many deleted instances during on his lifetime.
The selecting query contains a condition for omitting the deleted
records:
SELECT instance_groups.created_at AS instance_groups_created_at,
ins
Public bug reported:
Now the table is declared in this way:
show create table aggregate_hosts;
CREATE TABLE `aggregate_hosts` (
`created_at` datetime DEFAULT NULL,
`updated_at` datetime DEFAULT NULL,
`deleted_at` datetime DEFAULT NULL,
`id` int(11) NOT NULL AUTO_INCREMENT,
`host` varch
Public bug reported:
Now only two policy available, but only one can be used with a server
group.
$ nova server-group-create name "affinity" "anti-affinity"
ERROR (BadRequest): Invalid input received: Conflicting policies configured!
(HTTP 400) (Request-ID: req-1af553f8-5fd6-4227-870b-be963aad2
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:
instanc
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 a
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 queue
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 re
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.
https://bugs.launchpa
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 the
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 s
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
--
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
manage.
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
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 not
** 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).
https://bugs.launc
** 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 not
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 restrict
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 ml2_vxlan_allo
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-
full/95aea86/logs/screen-q-svc.txt
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 e
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 /opt/stack/new/devstack/acc
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-
full/4ad9772/logs/screen-q-s
Public bug reported:
I see similar message in non dvr setups as mentioned in #1371696.
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiQ2Fubm90IGFkZCBvciB1cGRhdGUgYSBjaGlsZCByb3dcXDogYSBmb3JlaWduIGtleSBjb25zdHJhaW50IGZhaWxzXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCI
ack
2014-10-24 10:59:53.921 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
--
Y
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 f
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
--
** 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
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 single
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 dow
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 qu
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 time,
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
** 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:
The get_active_networks_info rpc call causes high number of sql query.
For example the following query
SELECT subnetroutes.destination AS subnetroutes_destination,
subnetroutes.nexthop AS subnetroutes_nexthop, subnetroutes.subnet_id AS
subnetroutes_subnet_id
FROM subnetrou
*** This bug is a duplicate of bug 1194579 ***
https://bugs.launchpad.net/bugs/1194579
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiaXMgaW4gQ1JFQVRFX0ZBSUxFRCBzdGF0dXMgZHVlIHRvIFJlc291cmNlIENSRUFURSBmYWlsZWQ6IEJhZFJlcXVlc3Q6IFNlY3VyaXR5IGdyb3VwIGRlZmF1bHQgYWxyZWFkeSBleGlzdHMgZm9y
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 detai
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..)
mo
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 us
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 in
Public bug reported:
Logstash query for full console outputs which does not contains 'info:
initramfs loading root from /dev/vda' , but contains the previous boot
message.
These issues look like ssh connectivity issue, but the instance is not
booted and it happens regardless to the network type.
Public bug reported:
n-cpu times out while waiting for neutron.
Logstash
http://logstash.openstack.org/#eyJzZWFyY2giOiIgbWVzc2FnZTogXCJUaW1lb3V0IHdhaXRpbmcgZm9yIHZpZiBwbHVnZ2luZyBjYWxsYmFjayBmb3IgaW5zdGFuY2VcIiBBTkQgdGFnczpcInNjcmVlbi1uLWNwdS50eHRcIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGl
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"
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkZpeGVkSXBMaW1pdE
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 tes
Public bug reported:
The following tempest test fails when I select 'qpid' instead of
'rabbit' ENABLED_SERVICES in the devstack local.conf:
tempest.api.telemetry.test_telemetry_notification_api.TelemetryNotificationAPITestXML.test_check_glance_v1_notifications[gate,image,smoke]
tempest.api.teleme
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
nova.api.openstack.compute.contrib
Public bug reported:
message: "KeyError: 'image_id'" AND tags:"screen-n-api.txt"
The issue first appeared at 2014-07-17T16:36:43.000.
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIktleUVycm9yOiAnaW1hZ2VfaWQnXCIgQU5EIHRhZ3M6XCJzY3JlZW4tbi1hcGkudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjA
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"
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIkV4Y2VwdGlv
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"
http://logstash.openstack.org/#eyJzZ
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
--
Yo
** 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
Public bug reported:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiU3RkZXJyOiAnRGV2aWNlIFwiIEFORCBtZXNzYWdlOiBcImRvZXMgbm90IGV4aXN0XCIiLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsIm9mZnNldCI6MCwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwibW9kZSI6IiIsImFuYWx5emVfZm
Public bug reported:
http://logstash.openstack.org/#eyJmaWVsZHMiOltdLCJzZWFyY2giOiJtZXNzYWdlOlwiQXR0cmlidXRlRXJyb3JcXDogJ01ldGVyaW5nQWdlbnRXaXRoU3RhdGVSZXBvcnQnIFwiIiwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJvZmZzZXQiOjAsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sIm1vZGUiOiIiLCJhbmFseXplX2
** 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 wor
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
+--+
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
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.
https://bugs.launchpa
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 bu
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
Importa
** 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 st
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:
http://logs.openstack.org/32/97532/3/check/check-tempest-dsvm-full/ae1f95a/logs/screen-n-cpu.tx
message:"ServiceCatalogException" AND tags:"horizon_error.txt" 11 hit in
7 days.
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiU2VydmljZUNhdGFsb2dFeGNlcHRpb25cIiBBTkQgdGFnczpcImhvcml6b25fZXJyb3IudHh0XCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW
Public bug reported:
http://logs.openstack.org/90/96090/2/check/check-tempest-dsvm-postgres-full/3580e69/console.html
failed with:
2014-05-30 06:30:40.384 | Log File Has Errors: n-cond
2014-05-30 06:30:40.384 | *** Not Whitelisted *** 2014-05-30 05:57:53.811 ERROR
oslo.messaging.rpc.dispatcher [r
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 automatical
** No longer affects: openstack-ci
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1322440
Title:
NoSuchOptError: no such option: state_path
Status in OpenStack Neutron (virtual network
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
neutron.tests
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 affe
The check-grenade-dsvm-icehouse is upgrading from icehouse -> icehouse on
tempest changes,
instead of havana -> icehouse.
The check-grenade-dsvm-icehouse supposed to prevent this kind of
issues.
Adding openstack-infra.
** Also affects: openstack-ci
Importance: Undecided
Status: New
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: "`keysto
** 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 in
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
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] http://logs.openstack.org/29/93029/1/check/check-grenade-dsvm/3201
Public bug reported:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcIlVuaWNvZGVEZWNvZGVFcnJvclwiIiwiZmllbGRzIjpbXSwib2Zmc2V0IjowLCJ0aW1lZnJhbWUiOiI2MDQ4MDAiLCJncmFwaG1vZGUiOiJjb3VudCIsInRpbWUiOnsidXNlcl9pbnRlcnZhbCI6MH0sInN0YW1wIjoxNDAwNDI3ODM3NzE0LCJtb2RlIjoiIiwiYW5hbHl6ZV9maWVsZCI6Ii
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 pr
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 21:44:09.
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:
g
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: openstack-ci
1 - 100 of 138 matches
Mail list logo
