OpenStack Heat

stack_user_project_id is not discoverable by the user

Bug #1413398 reported by Steve Baker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Steve Baker
OpenStack Heat 2015.1.0 "kilo"
Juno
Fix Released
Undecided
Unassigned
OpenStack Heat 2014.2.4

Bug Description

stack_user_project_id is currently never exposed by heat, so the user has no way of discovering what it is.

This has a couple of implications:
- The user can't call the REST API create_software_deployment unless they know the stack_user_project_id of the stack that the server resource belongs to
- user can't do manual cleanup of stack_user_project_id when necessary

Steve Baker (steve-stevebaker)
Changed in heat:
status: New → Triaged
importance: Undecided → Medium
tags: added: juno-backport-potential
Changed in heat:
assignee: nobody → Steve Baker (steve-stevebaker)
milestone: none → kilo-2
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/149080

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/149080
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=007ce91c558d4f815ea2659c6d98c0caf35553a8
Submitter: Jenkins
Branch: master

commit 007ce91c558d4f815ea2659c6d98c0caf35553a8
Author: Steve Baker <email address hidden>
Date: Thu Jan 22 12:29:06 2015 +1300

    Expose stack_user_project_id in stack-show

    stack_user_project_id is currently never exposed by heat, so the user
    has no way of discovering what it is.

    This has a couple of implications:
    - The user can't call the REST API create_software_deployment unless
      they know the stack_user_project_id of the stack that the server
      resource belongs to
    - user can't do manual cleanup of stack_user_project_id when necessary

    This change adds stack_user_project_id to the formatted output of
    the stack-show REST API call.

    Change-Id: I0a2d337401c164eb58dbce63e01f68f98f8d467e
    Closes-Bug: #1413398

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-2 → 2015.1.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (stable/juno)

Fix proposed to branch: stable/juno
Review: https://review.openstack.org/244953

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (stable/juno)

Reviewed: https://review.openstack.org/244953
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=ef1c9e9a780d4eb41beddccd50b99123c5ca2e0c
Submitter: Jenkins
Branch: stable/juno

commit ef1c9e9a780d4eb41beddccd50b99123c5ca2e0c
Author: Steve Baker <email address hidden>
Date: Thu Jan 22 12:29:06 2015 +1300

    Expose stack_user_project_id in stack-show

    stack_user_project_id is currently never exposed by heat, so the user
    has no way of discovering what it is.

    This has a couple of implications:
    - The user can't call the REST API create_software_deployment unless
      they know the stack_user_project_id of the stack that the server
      resource belongs to
    - user can't do manual cleanup of stack_user_project_id when necessary

    This change adds stack_user_project_id to the formatted output of
    the stack-show REST API call.

    Change-Id: I0a2d337401c164eb58dbce63e01f68f98f8d467e
    Closes-Bug: #1413398

tags: added: in-stable-juno
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.