Resources with custom FnGetAtt don't populate attributes on resource-show
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Unassigned |
Bug Description
Resources with custom FnGetAtt generally bypass self.attributes since their attribute schemas are dynamic (software deployments, template resources, resource groups)
This means that a resource-show on these resources will return 'null' as the value for any defined attribute.
For example, an OS::Heat:
| | "deploy_stdout": null, |
| | "deploy_stderr": null, |
| | "deploy_
| | }
however doing a heat deployment-show with display actual values for deploy_stdout etc
Likely solutions would be:
1. modify heat.engine.
2. modify these resources to populate self.attributes with a dynamic schema, and remove their custom FnGetAtt functions
2. may require more effort/magic, but it could also be the basis for fixing bug 1464628
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in heat: | |
assignee: | nobody → Kairat Kushaev (kkushaev) |
Changed in heat: | |
status: | Triaged → In Progress |
Changed in heat: | |
assignee: | Kairat Kushaev (kkushaev) → Angus Salkeld (asalkeld) |
Changed in heat: | |
assignee: | Angus Salkeld (asalkeld) → Kairat Kushaev (kkushaev) |
tags: | added: kilo-backport-potential |
Changed in heat: | |
milestone: | none → liberty-3 |
Changed in heat: | |
milestone: | liberty-3 → liberty-rc1 |
tags: | removed: kilo-backport-potential |
Changed in heat: | |
milestone: | next → mitaka-1 |
tags: | removed: liberty-rc-potential |
tags: | added: liberty-backport-potential |
Changed in heat: | |
milestone: | mitaka-1 → mitaka-2 |
Changed in heat: | |
milestone: | mitaka-2 → mitaka-3 |
Changed in heat: | |
milestone: | mitaka-3 → newton-1 |
no longer affects: | heat/kilo |
Changed in heat: | |
milestone: | newton-1 → next |
status: | In Progress → Triaged |
Fix proposed to branch: master /review. openstack. org/206098
Review: https:/