Public bug reported:
Description of problem:
When trying to create a new network with illegal values or empty values in its
fields, error message is not generated indicating the incorrect fields
Version-Release number of selected component (if applicable):
Public bug reported:
When the ESX running the VM's was deleted or removed the following
exception occurred when the instance was deleted via OpenStack:
2015-07-02 21:33:00.638 21297 TRACE oslo.messaging.rpc.dispatcher
ManagedObjectNotFound: The object has already been deleted or has not been
Public bug reported:
Using a devstack setup, fairly latest!
1) Create a cinder volume (used GlusterFS as the cinder backed) - cv1
2) Attach cv1 to vm1 (vm1 is a nova VM in running state)
3) Create 2 snapshots of vol1 using cinder snapshot-create ... cv1-snap1,
cv1-snap2
4) Stop the nova vm vm1
Public bug reported:
This is wishlist bug
Add a cancel button in following page :
http://Horizon IP /admin/defaults/update_defaults
or
Admin - Systems - Defaults - Update Defaults
** Affects: horizon
Importance: Undecided
Assignee: Ritesh (rsritesh)
Status: New
** Changed
Public bug reported:
'test_create_project_invalid_domain_id' intends to test create project with
invalid domain id, but it didn't use the invalid reference data but use a empty
request body.
see:
Public bug reported:
Policies defined for the neutron extension resource attributes are not
enforced.
In the case of address scopes, even though the policy.json has the
below rules, neutron is allowing the tenant user to create a shared
address scope.
create_subnetpool: ,
The cause for the degradation could be anywhere - keystone or any other
co-located service which is hitting your devstack node resources. The
only way Tempest could make thing worst is by not cleaning test
resources properly, which still would hardly justify the slowdown.
Such a slow down is
You have been subscribed to a public bug:
If I first run tempest on a newly-created VM with and install devstack
with only keystone setup, first parallel run of
tempest.api.identity.admin.v3 tests take around 20 seconds. If I run
them again, they take around 38 seconds, third run would be around
Public bug reported:
Description of problem:
Live resizing an instance is failed, although nova.conf is configured as
allow_migrate_to_same_host=true, allow_resize_to_same_host=true
Version-Release number of selected component (if applicable):
Public bug reported:
I have a fresh ubuntu install and i git DevStack All on a VM, now here is how
i reproduce my bug:
1-stack.sh and open my ip adress for horizon (dashboard) everything works fine
and i am deploying instances .
2-unstack.sh to bring services down.
3-rejoin-stack.sh and
Public bug reported:
The IBM DS8000 storage subsystem supports different host types for
Fibre-Channel. When LUNs are
mapped to host ports, the user has to specify the LUN format to be used, as
well as the Volume Group address type. If those properties are not set
correctly, the host operating
Public bug reported:
Background: Nova commit eaaa659333c7586a71155c065dfb0f7b7e3758fc
modified the Cells code (specifically instance_update_at_top()) to use
objects instead of primitive dicts. One consequence of this is that the
changed fields tracking now controls what updates are applied to
Public bug reported:
Incorrect json input cause error instead of being invalidated properly:
Type error in dns_nameservers raise keyerror:
ERROR neutron.api.v2.resource [req-be58f6e1-db2f-4b2e-9620-afb49bdd4552 demo
d1da3f8632e3413b915eda78899806d7] create failed
Traceback (most recent call
Public bug reported:
Part of test_relationships() is spent building the subobject tree of
each nova object
(http://git.openstack.org/cgit/openstack/nova/tree/nova/tests/unit/objects/test_objects.py#n1274).
In _build_tree(), a tree is built with all objects in the nova registry,
and then it finds
This is purely a Glance bug and can be recreated without Nova in the
picture at all, therefore I do not believe that the bug fix mentioned in
comment 5 will fix this.
See the recreation steps in comment 2. This can be completely
abstracted from Nova. The bug is that Glance v1 allows you to set
Public bug reported:
Requirements.txt defines the pbr version as
pbr2.0,=0.11
but version 0.11 cannot handle the following syntax in the windows
section:
# Windows-only requirements
pywin32;sys_platform=='win32'
wmi;sys_platform=='win32'
This causes the following error when installing neutron.
Public bug reported:
Trace:
ERROR neutron.agent.linux.utils [req-26ce0148-4bc4-40bd-96ac-e9d484f37b61 demo
12b3399d1cb64da488e20f6a7c355d10]
Command: ['sudo', '/usr/local/bin/neutron-rootwrap',
'/etc/neutron/rootwrap.conf', 'ip', 'netns', 'exec',
'qdhcp-6cdefebf-ab88-4f55-b2b9-719286a7b75b',
Public bug reported:
Trace:
ERROR neutron.agent.dhcp_agent [-] Unable to enable dhcp for
125c7403-1ef1-489c-bc0c-cf6a0f83e742.
Traceback (most recent call last):
File /opt/stack/neutron/neutron/agent/dhcp_agent.py, line 128, in
call_driver
getattr(driver, action)(**action_kwargs)
File
Public bug reported:
There are some unit tests for the Fernet token provider that live
outside of the functional-like tests (test_v3_auth.py, for example) [0].
These tests should include a test to assert that the Fernet token
provider returns False when asked if it's tokens need persistence [1].
Public bug reported:
When using Keystone v3 with Horizon with the Multi-Domains disabled, the
Domains panel is still visible.
Settings:
OPENSTACK_API_VERSIONS = { identity: 3, }
OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT = False
Policy file:
The default one (not the domains specific one)
In
Public bug reported:
If a node running nova-compute is using the neutron with the linuxbridge
agent, and the node is also running other neutron agents like the
l3-agent or dhcp-agent (ie the node is acting as compute node and a
network node) then races can happen when both nova-compute and the
Public bug reported:
The evacuate code as it is currently in nova will delete instances when
instance.host != $(hostname) of the host. This assumes that the instance
has been evacuated (because its hostname changed). In that case,
deleting the local residue is correct, but if the host's hostname
** No longer affects: swift
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1469974
Title:
kilo version swift doesn't work showing swiftclient:Authorrization
Failure the resource
Public bug reported:
With this change https://review.openstack.org/#/c/121737/
autodoc_index_modules was set to 0 in the [pbr] section of setup.cfg so
that you can no longer get to git/nova/doc/build/html/py-modindex.html
locally to verify that module docstrings are correct.
We should enable
Public bug reported:
I have just upgraded Openstack from Juno to Kilo and I am testing all
the features.
We run 14.04 Ubuntu, all neutron packages are 1:2015.1.0-0ubuntu1~cloud0
It seems when I am trying to create a VPN IPSec Site Connection, the
master L3 router is not chosen, but instead it
Public bug reported:
The nova.objects.fields.DiskBus enum field type added here:
https://review.openstack.org/#/c/76234/
Is missing the 'uml' and 'lxc' disk bus types checked here:
http://git.openstack.org/cgit/openstack/nova/tree/nova/virt/libvirt/blockinfo.py#n112
** Affects: nova
Public bug reported:
When listing federated projects using unscoped token an EmptyCatalog
Exception is thrown. KeystoneClient should handle this exception. Line
36 in [1]
[1]
** Changed in: swift
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1192966
Title:
Potentially insecure dependency loading
Status in OpenStack Image
Public bug reported:
The MAX_FUNC value in nova/pci/devspec.py is set to 0x7. This limits us
to a relatively small number of VFs per PF, which is annoying when
trying to use SRIOV in any sort of serious way.
** Affects: nova
Importance: Undecided
Assignee: Chris Friesen (cbf123)
This is normally handled by utilization/billing tools that walk the
drives to see what's there and report on usage in the cluster.
** Changed in: swift
Status: New = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
in the function of create_trust (Corresponding file
is:/keystone/trust/core.py),it should show the message as follows
remaining_uses must not be set if redelegation is allowed.but missing raise
statement in the following code:
if 'remaining_uses' in trust:
Public bug reported:
In the function of create_trust (Corresponding file
is:/keystone/trust/core.py),the judgment for “remaining_uses” can be deleted,
because controller has registered a schema to validate a resource reference.
if not redelegatable:
trust['redelegation_count'] =
Public bug reported:
When the /etc/keystone/domains directory is empty, execute keystone-
manage domain_config_upload --all without no information notification
.Maybe it can show no file can be loaded.
** Affects: keystone
Importance: Undecided
Status: New
--
You received this
Public bug reported:
We have all this infrastructure in /OS-
FEDERATION/identity_providers/{id}/protocol/{id} to uniquely identify
the relationship between an identity provider and a protocol for
interacting with that provider so we can apply mappings. With websso we
then hard code a route of
Public bug reported:
Neutron doesn't have a way to test a newly added network node by
deploying test resource before any customer resource on the node is
deployed. Nova and Cinder has the setting of “enable_new_services” in
each conf to disable the initial service status to achieve this. This
** Changed in: keystone
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1210141
Title:
Document howto config LDAP identity with non-DN based ids.
36 matches
Mail list logo
