Public bug reported:
Steps to Reproduce:
===
1. install openstack-nova-serialproxy
2. On /etc/openstack-dashboard/local_settings set CONSOLE_TYPE = SERIAL
3. On compute node edit /etc/nova/nova.conf set
[serial_console]
enabled=True
Public bug reported:
when fwaas is enabled with dvr router, the firewall rules will only be
added to snat-ROUTER_ID on controller and floating ip namespaces on
compute, this will result that, only south-north traffic can be
controlled by fwaas, and the east-west traffic,which produced from one
Public bug reported:
Launching instance fails when using a volume that is created using a
snapshot of a volume-backended instance.
How to reproduce:
Step 1:
Create an volume backended instance.
root@zheng-dev1:/var/log/nova# nova boot --flavor 1 --boot-volume
Public bug reported:
Now if we create a floating IP, neutron will create a internal port for this
floating IP which is used purely for internal system and admin use when
managing floating IPs, but if a external network with a IPv4 subnet and a IPv6
subnet, then the port for floating IP will
@ Steve Martinelli (stevemar), @Henry Nash (henry-nash),@jiaxi
In UI, I found that, users from one domain are not allowed to be part of the
group of another domain..
Steps followed:
1. Created 2 domains, domain1 and domain2
2. Created users, user1 in domain1 and user2 in domain2.
3. Created
Public bug reported:
In Horizon, I found that, users from one domain are not allowed to be
part of the group of another domain..
Steps followed:
1. Created 2 domains, domain1 and domain2
2. Created users, user1 in domain1 and user2 in domain2.
3. Created groups, group1 in domain1 and group2 in
I was running a private RPM for cisco-networking neutron.
I could not reproduce the problem with stable/juno nor stable/kilo.
** 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:
Steps to reproduce:
Create project
Assign non-admin role to user
As non-admin user Go to Glance and create image
As admin Delete project
As non-admin, cannot delete image
If policy requires as scoped token, even admin cannot delete the image.
This has the effect of
Public bug reported:
The lbaas table actions all use a post() call with a lot of if/then/else
blocks checking the actions. This makes extending this page very
tricky, and does not follow documentation and examples / best practices
of how to implement table actions in a more flexible / extensible
Public bug reported:
Overview:
If when creating a member the user either puts a number as the body or sends
some type of string will cause the server to fall over due to a type error.
How to produce:
curl -X POST http://your-ip:9292/v2/images/your-image-id/members -H
X-Auth-Token:
Public bug reported:
Change 8ff5520713251ec247eeeb783f140d757cbdceb0 deprecated LDAP
Assignment backend, which meant our current Assignment + Resource
backends.
The resource backend must be explicitly deprecated as of Kilo and
removed in Mitaka.
** Affects: keystone
Importance: Medium
Public bug reported:
lbaas is now a plugin and cannot be enabled via enable_service q-lbaas
local.conf sample in horizon needs to be updated.
** Affects: horizon
Importance: Medium
Assignee: David Lyle (david-lyle)
Status: In Progress
** Tags: neutron
--
You received this
** Changed in: os-brick
Status: Fix Committed = Fix Released
** Changed in: os-brick
Milestone: None = 0.3.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1466851
Title:
Public bug reported:
v3 tokens contain the issued_at and expires_at timestamps for each
token. If a token is created on the v2 API and then validated on the v3
API, this timezone information is missing (the 'Z' at the end of the
timestamp), and thus cannot be validated as ISO 8601 extended format
Public bug reported:
Using glance v2, most recent commit is
6dc5477a12b9b904332ac6fe7932abbc7a0275a7.
I see that GET(list image) requests with different invalid parameters
return different response codes. I would expect that invalid parameters
would be treated consistently. In other words I
** Changed in: os-brick
Status: Fix Committed = Fix Released
** Changed in: os-brick
Milestone: None = 0.3.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
I believe this was addressed during Kilo when we refactored FWaaS to
allow FW's to apply per-router.
** Changed in: neutron
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
I have 3 identical machines (host names are different), and I have an
ansible script to deploy horizon. As part of the script we run
collectstatic and compress by hand (offline compression).
Each machine's static contents looks slightly different.
This causes horizon to
Public bug reported:
oslo.utils 2.0.0 entriely removes import oslo.* we need to switch
over. Here's the failure in python27 tests
==
FAIL:
nova.tests.unit.virt.disk.test_api.APITestCase.test_can_resize_need_fs_type_specified
Marking Invalid per comment #19.
** Changed in: neutron
Status: Incomplete = Invalid
** Changed in: neutron
Milestone: liberty-2 = None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Description changed:
File
/home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/openstack_auth/utils.py,
line 24, in module
2015-07-20 18:48:01.107 | from keystoneclient.v2_0 import client as
client_v2
2015-07-20 18:48:01.107 | File
Public bug reported:
File
/home/jenkins/workspace/gate-horizon-python26/.tox/py26/lib/python2.6/site-packages/openstack_auth/utils.py,
line 24, in module
2015-07-20 18:48:01.107 | from keystoneclient.v2_0 import client as
client_v2
2015-07-20 18:48:01.107 | File
The fix referenced in #1 was merged during Kilo, so marking this Fix
Released.
** Changed in: neutron
Status: Confirmed = Fix Released
** Changed in: neutron
Milestone: None = 2015.1.1
** Changed in: neutron
Assignee: (unassigned) = Dane LeBlanc (leblancd)
--
You received this
Public bug reported:
The admin volume types page doesn't display private volume types:
Here is all my volume types
~$ cinder type-list --all
+--+--+-+---+
| ID | Name | Description | Is_Public |
Public bug reported:
Currently using OpenStack Kilo on CentOS 7. Issue is with:
openstack-dashboard-2015.1.0-7.el7.noarch
/usr/share/openstack-dashboard/static/angular/widget.module.js
When using the update_metadata feature in horizon in the flavors and
images section, the meta data table is
Public bug reported:
Now VPN Service is available for Distributed Routers by patch
#https://review.openstack.org/#/c/143203/,
but there is another problem, with DVR, a VM can't use floatingIP and VPN at
the same time.
** Affects: neutron
Importance: Undecided
Status: New
--
Public bug reported:
[Existing problem]
This spec is for adding fowarding rules to Neutron API extension.
There are several use cases to forward packets without considering about
packet
header. For example, in Service Function Chaining(SFC) use cases,
when a transparent network
27 matches
Mail list logo
