vnf-create is failing for parameterized input for both user_data and ip addr. yaml files

Bug #1501910 reported by Sripriya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Undecided
vishwanath jayaraman
Sripriya (sseetha)
Changed in tacker:
status: New → Confirmed
Changed in tacker:
assignee: nobody → vishwanath jayaraman (vishwanathj)
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/230169

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

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

commit caee7758364457ffbc782568b5519de1fbfea466
Author: Vishwanath Jayaraman <email address hidden>
Date: Thu Oct 1 16:53:51 2015 -0500

    Fixes vnf create failure even if all parameters are supplied

    This commit adds code to fix the issue where vnf creation fails even
    if all the parameter values are supplied for the get_input parameters
    in VNFD template. The code was not properly handling the scenario
    where a certain non-vdu section may not have been parameterized in the
    VNFD template

    Change-Id: I459b0d4104cafeda6c26c5223e571f76cb5300da
    Closes-Bug: #1501910

Changed in tacker:
status: In Progress → Fix Committed
Changed in tacker:
status: Fix Committed → Fix Released
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.