Murano generated heat template does not pass the validation of heat stack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
In Progress
|
Undecided
|
Shi Yan |
Bug Description
When using Queens Murano with Rocky release Heat, application deployment is failed at the stage of server creation validation.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
2019-02-25 12:47:09.557 25037 ERROR heat.engine.
It's working with Queens Heat but not working with Rocky heat is because of such heat change: https:/
And looks the template pushed from Murano does not contain network parameters, so the stack creation failed. The template from Murano is like:
"
},
{
}
],
}
}
Maybe I have some misunderstanding here but wonder if we need a fix in murano? or heat?
Changed in murano: | |
status: | New → Invalid |
Dig a bit murano code, and still think Murano should fix this.
In murano core library, the "networks" property is actually not passed into heat template. As below:
- $properties:
availability _zone: $.availabilityZone
user_ data: $preparedUserDa ta.data
user_ data_format: $preparedUserDa ta.format ta($region)
name: $.name
flavor: $.flavor
key_name: $.keyname
metadata: $this.getMetada