Public bug reported:
In some models value of 'nullable' parameter in columns is wrong. The following
models are incorrect:
NULL for PoolLoadbalancerAgentBinding agent_id
NULL for NexusPortBinding switch_ip and instance_id
NULL for LsnPort lsn_id
NULL for NeutronNsxPortMapping nsx_port_id
NULL
Public bug reported:
When using SQLAlchemy 0.9, the docs fail to build. This is preventing Keystone
from moving up to SQLAlchemy 0.9.
There's a commit to update keystone's requirements to SQLAlchemy 0.9
which is failing the docs build: https://review.openstack.org/#/c/82231/
The log there
Public bug reported:
Most modules in openstack_dashboard/openstack/common are out-of-date and need
to be synced with latest oslo.
The following modules are out-of-date.
In addition, many modules are not used in OpenStack Dashboard. If I remember
correctly, they were introduced because of
Public bug reported:
URL /v3/auth/tokens cannot be used when issuing unscoped federated
tokens, as such URL must be configured as protected in the mod_shib
configuration. Thus, a dedicated URL must be able to run federated
authentication. Also, as usually during federated authentication initial
** Changed in: anvil
Status: Fix Committed = Fix Released
** Changed in: anvil/havana
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to anvil.
** Changed in: anvil
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to anvil.
https://bugs.launchpad.net/bugs/1255872
Title:
Write verbose log to a file
Status in ANVIL for forging
Public bug reported:
When a volume is attached to an instance, instance detail page has a
link to volume detail but the link points to volume snapshot and it
leads to Unable to retrieve snapshot detail error.
instance detail template _detail_overview.html needs to be updated to volume
detail:
Public bug reported:
Related to bug 1296356, It is confusing that
horizon:project:volumes:detail refers to a volume snapshot. It is
better volume snapshot codes are placed in snapshots directory.
** Affects: horizon
Importance: Low
Status: New
--
You received this bug
Public bug reported:
Related to bug 1296356, It is confusing that
horizon:project:volumes:detail refers to a volume snapshot. It is
better volume snapshot codes are placed in snapshots directory.
** Affects: horizon
Importance: Low
Assignee: Akihiro Motoki (amotoki)
Status: In
** Changed in: keystone
Milestone: None = icehouse-rc1
** Also affects: openstack-api-site
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Public bug reported:
There are a couple of cases in the compute manager where we don't pass
reservations to _delete_instance(). For example, one of them is
cleaning up when we see a delete that is stuck in DELETING.
The only place we ever update quotas as part of delete should be when
the
Public bug reported:
Regarding the discussion in bug 1242338, there is a suggestion that it is
better to check if VIP has members is being deleted.
From UX perspective, it is better to be warned when a user try to delete a VIP
with members.
** Affects: horizon
Importance: Wishlist
Horizon just fetches a volume status from Cinder. It should be addressed
in Cinder side.
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: horizon
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
The point related to UX perspective (is it reasonable to allow deleting
a VIP with members) is filed as bug 1296419.
I confirmed Horizon does not return Internal server error even when
deleting a VIP with members and the VIP is successfully deleted. I mark
this bug Invalid in Horizon.
** Changed
Public bug reported:
When you attempt to delete a host aggregate that has associated hosts you get a
generic and confusing error message saying:
Error: Unable to delete host aggregate: host aggregate name
This error should be more specific and tell the user that the action
cannot be completed
Public bug reported:
In bug 1264228 and https://review.openstack.org/#/c/64137/, the default
value of OPENSTACK_KEYSTONE_DEFAULT_ROLE was changed from Member to
_member_ which is the default config value in keystone.
However, OPENSTACK_KEYSTONE_DEFAULT_ROLE in openstack_dashboard/settings.py is
** Changed in: neutron
Status: Fix Committed = 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/1292366
Title:
UnboundLocalError: local variable 'network_name' in
This bug has bee invalidated by patches that merged subsequently.
** Changed in: neutron
Status: In Progress = Incomplete
** Changed in: neutron
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
This issue is related to different values that MSVM_ComputerSystem's
Caption property can have on different locales.
** Affects: nova
Importance: Undecided
Status: New
** Tags: hyper-v
** Tags added: hyper-v
--
You received this bug notification because
Public bug reported:
when we call API with 'os_tenant_networks' to delete an existing network
it might fail due to unexpected reason, we should rollback the quota we
reserved eitherwise will face no quota later
** Affects: nova
Importance: Undecided
Assignee: jichencom (jichenjc)
** Also affects: nova
Importance: Undecided
Status: New
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: openstack-ci
Status: New = Incomplete
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
The project/user id of the user is not passed to the quotas.rollback methods in
conductor/manager.py if the instance is migrated by admin.
See:
http://git.openstack.org/cgit/openstack/nova/tree/nova/conductor/manager.py#n711
There's no way currently for Cinder to know about this situation.
It's actually a failure on Nova's part to clean up after itself when
deleting a VM IMO.
Also.. FYI there's a reset-state extension that you can/should use
rather than manipulating the DB directly.
** Changed in: cinder
Public bug reported:
when instance resize, it will call finish_migration at last to create new
instance and destroy old instance
if driver layer has problem in create new instance, the instance will be set to
'ERROR' state
we are able to use reset-state --active to reset the instance and use
Public bug reported:
When executing 'nova dns-domains', I got a 500 exception.
$nova dns-domains
2014-03-24 23:21:30.815 ERROR nova.api.openstack
[req-3dbd5f05-4be8-45c6-864e-daaaf0552042 admin demo] Caught error:
2014-03-24 23:21:30.815 TRACE nova.api.openstack Traceback (most recent call
Public bug reported:
When executing 'nova dns-domains', I got a 500 exception.
$nova dns-domains
2014-03-24 23:21:30.815 ERROR nova.api.openstack
[req-3dbd5f05-4be8-45c6-864e-daaaf0552042 admin demo] Caught error:
2014-03-24 23:21:30.815 TRACE nova.api.openstack Traceback (most recent call
Public bug reported:
When executing 'nova dns-domains', I got a 500 exception.
$nova dns-domains
2014-03-24 23:21:30.815 ERROR nova.api.openstack
[req-3dbd5f05-4be8-45c6-864e-daaaf0552042 admin demo] Caught error:
2014-03-24 23:21:30.815 TRACE nova.api.openstack Traceback (most recent call
27 matches
Mail list logo
