tacker

NS status is active but member vnfs are in error

Bug #1674896 reported by yong sheng gong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tacker
Confirmed
Medium
Unassigned
tacker queens-3

Bug Description

gongysh@ubuntu64:/opt/stack/tacker/samples/tosca-templates$ tacker vnf-list
+--------------------------+--------------------------+----------+--------+--------------------------+---------------------------+
| id | name | mgmt_url | status | vim_id | vnfd_id |
+--------------------------+--------------------------+----------+--------+--------------------------+---------------------------+
| 90c7f984-f191-49c0-be28- | create_vnf_1d2b83ef-99ab | | ERROR | 0ec2249f-0106-4f67-9da2- | 1d2b83ef-99ab-4999-a724-5 |
| 0f21c74e28e6 | -4999-a724-5860f4047b5a_ | | | e98657246ab2 | 860f4047b5a |
| | f1fe3de4-9829-4a2e-9525- | | | | |
| | 528e73b06132 | | | | |
| afd49fa0-02ab-49aa- | create_vnf_87cde57c- | | ERROR | 0ec2249f-0106-4f67-9da2- | 87cde57c-f4b7-40f3-867e- |
| 90d4-c350fd883c16 | f4b7-40f3-867e-28ed0b771 | | | e98657246ab2 | 28ed0b771358 |
| | 358_f1fe3de4-9829-4a2e-9 | | | | |
| | 525-528e73b06132 | | | | |
+--------------------------+--------------------------+----------+--------+--------------------------+---------------------------+
gongysh@ubuntu64:/opt/stack/tacker/samples/tosca-templates$ tacker ns-list
+--------------------------------------+------+--------------------------------------+------------------------------+--------+
| id | name | nsd_id | mgmt_urls | status |
+--------------------------------------+------+--------------------------------------+------------------------------+--------+
| 19e44435-0cc1-413a-b953-52ddc02c6406 | ns | aa5e0eb9-2c97-4836-ac42-a2abd88169cd | {'VNF2': None, 'VNF1': None} | ACTIVE |
+--------------------------------------+------+--------------------------------------+------------------------------+--------+

Tung Doan (tungdoan)
Changed in tacker:
status: New → Confirmed
Revision history for this message
jiangxing (jiangxing) wrote :

Should check the vnfs' status after ns_create in ns_db.create_ns_post,like this:

        vnf_status = []
        if len(output) > 0:
            for vnfd_name, vnfd_val in iteritems(vnfd_dict):
                for instance in vnfd_val['instances']:
                    if 'mgmt_url_' + instance in output:
                        mgmt_urls[instance] = ast.literal_eval(
                            output['mgmt_url_' + instance].strip())
                        vnf_ids[instance] = output['vnf_id_' + instance]
                        vnf_status.append(output["status_" + instance])
            vnf_ids = str(vnf_ids)
            mgmt_urls = str(mgmt_urls)

        if not vnf_ids:
            vnf_ids = None
        if not mgmt_urls:
            mgmt_urls = None
        status = constants.ACTIVE if mistral_obj.state == 'SUCCESS' \
            else constants.ERROR
        if vnf_status:
            if constants.ERROR in vnf_status:
                status = constants.ERROR

But how to process the vnf's status which is PENDING_CREATE should be more complex, we think need a notification from vnfm to nfvo after the vnf's ACTIVE.

dharmendra (dharmendra-kushwaha)
Changed in tacker:
importance: Undecided → Medium
milestone: none → queens-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.