[R2.20-ubuntu-12-04 icehouse: Build 2]: vrouter-agent crash seen after running docker command

Bug #1447461 reported by alok kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
High
Ashok Singh
Trunk
Fix Committed
High
Ashok Singh

Bug Description

vrouter crashed after running below docker commands(compute node was hanged for sometime, console was also not opening. when it came back I found agent core):

root@nodec62:/etc/nova# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3a3a9b4274c5 ubuntu:14.04 "/bin/bash" 4 minutes ago Up 4 minutes nova-b4c3a3d4-255b-48cc-be08-7255fc717983
07c3c952059d ubuntu:14.04 "/bin/bash" 15 minutes ago Up 15 minutes nova-21456ee6-d36c-43c2-ae67-e09dece880f9
root@nodec62:/etc/nova# docker ps -l
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
3a3a9b4274c5 ubuntu:14.04 "/bin/bash" 4 minutes ago Up 4 minutes nova-b4c3a3d4-255b-48cc-be08-7255fc717983
root@nodec62:/etc/nova# docker run 3a3a9b4274c5 /bin/echo "hello"
Unable to find image '3a3a9b4274c5:latest' locally
Pulling repository 3a3a9b4274c5
^Croot@nodec62:/etc/nova#
root@nodec62:/etc/nova#
root@nodec62:/etc/nova# docker run ubuntu:14.04 /bin/echo "hello"
hello
Write failed: Broken pipe

trace from core:
(gdb) bt
#0 0x00007f7eca1ea5ae in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f7eca1ecf95 in malloc () from /lib/x86_64-linux-gnu/libc.so.6
#2 0x00007f7ecaaf1ded in operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3 0x0000000000ffe491 in void boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::chrono::steady_clock> >::async_wait<boost::_bi::bind_t<void, boost::_mfi::mf4<void, Timer, boost::intrusive_ptr<Timer>, int, unsigned int, boost::system::error_code const&>, boost::_bi::list5<boost::_bi::value<Timer*>, boost::_bi::value<boost::intrusive_ptr<Timer> >, boost::_bi::value<int>, boost::_bi::value<unsigned int>, boost::arg<1> (*)()> > >(boost::asio::detail::deadline_timer_service<boost::asio::time_traits<boost::chrono::steady_clock> >::implementation_type&, boost::_bi::bind_t<void, boost::_mfi::mf4<void, Timer, boost::intrusive_ptr<Timer>, int, unsigned int, boost::system::error_code const&>, boost::_bi::list5<boost::_bi::value<Timer*>, boost::_bi::value<boost::intrusive_ptr<Timer> >, boost::_bi::value<int>, boost::_bi::value<unsigned int>, boost::arg<1> (*)()> >) ()
#4 0x0000000000ffbf2b in Timer::Start(int, boost::function<bool ()>, boost::function<void (std::string, std::string, std::string)>) ()
#5 0x0000000000ffe6d4 in Timer::TimerTask::Run() ()
#6 0x0000000000ff0855 in TaskImpl::execute() ()
#7 0x00007f7ecad5ae52 in ?? () from /usr/lib/libtbb.so.2
#8 0x00007f7ecad56c2d in ?? () from /usr/lib/libtbb.so.2
#9 0x00007f7ecad560db in ?? () from /usr/lib/libtbb.so.2
#10 0x00007f7ecad53c1f in ?? () from /usr/lib/libtbb.so.2
#11 0x00007f7ecad53e59 in ?? () from /usr/lib/libtbb.so.2
#12 0x00007f7ecaf71e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#13 0x00007f7eca25e3fd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#14 0x0000000000000000 in ?? ()

setup info:
env.roledefs = {
    'all': [host1,host2,host3,host4,host5],
    'cfgm': [host1,host2,host5],
    'openstack':[host2],
    'control': [host2,host1],
    'compute': [host3,host4],
    'collector': [host2,host1],
    'webui': [host1],
    'database': [host1,host2,host5],
    'build': [host_build],
}

env.hostnames = {
    'all': ['nodec64', 'nodeg18', 'nodec62', 'nodec11', 'nodec12']
}

Tags: vrouter
alok kumar (kalok)
tags: added: vrouter
Revision history for this message
alok kumar (kalok) wrote :

logs @mayamruga-E71:/home/bhushana/Documents/technical/bugs/<bugId>

alok kumar (kalok)
summary: - [R2.20-ubuntu-12-04 icehouse: Build 2]: vrouter crash seen after running
- docker command
+ [R2.20-ubuntu-12-04 icehouse: Build 2]: vrouter-agent crash seen after
+ running docker command
information type: Proprietary → Public
Revision history for this message
Hari Prasad Killi (haripk) wrote :
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.