vnfd: availability_zone to specific host fails vnf instantiation

Bug #1481974 reported by Sridhar Ramaswamy on 2015-08-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Low
Rudresh

Bug Description

TOSCA template has availability zone set to specific Nova host using the following snippet,

vdus:
  vdu1:
    id: vdu1
...
    placement_policy:
      availability_zone: nova:nfv-compute-1

Here nfv-compute-1 is the Nova compute node name.

Symptoms:

1) When such a template is instantiated, Tacker VNF stays in "PENDING_CREATE" state for ever.
2) Looking into Heat stack, response shows,

Create_Failed: Resource CREATE failed: Forbidden: Policy doesn't allow compute:create:forced_host to be performed. (HTTP 403) (Request-ID: req-65e26d25-6cad-4fda-94b7-f6e2fa909466)

vdu1
  OS::Nova::Server 1 hour, 50 minutes Create Failed Forbidden: Policy doesn't allow compute:create:forced_host to be performed. (HTTP 403) (Request-ID: req-65e26d25-6cad-4fda-94b7-f6e2fa909466)

Expected behavior:

1) Tacker shouldn't be stuck at PENDING_CREATE ever. It shouldve moved to ERROR state
2) Tacker should allow az forcing to specific Nova compute nodes [1]

[1] https://ask.openstack.org/en/question/49866/policy-doesnt-allow-computecreateforced_host-to-be-performed/

Changed in tacker:
assignee: nobody → vishwanath jayaraman (vishwanathj)
tags: added: liberty-critical
Changed in tacker:
assignee: vishwanath jayaraman (vishwanathj) → Sridhar Ramaswamy (srics-r)
tags: removed: liberty-critical
Changed in tacker:
assignee: Sridhar Ramaswamy (srics-r) → nobody
importance: Medium → Low
sajuptpm (sajuptpm) wrote :

does anybody fixed this issue ?

Rudresh (rudrii) on 2016-09-16
Changed in tacker:
assignee: nobody → Rudresh (rudrii)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers