This doesn't seem like a neutron bug.
** Also affects: devstack
Importance: Undecided
Status: New
** No longer affects: devstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1
Not a neutron bug. I changed it to designate.
** Project changed: neutron => 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/1918653
Title:
Designate DNS – create TLD using val
A similar bug: https://bugs.launchpad.net/neutron/+bug/1903531
As discussed above, there is known issue on upgrading from 15.3.0 to
15.3.2. It seems you were hitting that issue. However, based on
discussion on https://bugs.launchpad.net/neutron/+bug/1903531, this
issue won't be fixed.
Quoted from
** Changed in: neutron
Status: Incomplete => 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/1869136
Title:
Use public flat network to create vm faild
Status in neutron:
I don't think neutron will change the way to implement the OVS hybrid.
You can try the OVS firewall as @Yulong suggested.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutr
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Status: New => Confirmed
** Changed in: python-neutronclient
Importance: Undecided => Critical
** Changed in: neutron
Status: New => Invalid
--
You received th
I think "close by default" is the general practice in OpenStack, mainly
for security reasons. I personally don't think it is a good idea to
change that, but I marked this bug as "Opinion" so others can weight in
this proposal.
** Tags added: fwaas
** Changed in: neutron
Status: New => Opin
As comment #1 suggested, this bug is fixed and I am going to close this
ticket, but feel free to re-open it if needed.
** 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.
h
I am going to close this bug, but please feel free to re-open it if
comment #3 doesn't address your concern.
** 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://bug
Hi @Realtime,
It seems the document below is what you need:
https://docs.openstack.org/install-guide/launch-instance-networks-
provider.html
I am going to proceed to close this bug but please feel free to re-open
it if it still has problems.
** Changed in: neutron
Status: New => Invalid
I don't think this is a neutron bug. The error happened only in the case
that the fake query class is used in unit tests. It should be resolved
once the testing code is updated.
See if this patch fixes your issue:
https://review.openstack.org/#/c/629922/
** Changed in: neutron
Status: New
tance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Tags: rfe
** Tags added: rfe
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whic
openstack.org/68/424468/34/check/neutron-fullstack/4422e70/logs/testr_results.html.gz
http://logs.openstack.org/08/620708/2/check/neutron-fullstack/51099db/logs/testr_results.html.gz
http://logs.openstack.org/09/608909/24/check/neutron-fullstack/2891c09/logs/testr_results.html.gz
http://logs
This happened again: http://logs.openstack.org/26/615126/5/check
/tempest-full/69d913a/job-output.txt.gz#_2018-11-06_19_51_54_083047
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
200 OK
IMHO, neutron should be strict between '-' and '_'. For example, the
second and third commands above should fail or we should update the API
documentation about that.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status:
Still happening: http://logs.openstack.org/88/555088/29/check/neutron-
functional/0b00b31/job-output.txt.gz#_2018-10-25_22_18_28_107639
** Changed in: neutron
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Public bug reported:
Job: any tempest plugin scenario jobs
Failed test:
neutron_tempest_plugin.scenario.test_floatingip.FloatingIPPortDetailsTest.test_floatingip_port_details
Sample failure:
http://logs.openstack.org/36/610536/1/check/neutron-tempest-plugin-scenario-linuxbridge/dbac8ec/job-outpu
Public bug reported:
Job: neutron-fullstack-*
Failed test:
neutron.tests.fullstack.test_dhcp_agent.TestDhcpAgentHA.test_reschedule_network_on_new_agent(Linux
bridge agent)
Sample failure:
http://logs.openstack.org/88/555088/29/gate/neutron-fullstack-python36/34299ab/job-output.txt.gz
{0}
neut
Public bug reported:
* Job: neutron-tempest-iptables_hybrid
* Failed test:
tempest.api.compute.servers.test_servers_negative.ServersNegativeTestJSON.test_shelve_shelved_server
* Example of failure:
http://logs.openstack.org/80/610280/8/check/neutron-tempest-iptables_hybrid/caa373a/job-output.txt
Public bug reported:
* Job: neutron-fullstack-python36
* Failed tests: test_create_one_default_qos_policy_per_project,
test_create_two_default_qos_policies_per_project, test_update_default_status,
test_update_default_status_conflict
* Example failure:
http://logs.openstack.org/80/610280/8/check
:%(tenant_id)s as the parent resource: tenant was not found.
Neutron server returns request_ids: ['req-55c56d3f-246c-486c-8763-8b27248fef09']
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: In Progress
** Description changed:
Use the sam
I am going to mark this bug as "invalid" because it doesn't seem to be a
neutron 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/17
FYI, this bug is forwarded to openstacksdk:
https://storyboard.openstack.org/#!/story/2003517
** Also affects: python-openstacksdk
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron
I am going to mark this bug as "invalid" since it doesn't seem to be a
neutron 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/1788
#x27; expected to update 1 row(s); 0 were
matched.
Aug 14 20:27:13.557743 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: ERROR neutron.api.v2.resource
Aug 14 20:27:13.561375 ubuntu-xenial-inap-mtl01-0001325098
neutron-server[25320]: INFO neutron.wsgi [None
req-d0268850-9176-4fad-a
ould be:
iptables =
neutron.services.metering.drivers.iptables.iptables_driver:IptablesMeteringDriver
This cause the metering agent unable to load iptables driver via alias.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: In Progress
--
You received this bug notification because you are a member o
By referring to the multiple ipv6 prefixes spec [1], it is intentional
to include all the stateless IPv6 addresses into the port. The current
implementation seems to be correct. In addition, you can look at this
bug [2], in which people was complaining that neutron was not picking
all the SLAAC add
2018 20:43:22 GMT
{"NeutronError": {"message": "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
** Affects: neutron
Importance: Undecided
Assig
cation/json" -H "X-Auth-Token: $TOKEN"
{"NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
** Affects: neut
NeutronError": {"message": "Request Failed: internal server error while
processing your request.", "type": "HTTPInternalServerError", "detail": ""}}
This is the trace in neutron server log:
http://paste.openstack.org/show/720318/
*
enial-ovh-gra1-0003676293 neutron-server[10199]:
ERROR neutron.service File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/orm/relationships.py", line
2103, in _determine_joins
Apr 23 10:02:01.271736 ubuntu-xenial-ovh-gra1-0003676293 neutron-server[10199]:
ERROR neutron.service
e_up":true,"tenant_id":"a7a7fa10fd7a4c80acb7e4b224480495","created_at":"2018-03-19T19:17:07Z","mtu":1500},{"ipv6_address_scope":null,"dns_domain":"","revision_number":4,"port_security_enabled":true,&quo
40-4225-9dab-729338107d1a",
"description": null
},
{
"name": null,
"network_id": "ad93b454-4836-46c7-bfc8-64a20a2ab95a",
"segmentation_id": null,
"network_type": "flat",
"ph
Public bug reported:
Right now, it seems it is impossible to list resources with a filter
that contains null value. For example, it is impossible to list subnets
that doesn't have subnetpool. I tried the following, but it doesn't seem
to work (it returned an empty list instead of the filtered list
Public bug reported:
This RFE is created according to the feedback of the neutron driver team
meeting [1].
@yamamoto suggested to introduce a new API /ip-address/{ip-address}.
This API will determine whether the {ip-address} is fixed and floating
and then respond with the relevant data, including
Public bug reported:
The response of segment resource doesn't contain standard attributes,
i.e. created_at, updated_at, revision_number. These attributes should be
visible in the response as other resources.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongb
Public bug reported:
There is an address scope API extension defined in neutron-lib
https://github.com/openstack/neutron-
lib/blob/master/neutron_lib/api/definitions/address_scope.py , but its
documentation seems to be missing in API reference.
** Affects: neutron
Importance: Undecided
works?limit=1&marker=xxx"
{"NeutronError": {"message": "Network xxx could not be found.", "type":
"NetworkNotFound", "detail": ""}}
[8] GET "/v2.0/networks?marker=xxx"
{"networks":...}
[9] GET &qu
ol_id=null"
IMHO, we need to add support for that. Otherwise, the filtering feature
is incomplete.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You
t;: "HTTPInternalServerError",
"detail": ""}}
IMO, the neutron server should return a 4xx error in this case.
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned)
s-detailed
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
** Description changed:
The api-ref describe how the pagination works in general:
https://developer.
Public bug reported:
In the api-ref, the parameter 'tags' is not documented in either
response parameters or response sample. This applies to all API
resources that support tags (i.e. network, subnet). It is better to add
this missing documentation.
** Affects: neutron
Importance: Undecided
ow to specify each filter value.
If the filters documentation is missing or incomplete, it is hard to
predict the API behavior which will cause issue like:
https://bugs.launchpad.net/neutron/+bug/1418635 .
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
S
_dir=desc&sort_key=xxx'
HTTP/1.1 400 Bad Request
Content-Length: 116
Content-Type: application/json
X-Openstack-Request-Id: req-a2b43d49-f16a-40ae-ba76-51d2162cb72b
Date: Mon, 05 Feb 2018 23:18:45 GMT
{"NeutronError": {"message": "[u'xxx'] is i
d for
relationships. For a simple many-to-one, use in_() against the set of
foreign key values.", "type": "NotImplementedError", "detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
**
t;: "Request Failed: internal server error
while processing your request.", "type": "HTTPInternalServerError",
"detail": ""}}
** Affects: neutron
Importance: Undecided
Assignee: Hongbin Lu (hongbin.lu)
Status: New
** Changed in: neut
Public bug reported:
It looks neutron still use the legacy jobs syntax. This bug suggested to
migrate to zuul v3 syntax. See comment from Andreas Jaeger at
https://review.openstack.org/#/c/511983/35 (Patch Set 35).
** Affects: neutron
Importance: Undecided
Status: New
--
You recei
10fe181f11e), Invalid
input for operation: Requested MTU is too big, maximum is 1450.
The failure on deletion is strange. IMHO, we should either validate the
mtu on network create/update, or allow the deletion regardless of the
mtu value.
** Affects: neutron
Importance: Undecided
** Also affects: neutron
Importance: Undecided
Status: New
** Changed in: neutron
Assignee: (unassigned) => Hongbin Lu (hongbin.lu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
49 matches
Mail list logo
