No handling when updating with wrong value(disk size) for VNF updation

Bug #1716831 reported by Manik Bindlish
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Confirmed
Undecided
Manik Bindlish

Bug Description

Release: Stable Newton
Ubuntu 16.04
Environment for NFV

There is no handling when inputting wrong value(e.g disk size), values are reflecting in tacker vnf-show but actually not updated on VNF.
There should be handling that operation should be fail for wrong value input.

Scenario:
1.) Created VNF with disk size:1 GB
| 701b8b15-2859-4113 | fwvnf | OpenWRT with | {"VDU1": | ACTIVE | 613ab165-a420-4362 | {u'vim_name': | |
| -b2e3-a2ca4af6061a | | services | "192.168.x.x"} | | -813d-ec2936422942 | u'nfv_poc'} | |
+--------------------+--------------------+--------------------+--------------------+----------------+--------------------+--------------------+-----------------------+

2.) Updated VNF firstly with 3GB and then again with 7GB

dharmendra@controller:~/logsnall$ tacker vnf-update fwvnf --config-file firewall_update.yaml
Updated vnf: fwvnf

3.) Values reflected in tacker vnf-show and actually disk size not upgraded
properties: {disk_size: 3 GB, mem_size: 512 MB, num_cpus: 1}

These values shouldn't be reflect and updation should be fail for wrong value input

Revision history for this message
Manik Bindlish (manikbindlish19) wrote :
Changed in tacker:
assignee: nobody → Manik Bindlish (manikbindlish)
Revision history for this message
yong sheng gong (gongysh) wrote :

what is the content of fireewall_update.yaml?

Changed in tacker:
status: New → Confirmed
Changed in tacker:
milestone: none → queens-3
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.