cron trigger failed on Authorization failed in stack-update when using resource-signal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Triaged
|
Low
|
Unassigned |
Bug Description
step for reproduce:
1) create stack with the next template:
heat_template_
resources:
noop_wf:
type: OS::Mistral:
properties:
name: "noop_wf"
type: direct
tasks:
- name: nothing
action: std.noop
Api: heat stack-create -f stak1.yaml stack1
2) create stack with the next template:
heat_template_
resources:
scaling_wf:
type: OS::Mistral:
properties:
name: { "list_join": ["_", [ "check_
type: direct
input:
stack_id: {STACK_ID_FROM_1}
tasks:
- name: get_stack_
action: heat.stacks_get stack_id=<% $.stack_id %>
- name: update_stack
action: heat.stacks_update
input:
Api: heat stack-create -f stak2.yaml stack2
3)run heat resource-signal stack2 scaling_wf
when signaling to scaling_wf stack update will be triggered from mistral.
This bug happened because : security.
In some point in this step (/usr/local/
Changed in mistral: | |
status: | New → Triaged |
importance: | Undecided → Low |
hi Limor,
Can you provide scaleout_ template( f1 in your case) to reproduce the bug