Public bug reported:
Glance uses custom function to search endpoint in service catalog:
https://github.com/openstack/glance/blob/master/glance/common/auth.py#L259
But that functionality is also available in python-keystoneclient:
Public bug reported:
We have installed kilo release
[root@sienna ~]# uname -a
Linux sienna 3.10.0-327.4.5.el7.x86_64 #1 SMP Mon Jan 25 22:07:14 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
[root@sienna ~]# cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
Reviewed: https://review.openstack.org/241824
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=edea873565d07120141ae0f76199d6a3aee2959d
Submitter: Jenkins
Branch:master
commit edea873565d07120141ae0f76199d6a3aee2959d
Author: Mathieu Gagné
Date: Wed
looks like middlware related, not keystone server, changing project
** Also affects: keystonemiddleware
Importance: Undecided
Status: New
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Public bug reported:
Description
Boot a VM and check for the flows .
execute /opt/stack/neutron/neutron/agent/linux/utils.py:156
2016-02-10 11:04:22.977 11780 DEBUG neutron.agent.linux.utils [-] Running
command (rootwrap daemon): ['ovs-ofctl', 'add-flows', 'br-sec', '-']
execute_rootwrap_daemon
Public bug reported:
We currently use scope to clear table selections. This is not ideal
because it breaks encapsulation and encourages the use of scope over
ctrl. We should provide a method that can clear instead.
Reference:
Reviewed: https://review.openstack.org/279103
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=72bbc8dcaa93825239533d4590de30345d35c4d7
Submitter: Jenkins
Branch:master
commit 72bbc8dcaa93825239533d4590de30345d35c4d7
Author: Itxaka
Date: Thu Feb
Public bug reported:
Powered-ff VMs still get 'cpu_util' metrics with zero values. There
should be a distinction between no values and zero values. There is no
such problem with, say, 'memory.usage' metric.
I tested it on KILO.
[root@controller ~(keystone_admin)]# nova show
Public bug reported:
openstack_dashboards.dashboards.project.instances.tests:InstanceAjaxTests.test_row_update_flavor_not_found
test is missing a mock for "servers_update_addresses" causing the test
to output "Cannot connect to neutron"
Strangely enough, the test is passing, which is not really
Marked as high priority since it's nova-net specific at this point and
that's what the related fixes are for.
** Also affects: nova/kilo
Importance: Undecided
Status: New
** Also affects: nova/liberty
Importance: Undecided
Status: New
** Changed in: nova/kilo
Status:
I was not aware that we allowed 500s in that case. It makes sense, just
unfortunate. So yeah, this bug is invalid.
** Changed in: nova
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Reviewed: https://review.openstack.org/277439
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=6b04f47eae87dc78e609f7089cf31c14bf42ce6d
Submitter: Jenkins
Branch:master
commit 6b04f47eae87dc78e609f7089cf31c14bf42ce6d
Author: Rob Cresswell
** Also affects: tempest
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 OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1513558
Title:
unable to reproduce the bug on neutron.
** Changed in: neutron
Assignee: venkata anil (anil-venkata) => (unassigned)
** No longer affects: neutron
** Changed in: networking-ovn
Assignee: venkata anil (anil-venkata) => (unassigned)
--
You received this bug notification because you
** Also affects: neutron (Ubuntu Xenial)
Importance: High
Status: Triaged
** Also affects: neutron (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Xenial)
Public bug reported:
When use CEPH as storage backend and try to resize instance to smaller
flavor, resize fails with wrong message.
Steps to reproduce:
1.) Create instance from image with flavor.
2.) Try resize instance to flavor which have smaller root disk.
For example:
I'm not really sure why this is filed against nova.
** Changed in: nova
Status: New => Opinion
--
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/1522381
Title:
evacuate assumes you've done all the fencing and cleanup of the node
itself, this is by design.
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
WebSSO uses OPENSTACK_KEYSTONE_URL to generate URLs to point a browser
at. Under many configurations this is fine, but in setups where there
may be multiple networks, it can be problematic. For instance, if
horizon is configured to talk to keystone over a network that is
Is there an upstream eventlet bug for 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 neutron.
https://bugs.launchpad.net/bugs/1482633
Title:
requests to SSL wrapped
** Also affects: nova/liberty
Importance: Undecided
Status: New
** Changed in: nova/liberty
Status: New => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Reviewed: https://review.openstack.org/272313
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7c24fa111e0ea0b656858c7f54e55a1eac5fc2d3
Submitter: Jenkins
Branch:master
commit 7c24fa111e0ea0b656858c7f54e55a1eac5fc2d3
Author: Salvatore Orlando
** Description changed:
+ [Impact]
+ Restarts of openvswitch (typically on upgrade) result in loss of tunnel
connectivity when the l2population driver is in use. This results in loss of
access to all instances on the effected compute hosts
+
+ [Test Case]
+ Deploy cloud with
Reviewed: https://review.openstack.org/252597
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=85973b7e907a41352d6aa8fe7dbc0f4afb89bdbc
Submitter: Jenkins
Branch:master
commit 85973b7e907a41352d6aa8fe7dbc0f4afb89bdbc
Author: Paulo Ewerton
Reviewed: https://review.openstack.org/278609
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=eb8141051abe64de7ad9398fb2adaf9a0a79d62d
Submitter: Jenkins
Branch:master
commit eb8141051abe64de7ad9398fb2adaf9a0a79d62d
Author: Kevin Benton
Date: Wed
Public bug reported:
If neutron-meter-agent is installed and enabled, and a meter-label is
created, all traffic between internal networks becomes NATed, which is
unexpected and potentially causes firewall/routing issues. This happens
because meter-agent does not define stateless flag during
We can't let people that don't own the network select their own fixed
IP. Using the fixed IP field, someone can pick addresses outside of the
allocation pool so it's restricted to an owner-only operation.
It might be worth discussion if we should allow them to select a
subnet_id but not a
** Project changed: neutron => python-neutronclient
** Changed in: python-neutronclient
Importance: Undecided => Wishlist
** Tags added: rfe
** Changed in: python-neutronclient
Status: New => Triaged
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
We run tempest in such an environment that all ssh keys, personality files,
etc. go through metadata service.
Which requires metadata route to 169.254.169.254 being provided by DHCP.
We faced rather complicated problem in scenario/test_network_v6.py:
Networking
** Project changed: neutron => tap-as-a-service
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1544176
Title:
br-int with Normal action
Status in tap-as-a-service:
New
Bug
Reviewed: https://review.openstack.org/272737
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=5cc5a841109b082395d9664edcfc11e31fb678fa
Submitter: Jenkins
Branch:master
commit 5cc5a841109b082395d9664edcfc11e31fb678fa
Author: Balazs Gibizer
Similarly glance-manage db purge 1
111 fails
and give long stack trace.
** Also affects: glance
Importance: Undecided
Status: New
** Changed in: glance
Assignee: (unassigned) => Dinesh Bhor (dinesh-bhor)
** Summary
Reviewed: https://review.openstack.org/274996
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=af505dacd1d8d64f602629fa2e334582c3a89d5b
Submitter: Jenkins
Branch:master
commit af505dacd1d8d64f602629fa2e334582c3a89d5b
Author: Richard Jones
Date:
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: sahara
Assignee: (unassigned) => javeme (javaloveme)
** Changed in: cinder
Assignee: (unassigned) => javeme (javaloveme)
--
You received this bug notification because you are a member of Yahoo!
Reviewed: https://review.openstack.org/267615
Committed:
https://git.openstack.org/cgit/openstack/ceilometer-powervm/commit/?id=8e1651bba33dc1546f4cb0da1e52a50253802cbe
Submitter: Jenkins
Branch:master
commit 8e1651bba33dc1546f4cb0da1e52a50253802cbe
Author: Harshada Mangesh Kakad
Public bug reported:
Even if DHCP namespace creation fails at the network node due to some
reason, neutron API still returns success to the user.
2016-01-18 02:51:12.661 ^[[00;32mDEBUG neutron.agent.dhcp.agent [^[[01
;36mreq-f6d7a436-b9ff-45ca-9cfc-0f147b97effb
Reviewed: https://review.openstack.org/267648
Committed:
https://git.openstack.org/cgit/openstack/networking-powervm/commit/?id=6b14ac69332056a14c98f8b4401ac3a93566a066
Submitter: Jenkins
Branch:master
commit 6b14ac69332056a14c98f8b4401ac3a93566a066
Author: Harshada Mangesh Kakad
This is going to require a spec, as it will be a microversion. I agree
GET is the wrong method for these kinds of things.
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of
** Changed in: networking-ovn
Assignee: (unassigned) => venkata anil (anil-venkata)
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => venkata anil (anil-venkata)
--
You received this bug notification because you are
Public bug reported:
http://logs.openstack.org/47/275747/3/gate/gate-horizon-dsvm-
integration/b83e62a/console.html#_2016-02-09_01_25_30_551
2016-02-09 01:25:30.551 | 2016-02-09 01:25:30.522 | Traceback (most recent call
last):
2016-02-09 01:25:30.555 | 2016-02-09 01:25:30.525 | File
Public bug reported:
http://logs.openstack.org/25/266125/3/gate/gate-horizon-dsvm-
integration/0476236/console.html.gz#_2016-02-05_14_47_17_144
2016-02-05 14:47:17.144 | 2016-02-05 14:47:17.123 | ERROR:
Public bug reported:
I discovered this bug while refactoring functional tests. This happens
in the current Nova master.
Update the following files:
-
nova/tests/functional/api_sample_tests/api_samples/os-extended-server-attributes/v2.16/server-get-resp.json.tpl
-
Public bug reported:
Stock neutron grenade no longer covers this, so we need a grenade plugin
for neutron-lbaas.
** Affects: neutron
Importance: Undecided
Status: New
** Tags: lbaas
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Reviewed: https://review.openstack.org/274131
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=5062e1bb50b1bbae5f56e2f82f96e6484c12e824
Submitter: Jenkins
Branch:master
commit 5062e1bb50b1bbae5f56e2f82f96e6484c12e824
Author: kairat_kushaev
Date:
Public bug reported:
Kilo builds, with eventlet 0.18.2 have a constant traceback:
2016-02-12 00:47:01.126 3936 DEBUG nova.api.openstack.wsgi [-] Calling method
'>' _process_stack
/opt/bbc/openstack-11.0-bbc153/nova/local/lib/python2.7/site-packages/nova/api/openstack/wsgi.py:783
2016-02-12
Reviewed: https://review.openstack.org/271464
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=73bb9a59435c287c6ab364d92a6defacbbcfa680
Submitter: Jenkins
Branch:master
commit 73bb9a59435c287c6ab364d92a6defacbbcfa680
Author: Justin Pomeroy
Reviewed: https://review.openstack.org/246275
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=62ccd13a6f5d67aeb1e4845b187d1e3ab82ded59
Submitter: Jenkins
Branch:master
commit 62ccd13a6f5d67aeb1e4845b187d1e3ab82ded59
Author: Itxaka
Date: Tue
Public bug reported:
This is odd when looking at https://github.com/openstack/neutron-
fwaas/blob/master/neutron_fwaas/tests/contrib/gate_hook.sh.
https://jenkins05.openstack.org/job/gate-neutron-fwaas-dsvm-
api/2/consoleFull
2016-02-11 23:04:01.253 | ++
Public bug reported:
I've been thinking about this for a little while now. There seems to be
something different about floating IP subnets and other (I'll call them
static in this context) subnets in some use cases.
- On an external network where operators wish to use private IPs for router
Public bug reported:
During live migration with attached volume, instance is moved to ERROR
state and stuck in task state Migrating when cinder client exception is
thrown.
Steps:
1. Create a nova instance
2. Attach a cinder volume
3. Raise cinderclient exception in
** Changed in: neutron/kilo
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1442357
Title:
Brocade MLX plug-ins config options for switch need a group
Reviewed: https://review.openstack.org/270012
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=d099477de3dafcf5da064c2b46b227bbe6f8440d
Submitter: Jenkins
Branch:master
commit d099477de3dafcf5da064c2b46b227bbe6f8440d
Author: Kenji Ishii
Date:
Public bug reported:
When creating a v3 keystoneclient using non admin credentials I'm able
to get the list of service providers from the service catalog, but the
policy doesn't allow to list or get service providers by default.
>>> ksclient2.service_catalog.catalog[u'service_providers']
Status update:
http://eavesdrop.openstack.org/meetings/neutron_drivers/2016/neutron_drivers.2016-02-11-22.00.log.html#l-48
** Changed in: neutron
Status: Triaged => Won't Fix
** Changed in: neutron
Assignee: Hong Hui Xiao (xiaohhui) => (unassigned)
--
You received this bug
If we want to be more explicit about this in the networking-guide and
clarify the perceived side-effects of the existing implementation, then
it's fine, but this is not exactly a neutron 'bug', but a documentation
one.
** Changed in: neutron
Status: Triaged => Won't Fix
--
You received
Reviewed: https://review.openstack.org/278624
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f846519e5af6efa5007896c7ac75d13b415c3f53
Submitter: Jenkins
Branch:master
commit f846519e5af6efa5007896c7ac75d13b415c3f53
Author: malos
Date: Wed Feb
Reviewed: https://review.openstack.org/270057
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=38e115d385153a631216a120df68a903b2faa6d7
Submitter: Jenkins
Branch:master
commit 38e115d385153a631216a120df68a903b2faa6d7
Author: Ajaya Agrawal
Date:
Public bug reported:
[Description]
Currently it is not possible to run multiple L2 agents on a host without them
conflicting with each other. For example, if I set up and configure Linux
bridge and Open vSwitch agents on a compute host both agents will try to
enslave the tap interface of the
It is not clear that this is a nova issue, but a wholely ironic issue.
** 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).
If you are creating a tracking bug for yourself, please move to
confirmed
** Changed in: nova
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
This is definitely a core oslo.service issue with shutting down, this
keeps tripping us up.
** Changed in: oslo.service
Status: New => Confirmed
** Changed in: oslo.service
Importance: Undecided => Critical
** Changed in: nova
Status: New => Invalid
--
You received this bug
It seems really weird about why keystone just stops working. That is the
thing that really needs to be sorted out.
** 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
Yes, that is by design
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Wishlist
** Changed in: nova
Status: Opinion => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
This was released in oslo.db 4.1.0.
Something else must be wrong about your environment for this to be an
issue, because it's definitely in 4.2
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
These changes all come from keystone libraries. Nova doesn't do any
registration of this config variables itself. Please poke the keystone
auth folks about this.
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: nova
Status: New => Incomplete
--
You
Nova is an API server, it's fine to put whatever into these fields.
Should the clients scrub this, probably.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Importance: Undecided => Low
--
You received this bug notification because you are a member of Yahoo!
It's not there in 2.0 either. The help text is super out of whack saying
that volumes have 'gpu' associated with them.
I just don't think this ever existed.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
67 matches
Mail list logo