Public bug reported:
When creating a new entity, most APIs return a response which includes
id to represent a new id. However, only agent API returns agent_id
as a new entity. This behavior seems inconsistent from the viewpoint
of whole Nova API.
** Affects: nova
Importance: Undecided
Public bug reported:
Guys,
I just created my first Instance using IceHouse, Neutron with ML2 /
Flat, with Ubuntu 14.04, it got connectivity from my provider network,
it can ping the Internet but, I'm seeing the following error at the
compute node:
http://paste.openstack.org/show/75523/
Best,
Public bug reported:
When there is an iptables failure, it's difficult to troubleshoot
because the exception references a line number from a piped in set of
rules that the user can't see. (e.g.
http://paste.openstack.org/show/75523/)
The rules should be dumped in this case so the user and
Public bug reported:
2014-04-11 04:13:48.201 ERROR oslo.messaging.rpc.dispatcher
[req-801875af-3ef5-486b-8d5d-0794e785301c ServersAdminTestJSON-2137680125
ServersAdminTestJSON-546442934] Exception during message handling:
2014-04-11 04:13:48.201 13779 TRACE oslo.messaging.rpc.dispatcher
Public bug reported:
OS: Ubuntu 12.04
Kernel: 3.8.0-37-generic
libvirt: 0.9.8-2ubuntu17.18
2014-04-11 16:35:03.980 12081 AUDIT nova.service [-] Starting compute node
(version 2014.2)
2014-04-11 16:35:04.004 12081 DEBUG nova.virt.libvirt.driver [-] Connecting to
libvirt: qemu:///system
Public bug reported:
create vxlan successfully with invalid vxlan id for ml2:
curl -i http://127.0.0.1:9696/v2.0/networks -H X-Auth-Token:$token_id -H
Content-Type: application/json -X POST -d '{network: {name: vxlan_test,
admin_state_up: true, tenant_id: $tenant_id, provider:network_type:
Public bug reported:
While creating a new container using Horizon dashboard, In Horizon error logs
we get ClientException: Container HEAD failed.
With Resp status: 404.
Even if the container gets created without an issue.
Steps to reproduce:
#1: Log in to Horizon dashboard
#2: Click on Project
It seems that the exception has been raised deliberately. The exception
is for HEAD request which is done to check whether the container with
given name exists prior to its creation.
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a
Public bug reported:
Currently used pattern
https://review.openstack.org/#/c/63094/15/openstack/common/log.py (lines
471-479) will fail for Python 2.6.x.
In order to fix the broken Python 2.6.x compatibility, old style explicit
superclass method calls should be used instead.
(an example of
Addressed by: https://review.openstack.org/#/c/86875/
** Also affects: oslo
Importance: Undecided
Status: New
** Changed in: nova
Assignee: Bogdan Dobrelya (bogdando) = (unassigned)
** Changed in: nova
Status: In Progress = Confirmed
** Also affects: ceilometer
Public bug reported:
default floating ip pool is configured in default_floating_pool=
(default is named: nova )
user can't see the dafault under nova floating-ip-pool-list
user can't change/edit the default pool using CLI
1. create few floating ip pools with names
2. try to check which one
Public bug reported:
Problem:
---
If a host is part of an availability zone (AZ) it should not be part of the
default availability zone.
Otherwise scheduling hosts by default will be spread across AZs if this is not
specified in
the CLI.
Steps to reproduce:
--
** Description changed:
- In order to more effectively manage the unlinked and open (lsof +L1) log
- files descriptors w/o restarting the services, SIGHUP signal should be
- accepted by every Openstack service.
+ 1)In order to more effectively manage the unlinked and open (lsof +L1)
+ log files
I marked this an invalid as it wasn't a current bug in Keystone. The
problem was a Debian specific patch that looks to be a fix for an issue
we may have had in the past.
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Attached patch showing that changes only affect the Cloud Sigma DS.
** Summary changed:
- CloudSigma Datasource doesn't handle vendor-data correctly
+ [FFe] CloudSigma Datasource doesn't handle vendor-data correctly
** Changed in: cloud-init
Assignee: (unassigned) = Ben Howard (utlemming)
Public bug reported:
If an instance's vifs cannot be deleted (because, for example, they were
never plugged in the first place), then compute manager will fail trying
to delete the instance:
2014-04-11 09:25:27.754 TRACE oslo.messaging.rpc.dispatcher File
Public bug reported:
Using Nova trunk (Juno). I'm seeing the following nova-api.log errors
when unauthenticated /versions controller POST requests are made with a
request body:
-
Apr 11 07:04:06 overcloud-controller0-n2g3h54d6w6u nova-api[27022]: 2014-04-11
07:04:06.235 27044 ERROR
** Changed in: cloud-archive
Status: New = 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/1304107
Title:
Libvirt error launching instance - Device
Public bug reported:
After I installed some updates from Software Updater for a while, I found my
account cannot use sudo command anymore. Ubuntu told me that I'm not a sudoer.
Reboot my laptop and enter recover mode, I found 2 lines of my /etc/sudoers
file was changed from
root ALL=(ALL)
** Changed in: keystone
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1236511
Title:
Keystone Trusts API sends non descriptive error message
** Also affects: nova/icehouse
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/1306718
Title:
Instances become undelete-able
Public bug reported:
openstack_dashboard.dashboards.project.databases.workflows.create_instance in
populate_flavor_choices
TypeError: 'NoneType' object is not iterable
If there's an exception in
openstack_dashboard/dashboards/project/databases/workflows/create_instance.py
Public bug reported:
In setting the nova_api_insecure flag to True in neutron.conf, I've
found that neutron/notifiers/nova.py does not honor this flag. In fact,
it does not even pass any insecure parm at all on the invocation of
Client().
Public bug reported:
V3 list_user filter by email throws excpetion. There is no such
attribute email.
keystone.common.wsgi): 2014-04-11 23:09:00,422 ERROR type object 'User' has no
attribute 'email'
Traceback (most recent call last):
File
Reviewed: https://review.openstack.org/86937
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=abf2dd8ee8ea116205d661e57f8dda6627e2f5c1
Submitter: Jenkins
Branch:milestone-proposed
commit abf2dd8ee8ea116205d661e57f8dda6627e2f5c1
Author: Erno Kuvaja jo...@hp.com
Date:
Reviewed: https://review.openstack.org/86873
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=a18cbfd029a3e8837aa350b17b42481ff0a423e6
Submitter: Jenkins
Branch:milestone-proposed
commit a18cbfd029a3e8837aa350b17b42481ff0a423e6
Author: Zhi Yan Liu zhiy...@cn.ibm.com
Public bug reported:
Lots of failures here:
http://logs.openstack.org/47/69047/17/check/check-grenade-
dsvm/f153c4a/console.html
message:NoMoreFixedIps_Remote: Zero fixed ips available. AND
tags:screen-n-net.txt
** Also affects: django-openstack-auth
Importance: Undecided
Status: New
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: New = In Progress
** Changed in: django-openstack-auth
Status: New = In Progress
** Changed in:
** Changed in: nova
Assignee: wangpan (hzwangpan) = (unassigned)
** Changed in: nova
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
29 matches
Mail list logo
