haproxy doesnt run after the vrouter agent restart

Bug #1750354 reported by Venkatesh Velpula
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R4.0
New
High
Manish Singh
R4.1
New
High
Manish Singh
R5.0
Fix Released
High
Hari Prasad Killi
Trunk
Fix Released
High
Hari Prasad Killi

Bug Description

Build-id :4.0.3.0-157
build type :continuous build
DISTRO :U16.04.2 LTS (Xenial Xerus)
SKU :Ocata

Setup
===================================================
K8s with single Master and two nodes

====================================================

Before the vrouter agent restart
=================================
root@testbed-1-vm2(agent):/# contrail-status
== Contrail vRouter ==
contrail-vrouter-agent: active
contrail-vrouter-nodemgr: active

root@testbed-1-vm2(agent):/# ps -aux | grep haproxy
haproxy 10544 0.0 0.0 43760 2992 ? Ss 16:10 0:00 haproxy -f /var/lib/contrail/loadbalancer/haproxy/2d714eca-1561-11e8-8eef-525400010001/haproxy.conf -p /var/lib/contrail/loadbalancer/haproxy/2d714eca-1561-11e8-8eef-525400010001/haproxy.pid -sf 10534
root 10640 0.0 0.0 11284 960 ? S+ 16:11 0:00 grep --color=auto haproxy
root@testbed-1-vm2(agent):/# vi /var/lib/contrail/loadbalancer/haproxy/2d714eca-1561-11e8-8eef-525400010001/haproxy.conf
root@testbed-1-vm2(agent):/#
root@testbed-1-vm2(agent):/#

After the vrouter-agent restart
=================================
oot@testbed-1-vm2(agent):/# contrail-status
== Contrail vRouter ==
contrail-vrouter-agent: active
contrail-vrouter-nodemgr: active

root@testbed-1-vm2(agent):/# ps -aux | grep haproxy
root 10930 0.0 0.0 11284 936 ? S+ 16:14 0:00 grep --color=auto haproxy
root@testbed-1-vm2(agent):/#

contrail_version_testbed-1-vm2_agent.log
root@testbed-1-vm2(agent):/# tail -f /var/log/contrail
contrail/ contrail.log contrail_version_testbed-1-vm2_agent.log
root@testbed-1-vm2(agent):/# tail -f /var/log/contrail/contrail-vrouter-agent.log
2018-02-19 Mon 16:13:48:368.560 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028367316 [SYS_NOTICE]: SandeshModuleClientTrace: data= [ name = testbed-1-vm2:Compute:contrail-vrouter-agent:0 client_info= [ status = Disconnect successful_connections = 0 pid = 10774 http_port = 8085 start_time = 1519037028366031 collector_name = collector_ip = 0.0.0.0:0 collector_list= [ [ ] ] rx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] tx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] ] msg_type_diff= [ [ _iter107->first = SandeshModuleClientTrace [ messages_sent = 0 messages_sent_dropped_no_queue = 0 messages_sent_dropped_no_client = 1 messages_sent_dropped_no_session = 0 messages_sent_dropped_queue_level = 0 messages_sent_dropped_client_send_failed = 0 messages_sent_dropped_session_not_connected = 0 messages_sent_dropped_header_write_failed = 0 messages_sent_dropped_write_failed = 0 messages_sent_dropped_wrong_client_sm_state = 0 messages_sent_dropped_validation_failed = 0 messages_sent_dropped_rate_limited = 0 messages_sent_dropped_sending_disabled = 0 messages_sent_dropped_sending_to_syslog = 0 ], ] ] tx_msg_diff= [ [ _iter111->first = dropped_no_client _iter111->second = 1, ] ] ]
2018-02-19 Mon 16:13:48:368.698 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028367543 [SYS_NOTICE]: SandeshModuleClientTrace: data= [ name = testbed-1-vm2:Compute:contrail-vrouter-agent:0 client_info= [ status = Disconnect successful_connections = 0 pid = 10774 http_port = 8085 start_time = 1519037028366031 collector_name = collector_ip = 192.168.1.8:8086 collector_list= [ [ (*_iter40) = 192.168.1.8:8086, (*_iter40) = 192.168.1.9:8086, (*_iter40) = 192.168.1.5:8086, ] ] rx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] tx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] ] ]
2018-02-19 Mon 16:13:48:368.760 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028367591 [SYS_NOTICE]: NodeStatusUVE: data= [ name = testbed-1-vm2 process_status= [ [ [ module_id = contrail-vrouter-agent instance_id = 0 state = Non-Functional connection_infos= [ [ [ type = Collector name = server_addrs= [ [ (*_iter6) = 192.168.1.8:8086, ] ] status = Initializing description = Disconnect : EvCollectorUpdate -> Connect ], ] ] description = Collector connection down, No Configuration for self Number of connections:1, Expected: 5 ], ] ] ]
2018-02-19 Mon 16:13:48:368.827 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028368250 [SYS_NOTICE]: SandeshModuleClientTrace: data= [ name = testbed-1-vm2:Compute:contrail-vrouter-agent:0 client_info= [ status = Connect successful_connections = 0 pid = 10774 http_port = 8085 start_time = 1519037028366031 collector_name = collector_ip = 192.168.1.8:8086 collector_list= [ [ (*_iter40) = 192.168.1.8:8086, (*_iter40) = 192.168.1.9:8086, (*_iter40) = 192.168.1.5:8086, ] ] rx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] tx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] ] ]
2018-02-19 Mon 16:13:48:369.904 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028368879 [SYS_NOTICE]: NodeStatusUVE: data= [ name = testbed-1-vm2 process_status= [ [ [ module_id = contrail-vrouter-agent instance_id = 0 state = Non-Functional connection_infos= [ [ [ type = Collector name = server_addrs= [ [ (*_iter6) = 192.168.1.8:8086, ] ] status = Initializing description = Connect : EvTcpConnected ], ] ] description = Collector connection down, No Configuration for self Number of connections:1, Expected: 5 ], ] ] ]
2018-02-19 Mon 16:13:48:370.119 IST testbed-1-vm2 [Thread 139889475393280, Pid 10774]: SANDESH: Send FAILED: 1519037028369847 [SYS_NOTICE]: SandeshModuleClientTrace: data= [ name = testbed-1-vm2:Compute:contrail-vrouter-agent:0 client_info= [ status = ClientInit successful_connections = 1 pid = 10774 http_port = 8085 start_time = 1519037028366031 collector_name = collector_ip = 192.168.1.8:8086 collector_list= [ [ (*_iter40) = 192.168.1.8:8086, (*_iter40) = 192.168.1.9:8086, (*_iter40) = 192.168.1.5:8086, ] ] rx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] tx_socket_stats= [ bytes = 0 calls = 0 average_bytes = 0 blocked_duration = 00:00:00 blocked_count = 0 average_blocked_duration = errors = 0 ] ] msg_type_diff= [ [ _iter107->first = NodeStatusUVE [ messages_sent = 0 messages_sent_dropped_no_queue = 0 messages_sent_dropped_no_client = 0 messages_sent_dropped_no_session = 0 messages_sent_dropped_queue_level = 0 messages_sent_dropped_client_send_failed = 0 messages_sent_dropped_session_not_connected = 0 messages_sent_dropped_header_write_failed = 0 messages_sent_dropped_write_failed = 0 messages_sent_dropped_wrong_client_sm_state = 2 messages_sent_dropped_validation_failed = 0 messages_sent_dropped_rate_limited = 0 messages_sent_dropped_sending_disabled = 0 messages_sent_dropped_sending_to_syslog = 0 ], _iter107->first = SandeshModuleClientTrace [ messages_sent = 0 messages_sent_dropped_no_queue = 0 messages_sent_dropped_no_client = 0 messages_sent_dropped_no_session = 0 messages_sent_dropped_queue_level = 0 messages_sent_dropped_client_send_failed = 0 messages_sent_dropped_session_not_connected = 0 messages_sent_dropped_header_write_failed = 0 messages_sent_dropped_write_failed = 0 messages_sent_dropped_wrong_client_sm_state = 3 messages_sent_dropped_validation_failed = 0 messages_sent_dropped_rate_limited = 0 messages_sent_dropped_sending_disabled = 0 messages_sent_dropped_sending_to_syslog = 0 ], _iter107->first = TcpSessionMessageLog [ messages_sent = 0 messages_sent_dropped_no_queue = 0 messages_sent_dropped_no_client = 0 messages_sent_dropped_no_session = 0 messages_sent_dropped_queue_level = 0 messages_sent_dropped_client_send_failed = 0 messages_sent_dropped_session_not_connected = 0 messages_sent_dropped_header_write_failed = 0 messages_sent_dropped_write_failed = 0 messages_sent_dropped_wrong_client_sm_state = 0 messages_sent_dropped_validation_failed = 0 messages_sent_dropped_rate_limited = 0 messages_sent_dropped_sending_disabled = 1 messages_sent_dropped_sending_to_syslog = 0 ], _iter107->first = VrfObjectLog [ messages_sent = 0 messages_sent_dropped_no_queue = 0 messages_sent_dropped_no_client = 0 messages_sent_dropped_no_session = 0 messages_sent_dropped_queue_level = 0 messages_sent_dropped_client_send_failed = 0 messages_sent_dropped_session_not_connected = 0 messages_sent_dropped_header_write_failed = 0 messages_sent_dropped_write_failed = 0 messages_sent_dropped_wrong_client_sm_state = 2 messages_sent_dropped_validation_failed = 0 messages_sent_dropped_rate_limited = 0 messages_sent_dropped_sending_disabled = 0 messages_sent_dropped_sending_to_syslog = 0 ], ] ] tx_msg_diff= [ [ _iter111->first = dropped_sending_disabled _iter111->second = 1, _iter111->first = dropped_wrong_client_sm_state _iter111->second = 7, ] ] ]
2018-02-19 Mon 16:13:48:442.528 IST testbed-1-vm2 [Thread 139889663154048, Pid 10774]: XMPP [SYS_NOTICE]: XmppEventLog: XMPP Peer testbed-1-vm2:192.168.1.9 RECV Mode Client: Event: Tcp Connected peer ip: 192.168.1.9 ( <email address hidden> ) controller/src/xmpp/xmpp_state_machine.cc 1295
2018-02-19 Mon 16:13:48:442.830 IST testbed-1-vm2 [Thread 139889663154048, Pid 10774]: XMPP [SYS_NOTICE]: XmppEventLog: XMPP Peer testbed-1-vm2:192.168.1.5 RECV Mode Client: Event: Tcp Connected peer ip: 192.168.1.5 ( <email address hidden> ) controller/src/xmpp/xmpp_state_machine.cc 1295
2018-02-19 Mon 16:13:48:443.819 IST testbed-1-vm2 [Thread 139889663154048, Pid 10774]: XMPP [SYS_NOTICE]: XmppEventLog: XMPP Peer testbed-1-vm2:192.168.1.5 RECV Mode Client: Event: Tcp Connected peer ip: 192.168.1.5 ( <email address hidden> ) controller/src/xmpp/xmpp_state_machine.cc 1295
2018-02-19 Mon 16:13:49:440.524 IST testbed-1-vm2 [Thread 139889663154048, Pid 10774]: XMPP :0
[SYS_NOTICE]: XmppEventLog: XMPP Peer testbed-1-vm2:192.168.1.8 RECV Mode Client: Event: Tcp Connected peer ip: 192.168.1.8 ( <email address hidden> ) controller/src/xmpp/xmpp_state_machine.cc 1295

Changed in juniperopenstack:
importance: Undecided → High
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/39913
Committed: http://github.com/Juniper/contrail-test/commit/cd6b1cf8971551e74cb04525b0f4c19ea26412a4
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit cd6b1cf8971551e74cb04525b0f4c19ea26412a4
Author: Venkatesh Velpula <email address hidden>
Date: Tue Feb 20 20:57:34 2018 +0530

Adding new testcases for reboot restart scenarios and currently these
cases will fail due to open bug 1750354 and
Closes-Bug: #1750571

Change-Id: Iefeb13da4210c2599427077f4cc79f2698a506d1

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/39920
Committed: http://github.com/Juniper/contrail-test/commit/cac24f3b2290f2b051288c68833f3fd0a1386e0f
Submitter: Zuul (<email address hidden>)
Branch: R4.1

commit cac24f3b2290f2b051288c68833f3fd0a1386e0f
Author: Venkatesh Velpula <email address hidden>
Date: Tue Feb 20 20:57:34 2018 +0530

Adding new testcases for reboot restart scenarios and currently these
cases will fail due to open bug 1750354 and
Closes-Bug: #1750571

Change-Id: Iefeb13da4210c2599427077f4cc79f2698a506d1

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/39919
Committed: http://github.com/Juniper/contrail-test/commit/e98e293c4cf91bded6d09e7b0ead47496c78d472
Submitter: Zuul (<email address hidden>)
Branch: R4.0

commit e98e293c4cf91bded6d09e7b0ead47496c78d472
Author: Venkatesh Velpula <email address hidden>
Date: Tue Feb 20 20:57:34 2018 +0530

Adding new testcases for reboot restart scenarios and currently these
cases will fail due to open bug 1750354 and
Closes-Bug: #1750571

Change-Id: Iefeb13da4210c2599427077f4cc79f2698a506d1

Revision history for this message
Hari Prasad Killi (haripk) wrote :
Download full text (5.6 KiB)

Netns instances are not deleted properly, resulting in failure during recreation of the same.

[root@nodec58 opencontrail_vrouter_netns]# ip netns list
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
RTNETLINK answers: Invalid argument
vrouter-c5a1bae1-78b2-4b84-beab-6af2e687917b:5bce6b33-2c77-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-6ea8f261-c7a6-4e60-b0e4-e37d3123df92:00fca71a-2c7c-11e8-9da2-002590c8f320
vrouter-dfda8957-c0e9-43a6-bbdc-33c337ad151f:ff849154-2cee-11e8-9da2-002590c8f320 (id: 0)
RTNETLINK answers: Invalid argument
vrouter-33a690e8-9915-48d7-badc-a8a0cc5488bb:00688fa4-2c44-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-174069e7-55ad-4222-bdbf-a52eeb94f531:00fb3f99-2c7c-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-8c86e8a9-e199-43ba-b995-bd1f26ca3aab:9a1dd11e-2c6d-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-b9792783-3fa1-4a35-879f-6eeb587c6823:370b1369-2c40-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-3dbab745-b73a-42c9-ad04-d2b6c5927743:5f6fd7a4-2c69-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-5be57eb7-08f8-4a8c-b3d0-eeefd7705eb5:4613b4ac-2c48-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-cad4057b-4a8d-4bf0-9872-4c971bf7a1a2:9a15dd77-2c6d-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-0a7ab668-473e-4db5-baad-f9e160842c72:9614d494-2c35-11e8-9da2-002590c8f320
RTNETLINK answers: Invalid argument
vrouter-0318109e-f271-40f1-8363-9f2a45f5cb4a:460ad720-2c48-11e8-9da2-002590c8f320

The deletion of these seem to have been invoked from the agent, according to the following traces. But this operation may be failing.

2018-03-21 03:16:13.600 InstanceManagerTrace: StaleNetNS /usr/bin/opencontrail-vrouter-netns destroy loadbalancer c5a1bae1-78b2-4b84-beab-6af2e687917b 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 --loadbalancer-id 5bce6b33-2c77-11e8-9da2-002590c8f320 controller/src/vnsw/agent/oper/instance_manager.cc 734
2018-03-21 03:16:13.637 InstanceManagerTrace: StaleNetNS /usr/bin/opencontrail-vrouter-netns destroy loadbalancer 6ea8f261-c7a6-4e60-b0e4-e37d3123df92 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 --loadbalancer-id 00fca71a-2c7c-11e8-9da2-002590c8f320 controller/src/vnsw/agent/oper/instance_manager.cc 734
2018-03-21 03:16:13.669 InstanceManagerTrace: StaleNetNS /usr/bin/opencontrail-vrouter-netns destroy loadbalancer 33a690e8-9915-48d7-badc-a8a0cc5488bb 00000000-0000-0000-0000-000000000000 00000000-0000-0000-0000-000000000000 --loadbalancer-id 00688fa4-2c44-11e8-9da2-002590c8f320 controller/src/vnsw/agent/oper/instance_manager.cc 734
2018-03-21 03:16:13.697 InstanceManagerTrace: StaleNetNS /usr/bin/opencontrail-vrouter-netns destroy loadbalancer 174069e...

Read more...

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/41155
Submitter: Yuvaraja Mariappan

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/41155
Committed: http://github.com/Juniper/contrail-container-builder/commit/583def1063c78de9d52b20698f834e5a1cc2fd27
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 583def1063c78de9d52b20698f834e5a1cc2fd27
Author: Prasanna Mucharikar <email address hidden>
Date: Wed Mar 28 14:42:22 2018 -0700

Adding function to cleanup loadbalancer stale data and invoking it from
entrypoint
Closes-bug: #1750354

Change-Id: I07d2695da6eea8eab3ed2953c0150cf846aa4dfe

Revision history for this message
Venkatesh Velpula (vvelpula) wrote :

issue is still there ...latest we tried in 5.0-20 and 5-0-25...

tags: added: sanityblocker
Revision history for this message
Venkatesh Velpula (vvelpula) wrote :

work around for this issue

1) rm -rf /var/lib/contrail/loadbalancer/*
2) rm -rf /var/run/netns/*
3) restart the agent again

Jeba Paulaiyan (jebap)
tags: added: releasenote
Revision history for this message
Hari Prasad Killi (haripk) wrote :

https://github.com/Juniper/contrail-container-builder/commit/25d747c0d7f8365220333fde285dda2d35b1e9c4#diff-2a43f19d399a044b13abf63f148a3ff7 moved the cleanup_lbaas_netns_config
call from agent entry point to trap based invocation. Have to change it back to unconditional cleanup / trap all signals.

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/42451
Submitter: <email address hidden> (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R5.0

Review in progress for https://review.opencontrail.org/42452
Submitter: <email address hidden> (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/42452
Committed: http://github.com/Juniper/contrail-container-builder/commit/df332fe9f465ec4cc49a1774442153cd6f20f984
Submitter: Zuul v3 CI (<email address hidden>)
Branch: R5.0

commit df332fe9f465ec4cc49a1774442153cd6f20f984
Author: Madhukar Nayakbomman <email address hidden>
Date: Mon Apr 23 23:53:33 2018 -0700

Cleaning up of lbaas config

Making sure that lbaas config is cleaned at all times during bring up of
agent container

Change-Id: Ibc75befa510e34ea8611d2088dc5aa3f6310d127
Closes-bug: #1750354

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/42451
Committed: http://github.com/Juniper/contrail-container-builder/commit/2697a31fa648ffc95a3014364836cccc9fbeb1d1
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 2697a31fa648ffc95a3014364836cccc9fbeb1d1
Author: Madhukar Nayakbomman <email address hidden>
Date: Mon Apr 23 23:53:33 2018 -0700

Cleaning up of lbaas config

Making sure that lbaas config is cleaned at all times during bring up of
agent container

Change-Id: Ibc75befa510e34ea8611d2088dc5aa3f6310d127
Closes-bug: #1750354

Revision history for this message
Venkatesh Velpula (vvelpula) wrote :
Download full text (5.8 KiB)

[root@nodei23 /]# ps -aef | grep haproxy
haproxy 28355 28374 0 14:43 ? 00:00:00 haproxy -f /var/lib/contrail/loadbalancer/haproxy/e2c96b61-4931-11e8-b0be-002590e781c0/haproxy.conf -p /var/lib/contrail/loadbalancer/haproxy/e2c96b61-4931-11e8-b0be-002590e781c0/haproxy.pid -sf 28340
root 29099 29051 0 14:46 ? 00:00:00 grep --color=auto haproxy
[root@nodei23 /]#
[root@nodei23 /]#
[root@nodei23 /]#
[root@nodei23 /]# [root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]# docker exec -it vrouter_vrouter-agent_1 bash^C
[root@nodei23 ~]#
[root@nodei23 ~]# docker restart vrouter_vrouter-agent_1
vrouter_vrouter-agent_1
[root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]#
[root@nodei23 ~]# docker exec -it vrouter_vrouter-agent_1 bash
[root@nodei23 /]#
[root@nodei23 /]#
[root@nodei23 /]# ps -aef | grep haproxy
haproxy 29429 29166 0 14:46 ? 00:00:00 haproxy -f /var/lib/contrail/loadbalancer/haproxy/e2c96b61-4931-11e8-b0be-002590e781c0/haproxy.conf -p /var/lib/contrail/loadbalancer/haproxy/e2c96b61-4931-11e8-b0be-002590e781c0/haproxy.pid
root 29475 29458 0 14:46 ? 00:00:00 grep --color=auto haproxy
[root@nodei23 /]#
[root@nodei23 /]# contrail-version
Package Version Build-ID | Repo | RPM Name
-------------------------------------- ------------------------------ ----------------------------------
contrail-lib 5.0-36.el7.centos @contrail
contrail-vrouter-agent 5.0-36.el7.centos @contrail
contrail-vrouter-utils 5.0-36.el7.centos @contrail
python-contrail 5.0-36.el7.centos @contrail
python-contrail-vrouter-api 5.0-36.el7.centos @contrail
contrail-utils 5.0-36.el7.centos @contrail
python-opencontrail-vrouter-netns 5.0-36.el7.centos @contrail
contrail-setup 5.0-36.el7.centos @contrail

[root@nodei22 ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
nodei22 NotReady master 4h v1.9.2
nodei23 Ready <none> 4h v1.9.2

[root@nodei23 ~]# contrail-status
Pod Service Original Name State Status
vrouter agent contrail-vrouter-agent running Up About a minute
vrouter nodemgr contrail-nodemgr running Up 4 hours

vrouter kernel module is PRESENT
== Contrail vrouter ==
nodemgr: initializing (NTP state unsynchronized.)
agent: active

[root@nodei23 ~]#

[root@nodei22 ~]# contrail-status
Pod Service Original Name State Status
analytics alarm-gen contrail-analytics-alarm-gen running Up 4 hours
analytics api contrail-analytics-api running Up 4 hours
analytics collector contrail-analytics-collector running Up 4 hours
analytics nodemgr contrail-nodemg...

Read more...

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.