Juniper Openstack

The NodeTableExport() should call ConfigChanged() for a node-delete.

Bug #1462549 reported by Tapan Karwa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.0
Fix Committed
Medium
Tapan Karwa
R2.1
Fix Committed
Medium
Tapan Karwa
R2.20
Fix Committed
High
Tapan Karwa
Juniper Openstack r2.20-fcs
Trunk
Fix Committed
Medium
Tapan Karwa
Juniper Openstack r3.0-fcs

Bug Description

If the node gets revived (add followed by delete followed by add), we could have cases where the CRC in the second add is the same as CRC in the first add, causing 'bool change' to be false. But, the node has really changed since there was a delete in the middle.

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

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

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

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

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

Review in progress for https://review.opencontrail.org/11331
Submitter: Tapan Karwa (<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/11332
Submitter: Tapan Karwa (<email address hidden>)

Tapan Karwa (tkarwa)
no longer affects: juniperopenstack/r2.30
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/11329
Committed: http://github.org/Juniper/contrail-controller/commit/569828e58f140773a1b8996db9f95653e81fa4d3
Submitter: Zuul
Branch: master

commit 569828e58f140773a1b8996db9f95653e81fa4d3
Author: Tapan Karwa <email address hidden>
Date: Fri Jun 5 13:22:27 2015 -0700

The NodeTableExport() should call ConfigChanged() for a node-delete.

If the node gets revived (add followed by delete followed by add), we could have
cases where the CRC in the second add is the same as CRC in the first add,
causing 'bool change' to be false. But, the node has really changed since there
was a delete in the middle.

Closes-Bug: 1462549

Change-Id: Ife1f98ef8bc35826b829d2d122068edcf092469e

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

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

commit efce98fa2c629d1c43cc915eed56fcadafaf6356
Author: Tapan Karwa <email address hidden>
Date: Fri Jun 5 13:22:27 2015 -0700

The NodeTableExport() should call ConfigChanged() for a node-delete.

If the node gets revived (add followed by delete followed by add), we could have
cases where the CRC in the second add is the same as CRC in the first add,
causing 'bool change' to be false. But, the node has really changed since there
was a delete in the middle.

Closes-Bug: 1462549

Change-Id: Ife1f98ef8bc35826b829d2d122068edcf092469e

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

Reviewed: https://review.opencontrail.org/11330
Committed: http://github.org/Juniper/contrail-controller/commit/681fb5da43c2bfa6ced1ffe687f4f9863f84d4ec
Submitter: Zuul
Branch: R2.1

commit 681fb5da43c2bfa6ced1ffe687f4f9863f84d4ec
Author: Tapan Karwa <email address hidden>
Date: Fri Jun 5 13:22:27 2015 -0700

The NodeTableExport() should call ConfigChanged() for a node-delete.

If the node gets revived (add followed by delete followed by add), we could have
cases where the CRC in the second add is the same as CRC in the first add,
causing 'bool change' to be false. But, the node has really changed since there
was a delete in the middle.

Closes-Bug: 1462549

Change-Id: Ife1f98ef8bc35826b829d2d122068edcf092469e

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

Reviewed: https://review.opencontrail.org/11331
Committed: http://github.org/Juniper/contrail-controller/commit/e9441c800676902ade1cd7be8a3554488baf9ba1
Submitter: Zuul
Branch: R2.0

commit e9441c800676902ade1cd7be8a3554488baf9ba1
Author: Tapan Karwa <email address hidden>
Date: Fri Jun 5 13:22:27 2015 -0700

The NodeTableExport() should call ConfigChanged() for a node-delete.

If the node gets revived (add followed by delete followed by add), we could have
cases where the CRC in the second add is the same as CRC in the first add,
causing 'bool change' to be false. But, the node has really changed since there
was a delete in the middle.

Closes-Bug: 1462549

Change-Id: Ife1f98ef8bc35826b829d2d122068edcf092469e

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.