Comment 6 for bug 1912589

hi,

We tried to reproduce this bug, but we could not able reproduce it.

Following steps we had followed

1. created vnf descriptor by using file given in bug.

stack@necuser-HP-ProDesk-400-G2-MT:~/tacker$ openstack vnf descriptor create --vnfd-file tosca-vnfd-scale.yaml vnfd-scale

stack@necuser-HP-ProDesk-400-G2-MT:~/tacker$ openstack vnf descriptor list
+--------------------------------------+------------+-----------------+---------------------------+
| ID | Name | Template_Source | Description |
+--------------------------------------+------------+-----------------+---------------------------+
| 386a97e0-da8c-4475-bc8a-1f807ac0896f | vnfd-scale | onboarded | sample-tosca-vnfd-scaling |
+--------------------------------------+------------+-----------------+---------------------------+

2. created vnf using vnf descriptor created in step 1

stack@necuser-HP-ProDesk-400-G2-MT:~/tacker$ openstack vnf create --vnfd-id 386a97e0-da8c-4475-bc8a-1f807ac0896f Navum_1234

3. Login to tacker UI and open vnf manager events tab under NFV.
4. In VNF catalog tab our created vnf descriptor is showing
5. In VNF manager our created vnf is showing.
6. Then, we had performed scale out operation on created vnf

stack@necuser-HP-ProDesk-400-G2-MT:~$ openstack vnf scale --scaling-policy-name SP1 --scaling-type out 3b0b6ee9-6509-4ff8-be37-3ce7aa7ce65f

7. After that, we had performed scale out operation on created vnf

stack@necuser-HP-ProDesk-400-G2-MT:~$ openstack vnf scale --scaling-policy-name SP1 --scaling-type in 3b0b6ee9-6509-4ff8-be37-3ce7aa7ce65f

VNFD is as following

metadata:
  template_name: sample-tosca-vnfd-scaling

topology_template:
  node_templates:
    VDU1:
      type: tosca.nodes.nfv.VDU.Tacker
      properties:
        image: cirros-0.5.2-x86_64-disk
        mgmt_driver: noop
        availability_zone: nova
        flavor: m1.tiny

    CP1:
      type: tosca.nodes.nfv.CP.Tacker
      properties:
        management: true
        order: 0
        anti_spoofing_protection: false
      requirements:
        - virtualLink:
            node: VL1
        - virtualBinding:
            node: VDU1

    VDU2:
      type: tosca.nodes.nfv.VDU.Tacker
      properties:
        image: cirros-0.5.2-x86_64-disk
        mgmt_driver: noop
        availability_zone: nova
        flavor: m1.tiny

    CP2:
      type: tosca.nodes.nfv.CP.Tacker
      properties:
        management: true
        order: 0
        anti_spoofing_protection: false
      requirements:
        - virtualLink:
            node: VL1
        - virtualBinding:
            node: VDU2

    VL1:
      type: tosca.nodes.nfv.VL
      properties:
        network_name: net0
        vendor: Tacker

  policies:
    - SP1:
        type: tosca.policies.tacker.Scaling
  properties:
          targets: [VDU1, VDU2]
          increment: 1
          cooldown: 120
          min_instances: 1
          max_instances: 3
          default_instances: 2

Note: Please, share detailed procedure if we are missing something in above procedure