Public bug reported:
In
http://git.openstack.org/cgit/openstack/horizon/tree/openstack_dashboard/dashboards/admin/floating_ips/views.py#n119
,
Line 119, "msg = _('Unknow resource type for detail API.')"
: "Unknow" is typo. It should be changed to "Unknown".
I am not sure whether the source code
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1588355
Ti
Public bug reported:
The current api-ref for create server shows the
'block_device_mapping_v2' request parameter as:
"block_device_mapping_v2": { "boot_index": "0", "uuid": "ac408821-c95a-
448f-9292-73986c790911", "source_type": "image", "volume_size": "25",
"destination_type": "volume", "delete_
Reviewed: https://review.openstack.org/364622
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e2fdeefd37314d3e6c5910fcc7070de34561ec44
Submitter: Jenkins
Branch:master
commit e2fdeefd37314d3e6c5910fcc7070de34561ec44
Author: Armando Migliaccio
Date: Thu Sep 1 19:33:3
Reviewed: https://review.openstack.org/365014
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=9127f074f5a5f99eae09aba45a713041a55d91ae
Submitter: Jenkins
Branch:master
commit 9127f074f5a5f99eae09aba45a713041a55d91ae
Author: Jakub Libosvar
Date: Fri Sep 2 16:39:17 20
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1570489
Title:
Create Volume Type Extra Spec modal
** Also affects: neutron
Importance: Undecided
Status: New
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1617862
Title:
NoFilterMatched when kill m
I think the nova part of this bug was fixed with
https://review.openstack.org/364454 - if there is more to do please be
specific.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Op
What is this?
** Changed in: nova
Status: New => 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/1618707
Title:
add comment
Status in OpenStack Compute (
I'm not sure this is a bug, it just means that the xenapi driver gets
the same capabilities as are defined in the base ComputeDriver class.
Once it diverges from the base class defaults then it would need it's
own capabilities dict.
** Tags added: xenserver
** Changed in: nova
Status: New
This isn't a nova bug, it's either a problem in your setup or a bug in
nova-docker, which is basically a defunct project, so your bug will
probably not get addressed unless you attempt to fix it yourself, but I
believe the nova-docker repo is being abandoned in newton.
** Also affects: nova-docker
This is an invalid setup, you have ec2 in the enabled_apis config
option, which isn't supported in mitaka. If the docs say to do that,
then this is a docs bug and should be redirected.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a membe
Have you tried this trick
https://github.com/openstack/glance/blob/11cfe49b8f88f68d83028b5920891bb16792da72/glance/cmd/__init__.py#L23-L49
?
I think that'd work for you and we may have to update the documentation
using this bug as an example to update the docs!
** Changed in: glance
Status
@Lyle: are you using the schemas to validate your request?
I see how a 409 is more convenient.
I'm on the fence for this -- my opinion is that 403 is the right call
from glance's perspective as you are trying to update the reserved
attribute and have some knowledge of the image (using the id).
T
I doubt if we need doc change for this as the commit itself made the doc
change.
** Changed in: glance
Status: New => Opinion
** Changed in: glance
Importance: Undecided => Wishlist
** Changed in: glance
Importance: Wishlist => Low
--
You received this bug notification because you
Public bug reported:
The correct format is described at http://specs.openstack.org/openstack
/nova-specs/specs/newton/approved/generic-resource-pools.html#get-
resource-providers-uuid-inventories
In that format the resource provider generation is its own top level
key.
In the code the generation
I'm adding TripleO because we need to automate the process of upgrade regarding:
http://docs.openstack.org/releasenotes/keystone/unreleased.html#upgrade-notes
"Keystone now supports encrypted credentials at rest. In order to
upgrade successfully to Newton, deployers must encrypt all credentials
cu
Public bug reported:
A recent change to encrypt credetials broke RDO/Tripleo deployments:
2016-09-02 17:16:55.074 17619 ERROR keystone.common.fernet_utils
[req-31d60075-7e0e-401e-a93f-58297cd5439b f2caffbaf10d4e3da294c6366fe19a36
fd71b607cfa84539bf0440915ea2d94b - default default] Either [fern
Reported in a downstream distribution that should have synced from this
code as still a bug. please reconfirm.
** Changed in: keystone
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenS
Reviewed: https://review.openstack.org/359675
Committed:
https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=c43c8e4b7d4ea19267f6434bb45b3f0c0326c284
Submitter: Jenkins
Branch:master
commit c43c8e4b7d4ea19267f6434bb45b3f0c0326c284
Author: ubuntu
Date: Wed Aug 24 04:05:4
Public bug reported:
If a compute node has been reconfigured such that its allocations are
above its available capacity, the resource tracker still needs to be
able to report existing allocations without failure so that it doesn't
get in a stuck state.
To that end, we will make it so that when se
Public bug reported:
If a compute node is reconfigured in a way that makes its inventory
change, those changes must be reflected in the placement service, even
if they violate the existing allocations, otherwise the node is left in
a difficult state.
This is safe because with this new inventory t
Reviewed: https://review.openstack.org/364634
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=c7369483557e23782d2ec293d548bc96cd729934
Submitter: Jenkins
Branch:master
commit c7369483557e23782d2ec293d548bc96cd729934
Author: Kevin Benton
Date: Thu Sep 1 20:07:09 2016
Public bug reported:
Since this commit: https://review.openstack.org/#/c/293305/
Puppet OpenStack CI is failing to run db upgrades:
2016-09-02 13:41:05.973470 | Notice:
/Stage[main]/Neutron::Db::Sync/Exec[neutron-db-sync]/returns: INFO
[alembic.runtime.migration] Running upgrade 3b935b28e7a0,
Reviewed: https://review.openstack.org/364278
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b1ec8d523d4c45616dd71016f7e218b4b732c2ee
Submitter: Jenkins
Branch:master
commit b1ec8d523d4c45616dd71016f7e218b4b732c2ee
Author: John Schwarz
Date: Fri Aug 19 15:17:21 201
Public bug reported:
The request logging in the placement api will always log a status of
200, even when that's not the case because it it getting status from the
wrong place. A possible fix is to raise the logging up a level to
middleware where it can access the response status more directly (aft
Reviewed: https://review.openstack.org/342016
Committed:
https://git.openstack.org/cgit/openstack/tempest/commit/?id=79f5efd4687224519cd22b98b4f37b2832b1aae5
Submitter: Jenkins
Branch:master
commit 79f5efd4687224519cd22b98b4f37b2832b1aae5
Author: Ji-Wei
Date: Thu Jul 14 16:58:43 2016 +080
marked as fix-released.
as bug states, it is fixed in xenial.
wily is not supported any more, so its wont-fix there.
** No longer affects: maas
** Changed in: cloud-init
Status: New => Fix Released
** Changed in: cloud-init
Importance: Undecided => Medium
--
You received this bug n
Hi,
I've set this to 'wishlist' as I'm pretty sure it is fixed in 16.04,
with systemd units. The issue is probably still present in upstart.
I'm open to patches for this, and if it affects 16.04, please take out
of fix-released and comment.
Thanks for filing the bug.
** Also affects: cloud-ini
** Also affects: cloud-archive/icehouse
Importance: Undecided
Status: New
** Changed in: cloud-archive
Status: Confirmed => Invalid
** Changed in: cloud-archive/icehouse
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Hi,
Description
===
I have installed Openstack Mitaka release manually and getting following
error. Please find nova-api error log attached.
root@con:/home/con# neutron net-list
+--+-+--
Public bug reported:
When passing a dictionary inside of external_ids and there is a list
within the dictionary, Python OVS library raises ovsdb error: expected
string, got while vsctl interface converts the value to
string and stores it correctly into database.
** Affects: neutron
Importan
Public bug reported:
In Mitaka, there is no pagination for Identity-->Projects
and Number of items per page settings does not work in this page .
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineer
Public bug reported:
snapshot_volume_backed() in compute.API does not set a task_state during
execution. However, in essence it does:
if vm_state == ACTIVE:
quiesce()
snapshot()
if vm_state == ACTIVE:
unquiesce()
There is no exclusion here, though, which means a user could do:
quiesce()
Public bug reported:
During cold migration, vhd config drive images are not copied over, on
the wrong assumption that the instance is already configured and does
not need the config drive.
There is an explicit check at the following location:
https://github.com/openstack/nova/blob/8f35bb321d26bd7
You have been subscribed to a public bug:
During cold migration, vhd config drive images are not copied over, on
the wrong assumption that the instance is already configured and does
not need the config drive.
There is an explicit check at the following location:
https://github.com/openstack/nova
** Changed in: nova/mitaka
Status: In Progress => 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/1545675
Title:
Resizing a pinned VM results in incon
** Changed in: neutron
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1609217
Title:
DVR: dvr router should not exist in not-binded network node
St
With the current api design, we have to do multiple request to get the
extra-spec of all the flavors.
extra-spec information is not returned in '/v2.1/{tenant_id}/flavors'
as well as in '/v2.1/{tenant_id}/flavors/details' api(s) and so, to
get extra-spec for every single flavor, we have to cal
Python-neutronclient and openstackclient also do not support bulk
creation of security groups.
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Assignee: (unassigned) => Reedip (reedip-banerjee)
** Also affects: python-op
40 matches
Mail list logo