.contrail-dns crash is seen during upgrade from 2.22.2-14 to 3.0.2-40 at contrail-dns: controller/src/base/task.cc:291: virtual tbb::task* TaskImpl::execute():

Bug #1584174 reported by manishkn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
Critical
Nipa
R2.21.x
Fix Committed
Critical
Nipa
R2.22.x
Fix Committed
Critical
Nipa
R3.0
Fix Committed
Critical
Nipa
Trunk
Fix Committed
Critical
Nipa

Bug Description

Hi,

On upgrading from 2.22.2-14 to latest 3.0.2.40, I see this crash .

Core file and bin is placed in /cs-shared/bugs/#

Program terminated with signal SIGABRT, Aborted.
#0 0x00007f5f56a95cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x00007f5f56a95cc9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007f5f56a990d8 in __GI_abort () at abort.c:89
#2 0x00007f5f56a8eb86 in __assert_fail_base (fmt=0x7f5f56bdf830 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xac6b7b "0",
    file=file@entry=0xa8b044 "controller/src/base/task.cc", line=line@entry=291,
    function=function@entry=0xa8cbc0 <TaskImpl::execute()::__PRETTY_FUNCTION__> "virtual tbb::task* TaskImpl::execute()") at assert.c:92
#3 0x00007f5f56a8ec32 in __GI___assert_fail (assertion=0xac6b7b "0", file=0xa8b044 "controller/src/base/task.cc", line=291,
    function=0xa8cbc0 <TaskImpl::execute()::__PRETTY_FUNCTION__> "virtual tbb::task* TaskImpl::execute()") at assert.c:101
#4 0x0000000000640c83 in TaskImpl::execute (this=<optimized out>) at controller/src/base/task.cc:291
#5 0x00007f5f5786cb3a in ?? ()
#6 0x00007f5f5026ff28 in ?? ()
#7 0x00007f5f5026ff40 in ?? ()
#8 0x0000000000000001 in ?? ()
#9 0x00007f5f50303880 in ?? ()
#10 0x00007f5f5026ff28 in ?? ()
#11 0x0000000000000000 in ?? ()

Contrail collector also crash with same traces. Pls reassign if you think someone else should tale care of collector crash

Tags: blocker vdns
manishkn (manishkn)
summary: .contrail-dns crash is seen during upgrade from 2.22.2-14 to 3.0.2-40 at
- function=function@entry=0xa8cbc0
- <TaskImpl::execute()::__PRETTY_FUNCTION__> "virtual tbb::task*
- TaskImpl::execute()") at assert.c:92
+ contrail-dns: controller/src/base/task.cc:291: virtual tbb::task*
+ TaskImpl::execute():
Changed in juniperopenstack:
milestone: none → r3.0.2.0
Jeba Paulaiyan (jebap)
information type: Proprietary → Public
manishkn (manishkn)
description: updated
Revision history for this message
Hari Prasad Killi (haripk) wrote :

-rwxr-xr-x 1 root root 85401600 May 21 10:23 core.contrail-dns.2711.sdkvse4.1463703254

{"build-info":[{"build-time":"2016-05-19 09:49:09.415105","build-hostname":"contrail-ec-build17","build-user":"contrail-builder","build-version":"3.0.2.0","build-id":"3.0.2.0-40","build-number":"40"}]}

std::bad_alloc exception is caught. Corruption ?

Jeba Paulaiyan (jebap)
tags: added: blocker
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.0

Review in progress for https://review.opencontrail.org/20741
Submitter: Hari Prasad Killi (<email address hidden>)

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

Reviewed: https://review.opencontrail.org/20741
Committed: http://github.org/Juniper/contrail-controller/commit/d09203de75444e54f90ea5bf9b83443e29726281
Submitter: Zuul
Branch: R3.0

commit d09203de75444e54f90ea5bf9b83443e29726281
Author: Hari <email address hidden>
Date: Sun May 29 14:07:41 2016 +0530

Fix accessing deleted vdns obect.

When virtual-dns is deleted, all records configured under the vdns
have their vdns pointer reset. In this case, it was not reset as the
record wasnt added in the list under vdns, although the record was
pointing to vdns. This resulted in accessing deleted vdns entry.

In addition, make sure record is made valid when the appropriate
vdns for it is updated.

Change-Id: Id32f029014a46e8fe3efe35380940706708e7708
closes-bug: #1584174

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

Review in progress for https://review.opencontrail.org/20751
Submitter: Hari Prasad Killi (<email address hidden>)

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

Review in progress for https://review.opencontrail.org/20752
Submitter: Hari Prasad Killi (<email address hidden>)

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

Review in progress for https://review.opencontrail.org/20753
Submitter: Hari Prasad Killi (<email address hidden>)

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

Review in progress for https://review.opencontrail.org/20754
Submitter: Hari Prasad Killi (<email address hidden>)

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

Reviewed: https://review.opencontrail.org/20752
Committed: http://github.org/Juniper/contrail-controller/commit/3dd69c770726be080ac573d2f76613bf6029e070
Submitter: Zuul
Branch: R2.20

commit 3dd69c770726be080ac573d2f76613bf6029e070
Author: Hari <email address hidden>
Date: Sun May 29 14:07:41 2016 +0530

Fix accessing deleted vdns obect.

When virtual-dns is deleted, all records configured under the vdns
have their vdns pointer reset. In this case, it was not reset as the
record wasnt added in the list under vdns, although the record was
pointing to vdns. This resulted in accessing deleted vdns entry.

In addition, make sure record is made valid when the appropriate
vdns for it is updated.

Change-Id: Id32f029014a46e8fe3efe35380940706708e7708
closes-bug: #1584174
(cherry picked from commit d09203de75444e54f90ea5bf9b83443e29726281)

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

Reviewed: https://review.opencontrail.org/20751
Committed: http://github.org/Juniper/contrail-controller/commit/6528eb47b0f9c92e7669397432b7d1412fcec323
Submitter: Zuul
Branch: master

commit 6528eb47b0f9c92e7669397432b7d1412fcec323
Author: Hari <email address hidden>
Date: Sun May 29 14:07:41 2016 +0530

Fix accessing deleted vdns obect.

When virtual-dns is deleted, all records configured under the vdns
have their vdns pointer reset. In this case, it was not reset as the
record wasnt added in the list under vdns, although the record was
pointing to vdns. This resulted in accessing deleted vdns entry.

In addition, make sure record is made valid when the appropriate
vdns for it is updated.

Change-Id: Id32f029014a46e8fe3efe35380940706708e7708
closes-bug: #1584174
(cherry picked from commit d09203de75444e54f90ea5bf9b83443e29726281)

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

Reviewed: https://review.opencontrail.org/20754
Committed: http://github.org/Juniper/contrail-controller/commit/e49e8ea8d29fdd029c2b57c85712207efa0d6954
Submitter: Zuul
Branch: R2.21.x

commit e49e8ea8d29fdd029c2b57c85712207efa0d6954
Author: Hari <email address hidden>
Date: Sun May 29 14:07:41 2016 +0530

Fix accessing deleted vdns obect.

When virtual-dns is deleted, all records configured under the vdns
have their vdns pointer reset. In this case, it was not reset as the
record wasnt added in the list under vdns, although the record was
pointing to vdns. This resulted in accessing deleted vdns entry.

In addition, make sure record is made valid when the appropriate
vdns for it is updated.

Change-Id: Id32f029014a46e8fe3efe35380940706708e7708
closes-bug: #1584174
(cherry picked from commit d09203de75444e54f90ea5bf9b83443e29726281)

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

Reviewed: https://review.opencontrail.org/20753
Committed: http://github.org/Juniper/contrail-controller/commit/390e04a37cc1e393ab418bf3e497e4e87b8b3e8b
Submitter: Zuul
Branch: R2.22.x

commit 390e04a37cc1e393ab418bf3e497e4e87b8b3e8b
Author: Hari <email address hidden>
Date: Sun May 29 14:07:41 2016 +0530

Fix accessing deleted vdns obect.

When virtual-dns is deleted, all records configured under the vdns
have their vdns pointer reset. In this case, it was not reset as the
record wasnt added in the list under vdns, although the record was
pointing to vdns. This resulted in accessing deleted vdns entry.

In addition, make sure record is made valid when the appropriate
vdns for it is updated.

Change-Id: Id32f029014a46e8fe3efe35380940706708e7708
closes-bug: #1584174
(cherry picked from commit d09203de75444e54f90ea5bf9b83443e29726281)

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.