Tacker failing to ping vnf and re-spawning again and again

Bug #1557008 reported by dharmendra
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Medium
Unassigned

Bug Description

Deployed a new new OpenWRT vnf with default tacker/devstack/samples/openwrt.yaml by GUI.
After same time of showing ACTIVE state, vnf goies into DEAD state. And keep re-spawning again and again.

Log showing tacker failing to ping.

2016-03-14 20:35:22.144 ERROR tacker.agent.linux.utils [-]
Command: ['ping', '-c', '5', '-W', '1', '-i', '0.2', '192.168.120.8']
Exit code: 1
Stdout: 'PING 192.168.120.8 (192.168.120.8) 56(84) bytes of data.\n\n--- 192.168.120.8 ping statistics ---\n5 packets transmitted, 0 received, 100% packet loss, time 827ms\n\n'
Stderr: ''
2016-03-14 20:35:22.145 WARNING tacker.vm.monitor_drivers.ping.ping [-] Cannot ping ip address: 192.168.120.8
2016-03-14 20:35:22.145 DEBUG tacker.vm.monitor [-] driver_return failure from (pid=12324) run_monitor /opt/stack/tacker/tacker/vm/monitor.py:150
2016-03-14 20:35:22.146 ERROR tacker.vm.monitor [-] device 395af00c-3909-412f-9f52-33e44644c573 dead

Revision history for this message
dharmendra (dharmendra-kushwaha) wrote :
Revision history for this message
Sridhar Ramaswamy (srics-r) wrote :

Which version of OpenWRT are you using ? The default version uploaded doesn't have dhcp enabled and hence it won't respond to ping.

We need a fix as outlined in [1].

[1] https://review.openstack.org/#/c/289776/

Changed in tacker:
assignee: nobody → dharmendra (dharmendra-kushwaha)
Changed in tacker:
importance: Undecided → Medium
Aqsa Malik (aqsamm)
Changed in tacker:
assignee: dharmendra (dharmendra-kushwaha) → Aqsa Malik (aqsamm)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.openstack.org/421340

Changed in tacker:
status: New → In Progress
Changed in tacker:
milestone: none → ocata-3
Revision history for this message
Sridhar Ramaswamy (srics-r) wrote :

Out of time for Ocata, moving to Pike.

Changed in tacker:
milestone: ocata-3 → pike-1
Changed in tacker:
milestone: pike-1 → pike-2
Changed in tacker:
milestone: pike-2 → pike-3
Changed in tacker:
milestone: pike-3 → none
Changed in tacker:
assignee: Aqsa Malik (aqsamm) → Nguyen Hai (nguyentrihai93)
Changed in tacker:
status: In Progress → Fix Committed
Revision history for this message
Nguyen Hai (nguyentrihai93-deactivatedaccount) wrote :
Changed in tacker:
status: Fix Committed → In Progress
Changed in tacker:
milestone: none → queens-3
Changed in tacker:
milestone: queens-3 → rocky-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/543413
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=da9e0e4b9b0ba9dbea1c985b0ae169e5a910120c
Submitter: Zuul
Branch: master

commit da9e0e4b9b0ba9dbea1c985b0ae169e5a910120c
Author: Nguyen Hai <email address hidden>
Date: Mon Feb 12 19:18:14 2018 +0900

    Modify OpenWRT image & rewrite deployment OpenWRT instruction

    This patch adds the customized OpenWRT image that enables DHCP making
    the VNF can be ping. Therefore, the continuously respawning of VNF
    can be fixed.

    This patch also rewrites the instruction of deploying VNF
    based on OpenWRT.

    Change-Id: Ieb4d98fe374676bad101a6c2965354a9b19ea0a2
    Closes-Bug: #1557008
    Closes-Bug: #1749243
    Closes-Bug: #1709557

Changed in tacker:
status: In Progress → Fix Released
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.