Just verified after add the following configuration in keystone.conf we
can solve this problem.
admin_project_domain_name = default
admin_project_name = admin
Thanks Rabi.
** Changed in: keystone
Status: New => Invalid
** Changed in: heat
Status: New => Invalid
--
You received t
** Also affects: heat
Importance: Undecided
Status: New
--
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/1644041
Title:
heat_stack_owner users could see and
Public bug reported:
In a newton deployment we found that a heat_stack_ower user can delete a
heat stack from other projects
For example, we have two domain domain1 and domain2. In domain1 we have
project: project_domain1 which has user:user1, in domain2 we have a
project:project_domain2 which ha
Public bug reported:
In a newton deployment we found that a heat_stack_ower user can delete a
heat stack from other projects
For example, we have two domain domain1 and domain2. In domain1 we have
project: project_domain1 which has user:user1, in domain2 we have a
project:project_domain2 which ha
Public bug reported:
In a newton deployment we found that a heat_stack_ower user can delete a
heat stack from other projects
For example, we have two domain domain1 and domain2. In domain1 we have
project: project_domain1 which has user:user1, in domain2 we have a
project:project_domain2 which ha
Public bug reported:
We have deploymented an OpenStack cloud with newton release code. In
horizon we found that even the member user could see the admin tab in
horizon.
Admin tab should only been seen by the admin user in the cloud. And in
mitaka we even have the limit that only cloud admin could
313
https://github.com/openstack/neutron/blob/stable/newton/neutron/db/dns_db.py#L275
https://github.com/openstack/neutron/blob/stable/newton/neutron/db/dns_db.py#L281
from
https://github.com/openstack/neutron/blob/stable/newton/neutron/db/l3_db.py#L1041
we can see that port_id is actually the &q
** Project changed: neutron => octavia
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1611509
Title:
lbaasv2 doesn't support "https" keystone endpoint
Status in octavia:
New
Bug desc
ty straight forward just
configure keystone https endpoint in your devstack and enable lbaasv2 and
octavia then run the following command
```
neutron lbaas-loadbalancer-create --name lb1 test-subnet
```
** Affects: neutron
Importance: Undecided
Assignee: Hao Chen (chenh1987)
Status: New
**
Public bug reported:
I have a mitaka openstack deployment with neutron DVR enabled. When I
try to test the snat HA failover I found that even though the snat
namespace was created on the other backup node, it doesn't has any nat
rule in snat namespace iptable. And run "ip a" in the sant namespace
** This bug is no longer a duplicate of bug 1420104
quota set failed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1479981
Title:
Openstackclient return wrong quota information
Stat
*** This bug is a duplicate of bug 1420104 ***
https://bugs.launchpad.net/bugs/1420104
This is not the same issue as bug #1420104. There are two main
differents:
1. Quota set can't change the port limitations. In fact ```openstack quota
set``` command can only change nova quota limitation, i
Public bug reported:
I try to update the quota port limitations for my project, neutronclient
works well and I can get the right result using neutronclient. But when
we run ```openstack quota show admin``` we found the quota port
limitation doesn't changed. Here are the testing process:
layton
13 matches
Mail list logo
