Public bug reported:
I have two nodes, one is devstack-152(192.168.1.152) which is controller and
computer node, the other is devstack-167(192.168.1.167) which is computer node
only.
Fist, I starts devstack-152, when it is ready, the data are as follows:
[root@devstack-152 devstack]# nova service-list
+----+------------------+--------------+----------+---------+-------+----------------------------+-----------------+
| Id | Binary | Host | Zone | Status | State |
Updated_at | Disabled Reason |
+----+------------------+--------------+----------+---------+-------+----------------------------+-----------------+
| 6 | nova-conductor | devstack-152 | internal | enabled | up |
2016-08-19T05:48:52.000000 | - |
| 8 | nova-scheduler | devstack-152 | internal | enabled | up |
2016-08-19T05:48:57.000000 | - |
| 9 | nova-consoleauth | devstack-152 | internal | enabled | up |
2016-08-19T05:48:53.000000 | - |
| 10 | nova-compute | devstack-152 | nova | enabled | up |
2016-08-19T05:48:57.000000 | - |
| 11 | nova-compute | devstack-167 | nova | enabled | up |
2016-08-19T05:48:56.000000 | - |
+----+------------------+--------------+----------+---------+-------+----------------------------+-----------------+
[root@devstack-152 devstack]# neutron port-list
+--------------------------------------+------+-------------------+--------------------------------------------------+
| id | name | mac_address | fixed_ips
|
+--------------------------------------+------+-------------------+--------------------------------------------------+
| 57498ca8-a9a3-4fc2-b08c-339f8fcf4c21 | | fa:16:3e:62:c7:38 |
{"subnet_id": "8176d1ef- |
| | | |
6e68-4b5d-a475-ebc015e14106", "ip_address": |
| | | |
"fd8a:5f:b56b::1"} |
| 8541b3a4-8cc2-41c4-af11-27f581f044af | | fa:16:3e:2f:6a:4b |
{"subnet_id": "1d32f1ca-3805-494d- |
| | | |
ab25-f8a8c96804c5", "ip_address": "10.0.0.1"} |
| 9b334b65-c631-44bf-8338-02b0e3e63444 | | fa:16:3e:43:b6:89 |
{"subnet_id": |
| | | |
"51db7655-51c4-468c-8452-c2bbada20c86", |
| | | |
"ip_address": "172.24.4.4"} |
| | | |
{"subnet_id": "25a70542-a098-4b6d-989f- |
| | | |
b20f5cacd0d0", "ip_address": "2001:db8::c"} |
+--------------------------------------+------+-------------------+--------------------------------------------------[root@devstack-152
devstack]# ovn-nbctl list logical_switch_port
_uuid : b75e9e58-4ab0-42e8-994c-6fc0c1c344dd
addresses : ["fa:16:3e:2f:6a:4b 10.0.0.1"]
dhcpv4_options : 30428d9c-678c-4c1d-b762-45b3e4617237
dhcpv6_options : []
dynamic_addresses : []
enabled : true
external_ids : {"neutron:port_name"=""}
name : "8541b3a4-8cc2-41c4-af11-27f581f044af"
options : {router-port="lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"}
parent_name : []
port_security : []
tag : []
type : router
up : true
_uuid : 1d825431-83c5-456a-a6d9-2257afddc9cb
addresses : ["fa:16:3e:43:b6:89 172.24.4.4 2001:db8::c"]
dhcpv4_options : []
dhcpv6_options : []
dynamic_addresses : []
enabled : true
external_ids : {"neutron:port_name"=""}
name : "9b334b65-c631-44bf-8338-02b0e3e63444"
options : {}
parent_name : []
port_security : []
tag : []
type : ""
up : false
_uuid : 0076f185-3789-47bf-95ac-a742195596d2
addresses : ["fa:16:3e:62:c7:38 fd8a:5f:b56b::1"]
dhcpv4_options : []
dhcpv6_options : []
dynamic_addresses : []
enabled : true
external_ids : {"neutron:port_name"=""}
name : "57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
options : {router-port="lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"}
parent_name : []
port_security : []
tag : []
type : router
up : true
[root@devstack-152 ~]# ovs-vsctl show
a9a63a12-af0c-420d-a847-ebb6fd62a1ea
Bridge br-int
fail_mode: secure
Port
"patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
Interface
"patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
type: patch
options:
{peer="patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"}
Port
"patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"
Interface
"patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"
type: patch
options:
{peer="patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"}
Port br-int
Interface br-int
type: internal
Port
"patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
Interface
"patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
type: patch
options:
{peer="patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"}
Port
"patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"
Interface
"patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"
type: patch
options:
{peer="patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"}
Then, I starts devstack-167, data in devstack-152 is changed
[root@devstack-152 ~]# ovs-vsctl show
a9a63a12-af0c-420d-a847-ebb6fd62a1ea
Bridge br-int
fail_mode: secure
Port br-int
Interface br-int
type: internal
Port "ovn-87892d-0"
Interface "ovn-87892d-0"
type: geneve
options: {csum="true", key=flow, remote_ip="10.43.166.167"}
But devstack-167 data is correct
[root@devstack-167 logs]# ovs-vsctl show
0dbad5c3-c326-4d59-b295-1e8ee6d6bfac
Bridge br-int
fail_mode: secure
Port
"patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"
Interface
"patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"
type: patch
options:
{peer="patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"}
Port
"patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
Interface
"patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
type: patch
options:
{peer="patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"}
Port
"patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
Interface
"patch-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"
type: patch
options:
{peer="patch-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21-to-lrp-57498ca8-a9a3-4fc2-b08c-339f8fcf4c21"}
Port
"patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"
Interface
"patch-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af-to-8541b3a4-8cc2-41c4-af11-27f581f044af"
type: patch
options:
{peer="patch-8541b3a4-8cc2-41c4-af11-27f581f044af-to-lrp-8541b3a4-8cc2-41c4-af11-27f581f044af"}
Port br-int
Interface br-int
type: internal
Port "ovn-2b2d12-0"
Interface "ovn-2b2d12-0"
type: geneve
options: {csum="true", key=flow, remote_ip="192.168.1.152"}
** Affects: openvswitch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1614837
Title:
ovn:Multi nodes devstack, controller node losts ovs port when computer
node starts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1614837/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
