VNF create with templates larger than 4096 byte fails

Bug #1534844 reported by Sridhar Ramaswamy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Medium
bharaththiruveedula

Bug Description

When a VNF template of size > 4k is used in tacker the vnfd-create operation succeeds fine but vnf-create using that VNFD template fails with Internal Server Error,

$ tacker vnfd-create --name huge-vnf-template --vnfd-file sample-vnfd-no-monitor-huge.yaml

$ tacker vnf-create --name test-huge-vnf --vnfd-name huge-vnf-template

VNF stays indefinitely in PENDING_CREATE state and tacker log shows the follow error,

DBError: (pymysql.err.DataError) (1406, u"Data too long for column 'value' at row 1") [SQL: u'INSERT INTO deviceattributes (id,...

Revision history for this message
Sridhar Ramaswamy (srics-r) wrote :
description: updated
Changed in tacker:
importance: Low → Medium
Changed in tacker:
assignee: nobody → bharaththiruveedula (bharath-ves)
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/271811

Changed in tacker:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/271811
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=b5d7289421af9bf9ded4d38f18ab8cb84d96bdb1
Submitter: Jenkins
Branch: master

commit b5d7289421af9bf9ded4d38f18ab8cb84d96bdb1
Author: Bharath Thiruveedula <email address hidden>
Date: Mon Jan 25 00:05:06 2016 +0530

    Alter the 'value' column in 'deviceattributes' table

    Increase the size of 'value' column in 'deviceattributes' table
    from string(4096) to text(65535) to allocate large VNFD values.

    Change-Id: I10ff4696a75be6d0240ad35a806b9cd4b52690a1
    Closes-Bug: #1534844

Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/tacker 0.3.0

This issue was fixed in the openstack/tacker 0.3.0 release.

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.