Public bug reported:
I was running neutron_lbaas tempest
neutron_lbaas/tests/tempest/v2/scenario/test_healthmonitor_basic.py (
https://github.com/openstack/neutron-
lbaas/tree/master/neutron_lbaas/tests/tempest/v2/scenario )
I stopped the test before when all objects created in order to
Public bug reported:
I was trying update "target_tenant" field in the existing RBAC policy,
The policy is "access_as_external" policy.
On an admin tenant, with an admin user, I created an external network.
This automatically creates and "access_as_external" action RBAC policy
with "*" value
Public bug reported:
On an admin tenant, with an admin user, I created an external network.
This automatically creates and "access_as_external" action RBAC policy
with "*" value for "target_tenant" attribute.
I deleted this RBAC policy and manually create a new one with two
tenants IDs in the
Public bug reported:
When we execute "neutron purge tenantID" on a tenant who has shared its
network, and that network is in use by another tenant, the network will
not be deleted.
When we execute "neutron purge tenantID" on a tenant who has shared its
network, and that network is NOT in use by
Public bug reported:
I executed " neutron purge" command with a non existing tenant ID and
received the following:
neutron purge 25a1c11e26354d7dbb5b204eb1310f33
Purging resources: 100% complete.
The following resources could not be deleted: 1 network
We do not have that tenant ID so the
Public bug reported:
If we have an external network, with default rbac policy, and even 1 tenant is
using this network, we can not delete the default rbac policy in order to
decide to which tenants this network will be exposed.
In this situation the network will be exposed to all tenants unless
Public bug reported:
External network has no qdhcp namespace, when internal network does.
So,
After creating "access_as_external" rbac policy for tenant internal network (
convertes the network to external), the network qdhcp namespace is not removed.
IMHO it should be removed.
Mitaka
**
Public bug reported:
When the internal network have ports in use, a rbac "access_as_external"
policy should not be allowed. We should have an error message explaining
that.
When we execute such an action, the "router:external" for the internal network
becomes "true"
neutron net-show
Public bug reported:
Network update "--router:external" attribute should be blocked if the
network has ports in use ( not including qdhcp port)
When a network with a port attached to a VM turnes to be external, it
can make an opening to issues of qdhcp NS for this network, The VMs on
this
Public bug reported:
If we have 50 tenants and we will want to expose the external network to 49 of
them, we will have to create 49 rbac rules.
IMHO it can be not so comfortable.
I believe we should make an option to exclude specific tenant/tenants
from being targeted by the rbac rule.
May
Public bug reported:
We created external network with admin user for tenantA.
$ neutron net-create admin-ext --provider:network_type=vxlan --router:external
--tenant_id=TENANTA_ID
The rbac policy was created with "*" in target_tenant attribute.
When creatin an external network for specific
tested on Mitaka ^
** Changed in: horizon
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1408237
Title:
Can't connect a
Public bug reported:
Tested ovs 2.5 OVS FW driver.
Could not run sctp traffic between VMs in the same tenant and network
after allowing ip protocol 132 (sctp) ingress and egress traffic in the
security group.
With iptables driver worked well.
Tested on rhel7.3
OSP10- Newton
2016-09-20
Public bug reported:
Newton,
[root@controller-0 ~]# rpm -qa | grep neutron
python-neutron-lib-0.4.0-1.el7ost.noarch
puppet-neutron-9.4.2-1.el7ost.noarch
python-neutron-9.1.0-6.el7ost.noarch
openstack-neutron-ml2-9.1.0-6.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
Public bug reported:
Newton,
openstack-neutron-ml2-9.1.0-6.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch
openstack-neutron-common-9.1.0-6.el7ost.noarch
openstack-neutron-9.1.0-6.el7ost.noarch
[stack@undercloud-0 ~]$
Public bug reported:
[stack@undercloud-0 ~]$ openstack network trunk delete trunk1
Failed to delete trunk with name or ID 'trunk1': Trunk
3b5c8493-7832-4501-a93f-65c5131512bb is currently disabled.
Neutron server returns request_ids: ['req-2ee037a3-6d2f-49fe-babb-cc9a4b2ce9dd']
1 of 1 trunks
Importance: Undecided
Assignee: Alex Stafeyev (astafeye)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Alex Stafeyev (astafeye)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
Seeing the issue again on ocata
** Changed in: neutron
Status: Expired => New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1469498
Title:
LbaasV2 session persistence- Create
Public bug reported:
We believe that each test should not depend on other tests.
python -m testtools.run neutron.tests.tempest.scenario.test_floatingip
Ran 4 tests in 139.164s
OK
python -m testtools.run
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSameNetwork.test_east_west
Public bug reported:
When I run the test (python -m testtools.run)
neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity
with rhel image and "cloud_user" user the test fails due to following :
Traceback (most recent call last):
File
Public bug reported:
Description of problem:
We need to documents that while create sub-port it should be created with
--mac-address PARENT_PORT_MAC_ADDERSS.
This is the correct networking config- on VM subIF and IF should have the same
mac and it is the default option. We need to match
Public bug reported:
Queen
Assiging FIP when there is nor router between the external and internal
networks show " unknown error" instead of
"External network b6093932-a55d-4f9a-8af0-f6f953c3a443 is not reachable from
subnet 535a9a47-6797-454f-a1dc-eeda6ace87d8. Therefore, cannot associate
22 matches
Mail list logo
