Public bug reported:
Postgres as Database + latest stable Kilo; When doing live migrate with
attached volume (rally test
boot_server_attach_created_volume_and_live_migrate):
8<
ERROR oslo_db.sqlalchemy.exc_filters [req-76f003ad-8b12-4e85-902a-a52581fd5611
Public bug reported:
neutronclient logs sensitive info in headers when logging http requests
in debug mode.
/usr/lib/python2.7/site-
packages/neutronclient/common/utils.py:http_log_req()
neutronclient should hash sensitive info in headers such as 'X-Auth-Token' and
'X-Subject-Token'.
For
Sean, http://logs.openstack.org/85/193485/13/check/gate-tempest-dsvm-
neutron-
linuxbridge/079f108/logs/screen-q-agt.txt.gz#_2015-11-12_08_45_59_502 is
debug level, logstash.o.o only indexes INFO+ level logs.
** Also affects: oslo.log
Importance: Undecided
Status: New
--
You received
Public bug reported:
nova/crypto.py:generate_winrm_x509_cert() generates certs with default
SHA-1 digest.
The call to 'openssl req' does not specify -digest option nor
certificate config file sets digest, so certificates are generated with
SHA-1 digest. SHA-1 is not considered to be a secure
Public bug reported:
After preparing my Horizon environment as described in
http://docs.openstack.org/developer/horizon/contributing.html#running-
the-pseudo-translation-tool I observe several non-translatable quotas:
Per Volume Gigabytes
Volumes Lvmdriver-1
Gigabytes Lvmdriver-1
Snapshots
Public bug reported:
After preparing my Horizon environment as described in
http://docs.openstack.org/developer/horizon/contributing.html#running-
the-pseudo-translation-tool I observe several non-translatable quotas:
Per Volume Gigabytes
Volumes Lvmdriver-1
Gigabytes Lvmdriver-1
Snapshots
Public bug reported:
If I configure storage quotas with:
user_storage_quota = 6
And I enable the v2 registry:
data_api = glance.db.registry.api
Then a v1 image create:
$ glance --os-image-api-version 1 image-create --name x3 --disk-format raw
--container-format bare --file /etc/fstab
413
Public bug reported:
I'm trying to boot glance images which have the hypervisor_type property
set on them to 'lxd' to target specific hypervisors within a mixed
hypervisor cloud; instance boot fails with:
{"message": "Hypervisor virtualization type 'lxd' is not recognised",
"code": 400,
Public bug reported:
The help text (both tooltips, and descriptive text on the right hand
side) for Firewalls forms (Create, Edit etc.) is very sparse, and we
should update it with more information from the VPN docs or API docs.
This is especially apparent on Policies and Rules.
** Affects:
Public bug reported:
The help text (both tooltips, and descriptive text on the right hand
side) for VPN forms (Create, Edit etc.) is very sparse, and we should
update it with more information from the VPN docs or API docs.
** Affects: horizon
Importance: Wishlist
Status: New
**
Public bug reported:
When running neutron api test with:
tox -eapi
the advertised TEMPEST_CONFIG_DIR env var doesn't work as it's said in
https://github.com/openstack/neutron/blob/master/tox.ini#L27-L28 .
Instead, it always tries to fetch the file from
/etc/tempest/tempest.conf
i.e.
Public bug reported:
The "Update Metadata" actions for images, flavors, etc. currently
fetches the metadata definitions from glance to display in the metadata
modal. The metadata definitions API was introduced with the v2 API and
if this is not being used the user will get an error.
"Error:
Public bug reported:
The latest nova policy file includes many new policies including some
related to instance metadata. The version currently in horizon does not
include these, and it should be updated.
** Affects: horizon
Importance: Undecided
Assignee: Justin Pomeroy (jpomero)
Had a quick look at 2 other patchsets - Haven't found this message in
there. So probably related to my patchset?
I set to invalid - try to investigate and if still exists, open this bug
again. Sorry for the inconvenience!
** Changed in: neutron
Status: Triaged => Invalid
** Changed in:
There's an approved blueprint for fibre channel support on Hyper-V:
https://blueprints.launchpad.net/nova/+spec/hyperv-fibre-channel
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
This has been published as OSSN-0059:
https://wiki.openstack.org/wiki/OSSN/OSSN-0059
** Changed in: ossn
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This has been published as OSSN-0049:
https://wiki.openstack.org/wiki/OSSN/OSSN-0049
** Changed in: ossn
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).
** Tags added: kilo-backport-potential liberty-backport-potential
** Tags added: juno-backport-potential
** Also affects: nova/mitaka
Importance: High
Assignee: Matt Riedemann (mriedem)
Status: In Progress
** Also affects: nova/juno
Importance: Undecided
Status: New
**
Public bug reported:
Using git revision: e6100f593413de77cc825cb9aeb5b86a739874e9
When I run nova-api without an arguments I get an exception. I used the
api-paste.ini that was in the source tree.
2015-11-16 16:21:28.376 47780 DEBUG nova.wsgi [-] Loading app osapi_compute
from
Public bug reported:
Sometimes, operator need to disable some panels to fit their cloud.
However, after disabled a panel, the unit test of Horizon will still try
to resolve the URL. It doesn't make sense.
** Affects: horizon
Importance: Low
Status: Confirmed
--
You received this
Public bug reported:
http://developer.openstack.org/api-ref-
networking-v2-ext.html#showLoadBalancerv2 displays the output of a show
loadbalancer call. One of the keys shown is 'status'.
Based on the code (https://github.com/openstack/neutron-
Public bug reported:
Seen here:
http://logs.openstack.org/20/243320/4/gate/gate-nova-
python27/37b1b32/console.html
Just started on 11/16 with the o.vo 0.13.0 release.
Lots of this:
2015-11-16 21:00:40.347 | result = getattr(cls, objmethod)(context,
*args, **kwargs)
2015-11-16
Public bug reported:
Remotefs drivers have to mount a filesystem while connecting a new
volume and unmount it eventually. They do it with code like:
connect_volume:
if not is_mounted():
do_mount()
disconnect_volume:
try:
umount()
except:
if error is not 'fs is
** Changed in: oslo.config
Status: Fix Committed => Fix Released
** Changed in: oslo.config
Milestone: None => 2.7.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
http://developer.openstack.org/api-ref-
networking-v2-ext.html#createPoolv2 claims that the create pool API
includes this parameter
protocol_port. The port on which the front end listens. Must be an
integer from 1 to 65535.
It doesn't (johnsom even checked in the code!)
**
** Also affects: python-magnumclient
Importance: Undecided
Status: New
** Changed in: python-magnumclient
Assignee: (unassigned) => yuanying (ootsuka)
** Changed in: magnum
Importance: Undecided => Medium
** Changed in: python-magnumclient
Importance: Undecided => Medium
Public bug reported:
There a number of models.py files still in the source due to
https://code.djangoproject.com/ticket/7198, which was closed a very long
time ago.
** Affects: horizon
Importance: Undecided
Assignee: Rob Cresswell (robcresswell)
Status: In Progress
** Changed
[Expired for OpenStack Identity (keystone) because there has been no
activity for 60 days.]
** Changed in: keystone
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
** Changed in: oslo.versionedobjects
Status: New => Invalid
** Tags added: liberty-backport-potential
** Also affects: nova/liberty
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
[Summary]
LB_NFV:KiloV1 ,the maxconn should be created on global section of
HAprxy config file
[Topo]
Openstack version :RDO kilo
OS version :centOS 7.1
[Description and expect result]
the maxconn should be
Public bug reported:
[Summary]
LB_NFV KiloV1 :the default session limit is 2000 rather than unlimit
[Topo]
RDO-Kilo
CentOS 7.1
[Description and expect result]
if we don't config session limit , the expect the session shoule be not
limit
** Also affects: trove
Importance: Undecided
Status: New
** Changed in: trove
Assignee: (unassigned) => yuanying (ootsuka)
** Also affects: python-troveclient
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Data size on storage devices is typically measured in GiB (2^30), and
not GB (10^9).
The Cinder community has addressed this issue by changing all of their CLI and
Horizon panels to use "GiB"
(see https://bugs.launchpad.net/horizon/+bug/1511167)
There are several Nova
Public bug reported:
Python NeutronClient supports Allow, Deny and Reject
options.(https://github.com/openstack/python-neutronclient/blob/master/neutronclient/neutron/v2_0/fw/firewallrule.py#L107)
Horizon has only the Allow and Deny
Public bug reported:
curl -g -i -X GET
http://192.168.122.239:8774/v2.1/d1c5aa58af6c426492c642eb649017be/images/detail?status=ACTIVE
can get correct image list, however, (note status --> stats)
curl -g -i -X GET
Public bug reported:
When we use filter_by() fields for filtering are extracted from the
primary entity of the query, or the last entity that was the target of a
call to Query.join().
If db query contains filters 'project_id' and 'tag' (or 'tag-any') db
error will be raised:
File
Thanks for the info @rushikesh, moved it to Invalid.
** Changed in: neutron
Status: Incomplete => 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/1513788
Title:
Exception
Public bug reported:
It seems that all gate-tempest-dsvm-cells runs against the liberty
branch fail because of
2015-11-16 04:50:15.334 | ==
2015-11-16 04:50:15.334 | Failed 1 tests - output below:
2015-11-16 04:50:15.334 | ==
2015-11-16
Public bug reported:
Post this commit:
https://review.openstack.org/#/c/170780/11/nova/virt/libvirt/driver.py,
the NUMA topology reporting depends on the host architecture.
The current check includes arch.I686, arch.X86_64 only.
This bug is filed to include the ppc64/ppc64le architectures
** 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/1515896
Title:
Update port of admin state to False for neutron floating IP port does
Removing duplicate to perform additional checks
** This bug is no longer a duplicate of bug 1478925
Instances on the same compute node unable to connect to each other's ports
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
The modification needs to be done at the api-ref document.
So moving this issue to the api-site
** Project changed: neutron => openstack-api-site
** Tags removed: lbaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
42 matches
Mail list logo
