Looks like this is working as planned.
** Changed in: neutron
Status: New => Opinion
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1621086
Title:
Port delete on router interface
Public bug reported:
The current DHCP notifier only tells the DHCP agents things when
ports/subnets/networks are modified via the Neutron API. This is
problematic because service plugins may modify ports directly via the
core plugin API, which results in the agents not being notified unless
specia
Public bug reported:
The material theme is missing an icon for star outline. so, if a horizon
plugin uses fa-star-o, the material theme just shows an empty box.
** Affects: horizon
Importance: Undecided
Assignee: Travis Tripp (travis-tripp)
Status: In Progress
** Changed in: h
Reviewed: https://review.openstack.org/319276
Committed:
https://git.openstack.org/cgit/openstack/cinder/commit/?id=0adde01a06d81ab39f536794e178d0434e9783a2
Submitter: Jenkins
Branch:master
commit 0adde01a06d81ab39f536794e178d0434e9783a2
Author: Sven Anderson
Date: Fri May 20 16:20:48 201
Reviewed: https://review.openstack.org/357494
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=cdb9b6820dc17971bca24adfc0b56f030f0ae827
Submitter: Jenkins
Branch:master
commit cdb9b6820dc17971bca24adfc0b56f030f0ae827
Author: Michael Wurtz
Date: Thu Aug 18 14:53:33 2016
Reviewed: https://review.openstack.org/365177
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=73bdbe1f87ac3571bb5a348158ad1e4ece73fbcc
Submitter: Jenkins
Branch:master
commit 73bdbe1f87ac3571bb5a348158ad1e4ece73fbcc
Author: Sean Perry
Date: Fri Sep 2 16:48:54 2016
Public bug reported:
The material theme is missing an icon for filter. so, if a horizon
plugin uses fa-filter, the material theme just shows an empty box.
** Affects: horizon
Importance: Undecided
Status: New
** Changed in: horizon
Milestone: None => ocata-2
** Changed in: hor
** Changed in: cinder
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/1538620
Title:
Attach with host and instance_uuid not backwa
I don't believe this is an issue anymore, other than the caveat
discussed elsewhere that nova and cinder need to use the same lock_dir
if run on the same host. Please feel free to reopen if this is not the
case.
** Changed in: cinder
Status: Triaged => Invalid
--
You received this bug not
Recloning the repo and reinstalling the venv fixed the issue.
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/162
Public bug reported:
2016-09-07 17:17:36.330 DEBUG neutron.wsgi [-] (11553) accepted
('192.168.56.101', 44115) from (pid=11553) server
/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py:868
2016-09-07 17:17:36.331 INFO neutron.wsgi
[req-9325d159-689c-4eec-a2f2-09a3cd2cdd5d
tempest-Routers
Public bug reported:
When running keystone with uwsgi, the following warning and traceback is
generated:
http://paste.openstack.org/show/568396/
This doesn't happen in devstack where keystone is run under apache.
The commit that introduces the issue is
http://git.openstack.org/cgit/openstack/ke
Looks like this still works for Keystone v2.0. I just tried it against a
v2.0 endpoint with the latest Horizon master, and the images per page
setting worked.
Horizon just can't support it for v3 yet, since Keystone v3 doesn't
support it.
There was a blueprint for Keystone v3 to support it, but i
Reviewed: https://review.openstack.org/365068
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=09627f2a0bd0c4ad05671d4646557066e606f2ad
Submitter: Jenkins
Branch:master
commit 09627f2a0bd0c4ad05671d4646557066e606f2ad
Author: Chris Dent
Date: Fri Sep 2 15:58:38 2016 +000
Public bug reported:
For VM boot on KVM HV, the noVNC console keeps popping up the following
exception whenever any key is pressed. Please refer to attached screenshot for
details.
"[32.786640] atkbd serio0: Use 'setkeycodes 00 ' to make it know.
[60.026326] atkbd serio0: Unknown key pressed (t
Public bug reported:
https://review.openstack.org/324012
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/glance" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option nee
** Changed in: nova/mitaka
Status: Confirmed => In Progress
** Changed in: nova/mitaka
Importance: Undecided => Medium
** Changed in: nova/mitaka
Assignee: (unassigned) => Ken'ichi Ohmichi (oomichi)
** Also affects: nova/liberty
Importance: Undecided
Status: New
** Tags
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/305137
** No longer affects: curtin
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1621
Public bug reported:
Steps to reproduce:
1. dpkg-reconfigure tzdata and select there Europe/Moscow (UTC+3).
2. Restart mysql
3. Configure opportunistic tests with the following command in mysql:
GRANT ALL PRIVILEGES ON *.* TO 'openstack_citest' @'%' identified by
'openstack_citest' WITH GRANT OPT
** Package changed: juju (Ubuntu) => juju-core (Ubuntu)
** Also affects: curtin
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1621180
Title
Reviewed: https://review.openstack.org/313086
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9a535a1f848c7813169fdd7d042a29678c554092
Submitter: Jenkins
Branch:master
commit 9a535a1f848c7813169fdd7d042a29678c554092
Author: Yosef Hoffman
Date: Thu May 5 11:12:23 201
Based on the discussion on the proposed patch [1], we don't want to
propagate the one-off setting of swap and ephemeral disk [2] from the
API further throughout the codebase. If anything, those options should
be removed from the API.
[1] https://review.openstack.org/#/c/352522/
[2]
http://docs.op
Public bug reported:
$ cat /tmp/foo.ud
#cloud-config
apt_mirror: ''
$ lxc launch ubuntu-daily:yakkety sm-y0 "--config=user.user-data=$(cat
/tmp/foo.ud)"
$ sleep 10
$ lxc exec sm-y0 grep yakkety /etc/apt/sources.list | head -n 3
deb yakkety main restricted
deb-src yakkety main restricted
d
Reviewed: https://review.openstack.org/352436
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=db032d6ad5e75d66d08f4b1a76b4b01ec2e0fc10
Submitter: Jenkins
Branch:master
commit db032d6ad5e75d66d08f4b1a76b4b01ec2e0fc10
Author: majik
Date: Mon Aug 8 21:55:24 2016 +0800
So, after a bit of investigation, I found that's actually not a
regression and we had other bug reports about that. The one I could
refer is https://bugs.launchpad.net/nova/+bug/1526715 which is
technically not a duplicate but where the proposal is very close to the
one you wrote : https://review.o
Reviewed: https://review.openstack.org/365684
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=3756bc510526531e3442da6d825cc90f44faa355
Submitter: Jenkins
Branch:master
commit 3756bc510526531e3442da6d825cc90f44faa355
Author: Kevin Benton
Date: Mon Sep 5 08:26:01 2016
Public bug reported:
Need release name/API version/status info on 'versions' api-ref page.
** Affects: glance
Importance: High
Assignee: Brian Rosmaita (brian-rosmaita)
Status: In Progress
** Tags: api-ref
--
You received this bug notification because you are a member of Ya
Public bug reported:
When deploying with several volumes the block_device_mappings column in
table build_requests can run out of space causing the below error.
2016-09-07 01:22:24.936 23522 ERROR oslo_db.sqlalchemy.exc_filters Traceback
(most recent call last):
2016-09-07 01:22:24.936 23522 ERRO
Public bug reported:
wrong warning printed in current code
I added some log and seems we need use ["/v2.0"] instead "/v2.0"
[Wed Sep 07 15:09:40.951167 2016] [:error] [pid 29875] path is /v3, subs is
/v2.0, t is True
[Wed Sep 07 15:09:40.951254 2016] [:error] [pid 29875] The Keystone URL (eithe
Closing as "Won't Fix".
1. No action since 2014
2. Looks like a configuration problem.
** Changed in: glance
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net
Public bug reported:
1. I create port, then router and then use add_router_interface.
2. Then I use remove_router_interface.
3. Port is deleted - and this is unexpected (for me, at least).
I was using Heat on devstack master to test this.
Template for stack with port:
resources:
media_port:
Fixed as part of the api-ref WADL->RST migration
** Changed in: openstack-api-site
Assignee: Manav (manav-kiit) => (unassigned)
** Changed in: glance
Assignee: Manav (manav-kiit) => (unassigned)
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug
Public bug reported:
When cloud-init itself fails to run, as in the case discussed in bug
1621075, an experienced user can detect the problem in the split-second
the console is still alive, but most users are lost.
Could we make it more obvious what the problem we encountered was? I'm
thinking of
Reviewed: https://review.openstack.org/347544
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=47b19ffb54082b9fe1b45e33b05a49a9e1ebc431
Submitter: Jenkins
Branch:master
commit 47b19ffb54082b9fe1b45e33b05a49a9e1ebc431
Author: Sarafraj Singh
Date: Tue Jul 26 15:12:19 2016
Public bug reported:
How to reproduce:
1. Run any VM.
2. Create two networks.
3. Create two ports for each network with same mac addresses
4. Attach those ports to VM
5. Try to detach any interface.
Expected result:
The interface should be detached from VM.
Actual result:
We don't get any error
Public bug reported:
Neutron object does not retrieve keystone domain attribute from request headers.
Neutron policies use context to check rules so we are not able to use domains.
Context is formed from headers in __call__ of NeutronKeystoneContext
object, which initializes Context object.
** A
Public bug reported:
Somehow in the spec process this was overlooked but it is required for
the resource tracker to effectively update allocation.
** Affects: nova
Importance: Undecided
Assignee: Chris Dent (cdent)
Status: New
** Tags: api placement scheduler
--
You receive
I'm not really sure we should gracefully handle configuration issues
where operators did a typo with the PCI whitelist. I mean, most of our
conf opts are needed to be right and not wrong, because if so, Nova
could be trampled, right? So, here, you propose to only strip() the
strings for your usecas
This was fixed as part of the api-ref WADL -> RST migration
** Changed in: glance
Assignee: Charles Bitter (cbitter78) => (unassigned)
** Changed in: glance
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Fixed as part of the api-ref WADL->RST migration, though this is an
ongoing problem that needs to be checked occasionally.
** Changed in: glance
Assignee: Brian Rosmaita (brian-rosmaita) => (unassigned)
** Changed in: glance
Status: Confirmed => Fix Released
--
You received this bug
Public bug reported:
The vmware-nsx repo has a number of different plugins. The DVS plugin enables
one to be able to use Neutron with a number of limitation (no security groups
and no layer 3 support). If one wants to achieve this with the DVS plugin then
there are many different examples that
** Project changed: devstack => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1619466
Title:
Enabling q-lbaasv2 in devstack should add neutron_lbaas.conf to q-svc
command line
You have been subscribed to a public bug:
When q-lbaasv2 is enabled in your devstack local.conf, this implies that
LBaaS v2 is going to be used, and neutron-lbaas's corresponding devstack
plugin.sh script creates a new /etc/neutron/neutron_lbaas.conf file with
come configuration parameters. Howeve
Public bug reported:
In Stable/Mitaka, in Horizon while creating an Instance Network field is
missing when running on port. You can find the screenshots in comments.
** Affects: horizon
Importance: Undecided
Status: New
** Tags: horizon-core
** Attachment added: "port.png"
htt
Reviewed: https://review.openstack.org/366245
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=e84396b5232cb52228bc75dee92429913d72468e
Submitter: Jenkins
Branch:master
commit e84396b5232cb52228bc75dee92429913d72468e
Author: Sean Dague
Date: Tue Sep 6 12:33:46 2016 -040
Public bug reported:
Description
===
When attaching of volumes across Nova/Cinder AZs is forbidden
(cross_az_attach = False in nova.conf) and you try to boot an instance
without specifying an AZ (i.e. you are ok with any of the AZs the
instance will be scheduled to), and block device mapp
Public bug reported:
This is a re-post of an issue that was reported for an older OpenStack
version. Unfortunately, I am confronted with the same problem in
OpenStack Mitaka. Keystone has a proper support for the case, when you
use SSL terminating via HAProxy.
Have a look here:
https://bugzilla.r
API-ref docs merged: https://review.openstack.org/#/c/358344/
CLI docs merged: https://review.openstack.org/#/c/358345/
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
** Also affects: neutron
Importance: Undecided
Status: New
** Description changed:
Currently enable_snat is allowed only when setting a gateway.
$ neutron router-gateway-set --disable-net
$ neutron router-gateway-set --enable-net
There should be provision to set this f
Marking this as Incomplete seeing as how the no progress has been made
on the bug report or on the patch.
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https:
This should have been mitigated by
https://review.openstack.org/#/c/364278/10/neutron/scheduler/l3_agent_scheduler.py@207
so I'm closing this.
** Changed in: neutron
Status: In Progress => Fix Released
** Changed in: neutron
Importance: Undecided => Medium
--
You received this bug not
51 matches
Mail list logo
