NEUTRON's OVS based VXLAN seems to be unable to access the network

Bug #2063989 reported by sam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned
Ubuntu
New
Undecided
Unassigned

Bug Description

I found that the cloud host I created cannot connect to the network. The network type is VXLAN, and it cannot even access cloud init
I used this installation document (partially in Chinese) and it was normal around 2022, but it cannot be used after updating the software source recently.

The use of VXLAN in cloud hosts has the following faults
(1) Unable to access network resources other than ICMP (ping), and even curl http://169.254.169.254 (This also leads to the inability to use cloud init)
(2) Sometimes unable to ping 169.254.169.254 for unknown reasons.

All firewalls and security groups are allowed or closed.

My network situation is as follows
Internal (vxlan) 10.0.0.0/24 Gateway 10.0.0.1
Router gateway 10.0.0.1 → 192.168.10.121
External (flat) 192.168.10.11.0/24 Gateway 192.168.10.1.1

If any other information is needed, I can provide it and hope to fix this error.

system version:ubuntu 22.04 last version (online )
openstack Y version

此错误跟踪器用于文档中的错误,请使用以下内容作为模板,并根据需要删除或添加字段。将 [ ] 转换为 [x] 以复选框:
- [ ] 这个文档是这样不准确的: ______
- [X ] 这是一个文档添加请求。
- [ ] 我对文档进行了修复,可以粘贴到下面,包括示例:输入和输出。

如果您有疑难解答或支持问题,请使用以下资源:

- 邮件列表:https://lists.openstack.org
 - IRC:OFTC上的“openstack”频道

-----------------------------------
发布:20.5.1.dev23 于 2022-03-01 21:07:17
SHA: 34e97943a8190a33d72458ce39aaa5f82e0855b9
来源: https://opendev.org/openstack/neutron/src/doc/source/install/
URL: https://docs.openstack.org/neutron/yoga/install/

Tags: doc
Revision history for this message
sam (sam22926) wrote :
Revision history for this message
sam (sam22926) wrote :

at cloud host (vxlan) cmd

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

This don't looks like Neutron bug really and more like some misconfiguration or something like that. If You can't reach metadata service from Your instance, please check if haproxy service for metadata was spawned in the router namespace. You need also to check e.g. with tcpdump where your connection is stopped. That may give you some clue what and where is wrong.

I am closing this as not a bug in Neutron and recommend You to go the the <email address hidden> mailing list to get support there.

Changed in neutron:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.