OS::stack_id output of nested stack not passed to parent stack correctly

Bug #1429154 reported by Johannes Grassler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Tatiana Kholkina

Bug Description

According to Heat's documentation it should be possible to return a resource ID
as OS::stack_id output from a nested stack, in order to be able use one of the
resources in the nested stack directly from the parent stack:

http://docs.openstack.org/developer/heat/template_guide/composition.html#making-your-template-resource-more-transparent

We tried this and it fails, since we get what looks like some kind of
serialization artifact instead of the desired resource UUID (a neutron Port ID
in this case). A minimum example to provoke this problem is attached. The
problem is caused by the get_resource lookup in test.yaml:40.

Steps to reproduce:

1. tar -C /tmp -xf test_stackid.tar
2. heat stack-create -e /tmp/test_stackid/env.yaml -f /tmp/test_stackid/test.yaml -P key_name=<nova key name> test_stackid

Stack creation will fail with the following stack_status_reason:

  Resource CREATE failed: BadRequest: Port id arn:openstack:heat::b23a1ea1a6d6481681822ab6242ee703:stacks
  /test_stackid-test_port-3ju4vbax45jz/e2e69284-c9e6-45bc-af62-7c4e414610c4 could not be found. (HTTP 400)

Revision history for this message
Johannes Grassler (jgr-launchpad) wrote :
Revision history for this message
Steve Baker (steve-stevebaker) wrote : Re: [Bug 1429154] [NEW] OS::stack_id output of nested stack not passed to parent stack correctly

On 07/03/15 03:42, Johannes Grassler wrote:
> Public bug reported:
>
> According to Heat's documentation it should be possible to return a resource ID
> as OS::stack_id output from a nested stack, in order to be able use one of the
> resources in the nested stack directly from the parent stack:
>
> http://docs.openstack.org/developer/heat/template_guide/composition.html
> #making-your-template-resource-more-transparent
>
This documentation should say that OS::stack_id is available in the
(upcoming) Kilo release of Heat. What version of Openstack is your cloud?

Revision history for this message
Johannes Grassler (jgr-launchpad) wrote :

We are running Juno, so I guess that means the bug is in the documentation.

(The example shown in the documentation even specifies heat_template_version: 2014-10-16, which is the Juno one).

Revision history for this message
Steve Baker (steve-stevebaker) wrote :

The fix is to clarify in the docs that OS::stack_id was added in Kilo

Changed in heat:
status: New → Triaged
importance: Undecided → Medium
Changed in heat:
assignee: nobody → Tetiana Lashchova (tlashchova)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/166907

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

Reviewed: https://review.openstack.org/166907
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=d06b6c098ba7f25ef8410a83b764c506f2955d08
Submitter: Jenkins
Branch: master

commit d06b6c098ba7f25ef8410a83b764c506f2955d08
Author: Tetiana Lashchova <email address hidden>
Date: Mon Mar 23 18:03:48 2015 +0200

    Add note that OS::stack_id is available since Kilo

    Change-Id: Iccf17494aa9446ebc83b0a8d5cac07594f8cd6a0
    Closes-Bug: #1429154

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
milestone: none → kilo-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-rc1 → 2015.1.0
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.