Juniper Openstack

[R2.20.49] UI: Associating user created VDNS with default ipam is failing

Series r2.20
Bug #1465631

Bug #1465631 reported by chhandak on 2015-06-16

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Juniper Openstack	Status tracked in Trunk
R2.20	Fix Committed	High	Siva Bavanasi	Juniper Openstack r2.20-fcs
Trunk	Fix Committed	Undecided	Siva Bavanasi

Bug Description

In TOR Scale setup associating VDNS with default-ipjm is failing . UI has shown error log saying "Request entry too large" Screenshot attached

In the scale setup we have 6K VN in 3 different project but all having one default ipam.

Tags:

Revision history for this message

chhandak (chhandak) wrote on 2015-06-16:

Screen Shot 2015-06-16 at 4.38.39 PM.png Edit (104.5 KiB, image/png)

Revision history for this message

OpenContrail Admin (ci-admin-f) wrote on 2015-06-16:

We need to test with lower no VNs per project to see where do we break,

information type:

Proprietary → Public

Revision history for this message

Raj Reddy (rajreddy) wrote on 2015-06-16:

Hi Raj,Chhandak,
Siva is fixing the issue. The issue was while doing a PUT on network-ipam (default-network-ipam) which is having a lot of virtual_network_back_refs, so API Server was throwing size error on post data.

With regards,
Biswajit

Siva Bavanasi (kbsiva) on 2015-06-17

Changed in juniperopenstack:
assignee:	nobody → Siva Bavanasi (kbsiva)

Revision history for this message

OpenContrail Admin (ci-admin-f) wrote on 2015-06-17: [Review update] R2.20

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

Revision history for this message

OpenContrail Admin (ci-admin-f) wrote on 2015-06-17: A change has been merged

Reviewed: https://review.opencontrail.org/11718
Committed: http://github.org/Juniper/contrail-web-controller/commit/0ec1dad63741ff981584f1695cfd3dba6ab0d2b6
Submitter: Zuul
Branch: R2.20

commit 0ec1dad63741ff981584f1695cfd3dba6ab0d2b6
Author: Siva Bavanasi <email address hidden>
Date: Wed Jun 17 11:25:20 2015 +0530

In IPAM get object response removed virtual_network_back_refs and doing put with virtual_dns_refs for R2.20.

Ideally we should remove complete IPAM get itself and directly proceed with IAPM put. It may lead to test many scenarios, hence targeting it to master.

Change-Id: I2aa04957d76b0cb5ed460b298c307953e8c9e48e
Closes-bug: #1465631

Revision history for this message

OpenContrail Admin (ci-admin-f) wrote on 2015-06-19: [Review update] master

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