Public bug reported:
Test this case:
Assume a port's mac_address is 12:34:56:78:aa:bb
Then put these to allowed address pair:
[{ip_address: 10.0.0.1},
{ip_address: 10.0.0.2,
mac_address: 12:34:56:78:aa:bb}]
This can pass in extension's validator, but will cause error in db, for
Public bug reported:
Some time we can see attach/detach interface failed, but we didn't log
the detail info, that's hard to debug.
for example:
http://logs.openstack.org/02/111802/1/gate/gate-tempest-dsvm-neutron/eff16a6/logs/screen-n-cpu.txt.gz?#_2014-09-24_07_54_12_206
** Affects: nova
Public bug reported:
Boot one instance with security_group_api=nova , it will check Nova's
default security group firstly,
There is race condition that boot some instances at the first time for
same tenant. with config option security_group_api=nova , current
logic is :
1. get default
Public bug reported:
Creation of server with command
‘nova boot --image image --flavor m1.medium --nic port-id=port-id
--security-groups sec_grp name’
fails to attach the security group to the port/instance. The response payload
has the security group added but only default security group
At this time, it is outside the window to add this to Havana.
** Changed in: keystone/havana
Status: In Progress = Won't Fix
** Changed in: keystone/havana
Assignee: Adam Young (ayoung) = (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Reproduce steps
1: git clone git://git.openstack.org/openstack/horizon.git
2: cd horiozn bash -xxx ./run_tests.sh --integration
openstack_dashboard.test.integration_tests.tests.test_user_settings a.out
21
3:Internal Server Error
The server encountered an internal
Public bug reported:
_get_security_groups_on_port checks before that all security groups on port
belong to tenant - and if there are any that don't fulfill this requirement it
tries to raise SecurityGroupNotFound but fails with :
TypeError: 'set' object does not support indexing
Public bug reported:
ODL MD reraised errors returned by ODL in single operations and in full
synchronization.
In both cases, ODL MD could raise more adapted errors (i.e. server errors
instead of client errors).
** Affects: neutron
Importance: Undecided
Status: New
** Tags:
Public bug reported:
$neutron security-group-list --sort-key name
---
id namedescription
Public bug reported:
I created a security group with the other security group as the source
group, and booted a server with the security group:
$ nova secgroup-create source-any secgroup for any sources
$ nova secgroup-add-rule source-any tcp 1 65535 0.0.0.0/0
$
$ nova secgroup-create
Public bug reported:
Test steps :
1) create a volume from image
2) now boot instance with above volume
ssatya@juno:~/juno/devstack$ nova image-list
+--++++
| ID | Name
Public bug reported:
The security groups db queries are loading extra data from the ports
table that is unnecessarily hindering performance.
** Affects: neutron
Importance: Undecided
Assignee: Kevin Benton (kevinbenton)
Status: New
** Changed in: neutron
Assignee:
So this is an interesting possible feature, but that means it should
come in via a spec, not really via launchpad.
** Changed in: nova
Importance: Undecided = Wishlist
** Changed in: nova
Status: New = Opinion
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
The way test_backend uses domains leads to either many of the tests
being over overridden in test_backend_ldap, or just skipped (leading to
a risk that we are not sufficiently testing certain functionality - see
bug 1373113 as an example).
There is already a construct for
Public bug reported:
Now we can add allowed address pair to every net's port if allowed
address pair is enable.
This will cause security problem in a shared network, I think.
So we should add an limit for shared net or add a config entry in neutron.conf,
so administrator
can disables some
Public bug reported:
OpenContrail neutron plugin is not supporting portbinding.vnic_type
during port creation. Nova expects portbindings.vnic_type.
** Affects: neutron
Importance: Undecided
Assignee: Numan Siddique (numansiddique)
Status: In Progress
** Changed in: neutron
I'm not sure now what is right usage of this feature.
Hopefully, some typos on the documentation would be nice.
** Also affects: openstack-manuals
Importance: Undecided
Status: New
** Also affects: neutron
Importance: Undecided
Status: New
** No longer affects: neutron
--
Public bug reported:
I wanted to create a unique user role and add some build in policies to it.
I can create a new role but than discovered that instead of being able to add
storage permissions or network permissions for a user (so specific system
functionality) I have to build my own
Public bug reported:
There are columns named State and Status in Compute Services, Volume
Services and Network Agents tabs in System Information panel, however the
meaning of these two words are inconsistent.
It makes hard to translate them appropriately and needs to assign the
same/similar
Public bug reported:
Currently there are no functional tests for metadata seeding for glance-
manage. This tests should cover a specific lifecycle of metadata using
three api methods:
db_load_metadefs
db_unload_metadefs
db_export_metadefs
This tests concerns json files stored in
** 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/1348204
Title:
** Changed in: manila
Status: Fix Committed = Fix Released
** Changed in: manila
Milestone: None = juno-rc1
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Hmm. my previous comment seems wrong.
Anyway consistency is important and the majority of tabs is
to use Status columns with enabled/disabled.
I will swap status and state in Network Agents.
** Changed in: horizon
Importance: Medium = Undecided
** Changed in: horizon
Status: New =
Public bug reported:
Hi!
I'm running the latest git nova code from branch stable/icehouse and have
patched it to get rid of the duplicate feature bug
(commit 0f28fbef8bedeafca0bf488b84f783568fefc960).
I'm running libvirt 1.2.8 and qemu 2.0.2.
When I issue the command to do a live migration it
Public bug reported:
As part of the blueprint https://blueprints.launchpad.net/nova/+spec
/serial-ports we introduced an API extension and a websocket proxy
binary. The problem with the 2 is that a lot of the stuff was copied
verbatim from the novnc-proxy API and service which relies heavily on
Public bug reported:
In Keystone2Keystone federation Assertion XML object is missing
attribute 'version' which makes Shibboleth Service Providers complain
badly.
This parameter should be statically set to string value '2.0'
** Affects: keystone
Importance: Undecided
Assignee: Marek
Public bug reported:
LVM ephemeral storage backend is broken in the most recent Nova (commit
945646e1298a53be6ae284766f5023d754dfe57d)
To reproduce in Devstack:
1. Configure Nova to use LVM ephemeral storage by adding to
create_nova_conf function in lib/nova
iniset $NOVA_CONF libvirt
** Changed in: keystonemiddleware
Status: Fix Committed = 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/1328067
Title:
Token with placeholder ID issued
Status in
** Changed in: nova
Status: In Progress = Won't Fix
--
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/1368942
Title:
lxc test failure under osx
Status in OpenStack
This is unit test not tempest' tests.
** Changed in: tempest
Status: New = Invalid
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
** Changed in: keystonemiddleware
Status: Fix Committed = 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/1360446
Title:
client connection leak to memcached under
** Changed in: keystonemiddleware
Status: Fix Committed = 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/1332058
Title:
keystone behavior when one memcache backend
I missed this too, as I also was using Keystone v2. Thanks, Julie
** Changed in: horizon
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
Public bug reported:
EC2KeystoneAuth uses httplib.HTTPSConnection objects. In Python 2.x
those do not perform CA checks so client connections are vulnerable to
MiM attacks.
This should use requests instead, and pick up the local cacert params if
needed.
** Affects: nova
Importance:
Public bug reported:
HTTPSClientAuthConnection uses httplib.HTTPSConnection objects. In
Python 2.x those do not perform CA checks so client connections are
vulnerable to MiM attacks.
This should be changed to use the requests lib.
** Affects: nova
Importance: Critical
Status:
Public bug reported:
VMwareHTTPWriteFile uses httplib.HTTPSConnection objects. In Python 2.x
those do not perform CA checks so client connections are vulnerable to
MiM attacks.
This is the specific version of
https://bugs.launchpad.net/nova/+bug/1188189
** Affects: nova
Importance:
Public bug reported:
plugins/xenserver/xenapi/etc/xapi.d/plugins/glance _upload_tarball uses
httplib.HTTPSConnection objects. In Python 2.x those do not perform CA
checks so client connections are vulnerable to MiM attacks.
This is the specific version of
This bug was fixed in the package cloud-init - 0.7.5-0ubuntu1.2
---
cloud-init (0.7.5-0ubuntu1.2) trusty-proposed; urgency=medium
* d/patches/lp-1353008-cloud-init-local-needs-run.conf:
backport change to cloud-init-local.conf to depend on /run being
mounted (LP: #1353008)
Public bug reported:
Attribute issuer should always be set to CONF.saml.idp_entity_id,
otherwise entityID from the IdP metadata and the generated assertion can
differ and hence make Service Provider reject the assertion.
** Affects: keystone
Importance: Undecided
Assignee: Marek Denis
Nova bugs will be tracked in the separate bugs listed above, so removing
Nova from this bug.
** 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/1188189
Title:
Reviewed: https://review.openstack.org/119980
Committed:
https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=d5a92e28ef8f85012eced9d08d0c2592771da4bc
Submitter: Jenkins
Branch:master
commit d5a92e28ef8f85012eced9d08d0c2592771da4bc
Author: darrenchan dazzac...@yahoo.com.au
** Also affects: neutron/icehouse
Importance: Undecided
Status: New
** Changed in: neutron/icehouse
Importance: Undecided = Medium
** Changed in: neutron/icehouse
Status: New = In Progress
** Changed in: neutron/icehouse
Assignee: (unassigned) = Cédric OLLIVIER (m.col)
Public bug reported:
This is a wish list.
Since we are moving to v3, it is better to add v3 endpoint in
sample_data.sh. We still have only v2.0 endpoint.I don't think
keystoenclient will be affected since it doesn't use the endpoint from
catalog, but relies on version discovery
** Affects:
This should be fixed now upstream
** 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/1330985
Title:
This is actually libvirt itself failing to do live migration, not
anything in Nova. So this really needs to be taken upstream.
** Changed in: nova
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Fix proposed to branch: master
Review: https://review.openstack.org/124125
** Changed in: horizon
Status: Opinion = In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
** Changed in: neutron/havana
Status: In Progress = 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/1357379
Title:
policy admin_only rules not enforced when changing value
Public bug reported:
On Windows / Hyper-V Server 2008 R2, when a switch port have to be disconnected
because the VM using it was removed,
DisconnectSwitchPort will fail, returning an error code and a HyperVException
is raised. If the exception is raised, the switch port is not removed and will
Public bug reported:
Hi guys,
We've noticed a weird behavior with nova compute reporting the wrong
free memory size in Grizzly and Ubuntu. The version of libvirt used is
1.0.2 and according to the documentation of libvirt, the memory is
returned in KB but in the code, it says MB? Did I
Public bug reported:
This is not really useful:
http://logs.openstack.org/17/123917/2/check/check-tempest-dsvm-
neutron/4bc2052/logs/screen-n-cpu.txt.gz?level=TRACE#_2014-09-25_17_35_11_635
2014-09-25 17:35:11.635 ERROR nova.virt.libvirt.driver
[req-50afcbfb-203e-454d-a7eb-1549691caf77
Public bug reported:
In Juno in nova/virt/libvirt/config.py:
LibvirtConfigGuestPUNUMA.parse_dom() calls super with a capital 'D' in
parse_dom().
super(LibvirtConfigGuestCPUNUMA, self).parse_Dom(xmldoc)
LibvirtConfigObject does not have a 'parse_Dom()' method. It has a
'parse_dom()'
Public bug reported:
This patch removes the method _convert_to_nsx_transport_zones
and instead calls it from nsx_utils directly.
** Affects: neutron
Importance: Undecided
Assignee: Aaron Rosen (arosen)
Status: In Progress
--
You received this bug notification because you are
Digging further after proposing a fix to the Nova driver, there is
*also* a race inside of ironic/conductor/manager.py and
ironic/conductor/utils.py -- I am posting a fix for those now.
** Changed in: ironic
Status: Invalid = In Progress
** Changed in: ironic
Assignee: Rakesh H S
Public bug reported:
When lazy is enabled the i18n translation object does not support
str() which causes failures like:
UnicodeError: Message objects do not support str() because they may
contain non-ascii characters. Please use unicode() or translate()
instead.
** Affects: nova
I'm forced into assuming this has been fixed without being tracked,
since there's no actual spelling errors cited here to confirm that
assumption against.
** Changed in: keystone
Status: In Progress = Invalid
--
You received this bug notification because you are a member of Yahoo!
Same code is also in oslo/vmware/rw_handles.py
** Also affects: oslo.vmware
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).
This was published as OSSN-0027:
https://wiki.openstack.org/wiki/OSSN/OSSN-0027
** 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 neutron.
This was published as OSSN-0024:
https://wiki.openstack.org/wiki/OSSN/OSSN-0024
** Changed in: ossn
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Public bug reported:
LBaaS API doesn't check the validity of the input parameters. Creating a
pool with invalid subnet_id, and updating a pool with invalid
health_monitors, can both success. The API should return a BadRequest
response instead.
** Affects: neutron
Importance: Undecided
Public bug reported:
When creating a floating_ip_bulk which already exists,
HTTPBadRequest(400) is returned, which should be changed to
HTTPConflict(409).
$ nova floating-ip-bulk-create 192.0.20.0/28 --pool private
ERROR (BadRequest): Floating ip 192.0.20.1 already exists. (HTTP 400)
Public bug reported:
Multiple neutron servers may read from the consistency hash table in the
big switch plugin simultaneously, which will cause the one with a later
request to receive an inconsistency error.
This is an issue with RPC induced backend requests (port update) or
active-active
** Changed in: nova
Status: Confirmed = 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/1208743
Title:
network uuid hasn't been checked in create server
62 matches
Mail list logo
