Public bug reported:
>From https://bugs.launchpad.net/neutron/+bug/2018529
Community had raised a fix in A release. But nova can still attach the
vip port on VM without failure, even the vip port can not be used..
We can repro it in Neutron A release and OVN based deployment, relied on
Public bug reported:
Hi team,
according to the latest annoucement of
https://github.com/tomaszmrugalski/dibbler,
seems the said project is concluded by lacking maintainers,
and I also found the said tools have been as the Ipv6 dhcp default
implementation.
The author suggest
Public bug reported:
Currentlly, Neutron FIP just support NAT v4 to v4. But the ipv6 is the
future, we must face it sooner or later.
I check the old related RFE and BPs[1], seems many customers or
developers want it.
In our country, goverment push to use ipv6 internally, so we can quickly
move
Public bug reported:
Version
=
Openstack neutron Ocata
Issue Description
=
Currently, the default behavior of Neutron will store the segment in compute
nodes level, so the port binding process can know exactly which network plane
it can reach on some specific compute nodes. But
Public bug reported:
Currently, the AWS VPC is a common concept for cloud providers, but for
openstack models, we treat it as a Neutron Router.
So the VPC peering support corresponds to something like "Router
peering" support. This function provides the network connecting between
different
/ovs_neutron_agent.py#n1564
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Tags: ovs
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
** Tags added: ovs
--
You received this bug notification because you are a member of Ya
Public bug reported:
Current openvswitch agent need to be stronger for more cases.
Please see [1]
This line will clean up all stale ovs flows. Try to think, if there is a
case, when the ovs agent restart and try to get its hold device info(rpc
to server get them and store into local cache if
Thank you.
You mentioned that create 1K "free" port, just db records, right?
If that, I don't think the policy engine or md driver would be the issue.
As the port delete is a very complex operation. Every step(l3 pre-check,
callbacks, port pre/postcommit to md drivers, delete the port record in
Public bug reported:
Currently, we support VM port/router port to apply fwg. So we deep into
L2 and L3 agent implementation to process the associated port for fwg.
For this bug, I will raise an example:
Server side set fwg status
Neutron doesn't set the protocol as a Interger value, it be stored as
varchar in db.
** Changed in: neutron
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
Public bug reported:
repro
neutron security-group-rule-create test --direction ingress --protocol 115
--port-range-min 22 --port-range-max 22
Request Failed: internal server error while processing your request.
This will raise 500 internal error.
Log
ERROR
Public bug reported:
Issue
---
For site to site type VPN, we need to limit the bandwidth of the VPN services,
as the VPN tunnel will cost the bandwidth from the outside public bandwidth
provided by the ISP or other organizations.That means it is not free. The
openstack provider or users
these infos into the network_infocache, it is hard to query instance
like this.
Proposal
* Support list/get floatingip show the related ports' device_id
* Adding regex matching support in DB layer using "LIKE" SQL phrase.
** Affects: neutron
Importance: Undecided
Assign
Public bug reported:
In real data center, it may contains several external gateways to access
external network. The VM instances can access all of them in L3 layer.
Each gateway may from different network providers, and different network
performance(such as stability, bandwidth, speed). Cloud
Public bug reported:
We use public IP address on SNAT/VPN service/DNAT. As now SNAT/VPN need
to support rate limit for access external network or the connection
cross openstack. I think [1] will meet this requirements. DNAT/port
forwarding[2] also need the Qos for the same reason which is saving
Public bug reported:
Nova contains 3 stages when process 1ive migration:
1. pre_live_migration
2. migrating
3. post_live_migration
The current implement, nova will plug a new vif on the target host. The
ovs-agent on the target host will process this new vif, and try to up this port
on target
Public bug reported:
Repro:
1. create a net and a subnet 'A-compute-nova' with service_types "compute:nova"
2. exec neutron port-create only specified the network ID/name.
This will return "No valid service subnet for the given device owner."
We only can create port with device_owner
port to other way, and
subport check to let user know the port is used by a trunk.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notificat
to VM2. I don't think this is a valid case.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Ya
Public bug reported:
Our in-tree openvswitch agent now process the port as a serial way. This
may cause some delay operation and even effect the whole work, such as
the real vm startup..
Could we let l2 agent process more quickly or make it process the port
in concurrent mode? And I know some
Public bug reported:
There are 3 sample fw_rules in server. And I expect the order is tcp - ping -
denyany
openstack firewall group rule list
+--+-+-++
| ID |
Public bug reported:
Background:
We need a stable and functional public cloud. It means users could launch VM
and call openstack API as they want.
So we need the server more strong and strong error-tolerance.
Scenario:
1. Neutron agent report its status through rpc to server side.
2. Alright,
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/b
/utils.py", line 43, in
get_and_validate_sort_keys
2017-01-25 09:42:59.830 TRACE neutron.api.v2.resource ^[[01;35m^[[00mif
isinstance(sort_key_attr.property,
2017-01-25 09:42:59.830 TRACE neutron.api.v2.resource
^[[01;35m^[[00mAttributeError: 'AssociationProxy' object has no attribute
sync.clear(dest,
self.mapper, self.prop.synchronize_pairs)
2017-01-16 16:01:20.220 TRACE neutron.api.v2.resource File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/sync.py", line 74, in
clear
2017-01-16 16:01:20.220 TRACE neutron.api.v2.resource (r,
orm_util.state_st
is powerful.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Tags: lbaas
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
** Tags added: lbaas
--
You received this bug notification because you are a member of Ya
Public bug reported:
Currently, neutron lbaas and octavia just support connection_limit, but not
bandwidth_limit. We need support it to make LB more powerful.
If no bandwidth_limit, the upstream bottleneck of vip will issue the low speed
in the public cloud, eventhough the backend server is
Public bug reported:
Currently, neutron-lbaas or octavia implemented the haproxy just support
TCP,HTTP,HTTPS,TERMINATED_HTTPS.
We need support udp if we want the data flow lb towards this kind protocol or
requirements.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo
I to query
the time of the rule work, set the period.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Tags: fwaas
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
** Tags added: fwaas
--
You received this bug n
I to query the
details of them.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Tags: fwaas
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
** Tags added: fwaas
--
You received this bug notification because you
",
"protocol": "tcp",
"source_ip_address": "1::23",
"ip_version": 6
}
}
OK, the firewall_rule will be created successful.
Then I update it like :
{
"firewall_rule": {
"source_ip_address":
.v2.resource context)
2017-01-05 11:59:26.592 TRACE neutron.api.v2.resource File
"/opt/stack/neutron/neutron/db/common_db_mixin.py", line 156, in
_apply_filters_to_query
2017-01-05 11:59:26.592 TRACE neutron.api.v2.resource query =
query.filter(column.in_(value))
201
object has no attribute '__getitem__'
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
En
Public bug reported:
Currently, neutron-lbaas had implemented "lb_network_vip" extension in
server side[1]. We can use restAPI the call the new feature. But
neutronclient didn't support[2], and this patch[2] is not alive for some
months.
The related RFE of "lb_network_vip":
p": true,
"tenant_id": "88ecb8bb6abb4207bb9a832e08eef245",
"ports": [
"2c6b1bcf-a1d6-4efa-8c7a-b7f0966aa3d1"
],
"project_id": "88ecb8bb6abb4207bb9a832e08eef245",
"public": false,
"egress_fire
/opt/stack/neutron-fwaas/neutron_fwaas/extensions/firewall.py", line 204, in
convert_action_to_case_insensitive
2016-12-14 10:00:14.982 TRACE neutron.api.v2.resource return value.lower()
2016-12-14 10:00:14.982 TRACE neutron.api.v2.resource AttributeError: 'int'
object has no attribute 'lo
net-create --provider:physical_network vlan_net
--provider:network_type vlan net-name
All cmds return exception NoNetworkAvailable, this is not frendly, we
should tell users how to use the configured physical network, what they
can do in the next.
** Affects: neutron
Importance: Undecided
Assignee: zhaob
ct them with some worthly parameter name.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
I use the default devstack configuration with l2pop. Then I use trunk
plugin to create trunk port and set some subport in it.
1.The parent port create from vxlan net A, and there is a subport from the same
net A.
2.Boot an vm with this trunk port on an specifyed compute
d before
assignment
2016-10-17 19:38:52.764 TRACE oslo_messaging.rpc.server ^[[01;35m^[[00m
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
9
-3a7b-48a1-a16c-bf9f7b2751a5'}, {'port_id': u'fa690dcc-
71eb-4154--', 'firewall_group_id': u'2932b3d9-3a7b-48a1
-a16c-bf9f7b2751a5'})]
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: In Progress
--
You received this bug notification bec
** 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://bugs.launchpad.net/bugs/1633385
Title:
fwaas v2 installation with devstack set the wrong plugin class
=
neutron_fwaas.services.firewall.fwaas_plugin:FirewallPlugin
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: In Progress
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Ya
_validate_subnet_service_types
2016-10-13 17:44:27.842 TRACE neutron.api.v2.resource not
service_type.startswith(tuple(prefixes))):
2016-10-13 17:44:27.842 TRACE neutron.api.v2.resource AttributeError: 'int'
object has no attribute 'startswith'
2016-10-13 17:44:27.842 TRACE neutron.api.v2.
** No longer affects: designate
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1588171
Title:
Should update nova api version to 2.1
Status in Ceilometer:
In Progress
Status in
** Also affects: designate
Importance: Undecided
Status: 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/1588171
Title:
Should update nova api version to 2.1
Status in
duplicate bug..:(
** Changed in: neutron
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/1588170
Title:
Should update nova api version to 2.1
Status in
** Changed in: cinder
Assignee: (unassigned) => zhaobo (zhaobo6)
** Also affects: octavia
Importance: Undecided
Status: New
** Changed in: octavia
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
Engin
Public bug reported:
As nova api had abandoned 2.0, and suggest to use v2.1 if we call nova.
So should update the version from 2.0 to 2.1
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
)
Status: New
** Affects: cinder
Importance: Undecided
Status: New
** Affects: heat
Importance: Undecided
Status: New
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Affects: searchlight
Importance: Undecided
k it if return "ovs_hybrid_plug": false" /"true"
to nova.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug not
. And it will be recreated in the end, this view is
meaningless and risky.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because
/250993/
[2]https://github.com/openstack/nova/blob/12.0.0/nova/network/neutronv2/api.py#L1178
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this
** Changed in: neutron
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/1468235
Title:
Create port exceed max_fixed_ips_per_port limit when contains multiple
"standardattrs". Now the db_models which has standard_attr are neutron
core resource and extension resource. We should add them either.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zh
when update
subnetpool. So should add the same logic like other core resources
towards dict maker.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this
network shared or maybe more cover.
[What is the enhancement?]
Share FW more sophisticated to other specified tenants
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
is an normal thing.
[Proposal]
Now vpn didn't contain the 'shared' field, so we should extend it and fulfill
the function of share to specified tenants based on rbac policies.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
the server
side didn't process this field.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) => zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
Engineer
reconfigure sharing settings for network
a80d09eb-9ef2-47a4-baac-90133894366a. Multiple tenants are using it.
2015-11-19 10:05:43.024 TRACE neutron.callbacks.manager
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
A
ager InvalidSharedSetting:
Unable to reconfigure sharing settings for network
d207350c-6d19-45fc-a3a4-2c70bf35a933. Multiple tenants are using it.
2015-11-19 02:46:57.687 TRACE neutron.callbacks.manager
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status:
to lbaas's resources which is
related with neutron core resources.
So should add the new appended attributes to
neutron_lbaas/services/loadbalancer/data_models.py which import
models_v2 from neutron.db .
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
|
+--+--+--+
repro:
run neutron net-list -F abc
it returned:
++
||
++
++
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) = zhaobo (zhaobo6)
--
You received this bug notification because you
default_prefixlen is always 8.And this may make user to input
cidr which the prefixlen is 8.
I think when use the subnetpool to create subnet, it should get one of pool and
cannot limit according to the default prefixlen.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6
|
+---+--+
So the subnetpool should not allow this special type of cidrs to be
created.
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee
'] [parameters: (u'd7c270ef-2a37-413f-99a3-8299aa96dc01',)]
2015-07-31 11:20:50.337 TRACE neutron.api.v2.resource
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6)
Status: New
** Description changed:
When exist a port which used by loadbalancer vip, and now
Assignee: zhaobo (zhaobo6)
Status: New
** Changed in: neutron
Assignee: (unassigned) = zhaobo (zhaobo6)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1477889
Title:
fixed
subnets
with slaac. The num of fixed ip exceed the limit of
max_fixed_ips_per_port which I had configured in neutron.conf.
According to the scene, max_fixed_ips_per_port didn't limite the fixed
ip num .
** Affects: neutron
Importance: Undecided
Assignee: zhaobo (zhaobo6
Public bug reported:
neutron --version
2.6.0
When a network named 'A' contains a ipv4 subnet and a ipv6 subnet. I
specify the ipv4 subnet without ipv4 addr to create a port based on this
network 'A'. The returned port contains 2 addresses (both ipv4 and
ipv6).
It just like:
| fixed_ips
: zhaobo (zhaobo6)
Status: New
** Changed in: nova
Assignee: (unassigned) = zhaobo (zhaobo6)
--
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/1460630
Title:
nova
70 matches
Mail list logo
