Polling for server metadata causes engine to log warnings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Zane Bitter | ||
Kilo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When os-collect-config is configured to poll heat's API for server metadata, we see warnings at regular intervals in the engine log like this:
2015-10-19 13:22:34.380 WARNING heat.engine.
I think this is because the polling identity is a stack domain user, thus can't find the Instance created by the stack while evaluating a custom constraint while we instantiate the stack object while servicing the request.
This is a bit distracting as you get a lot of these in large deployments with lots of instances polling heat - we should find a way to either fix the problem (conditionally evaluate custom constraints only on create/
Changed in heat: | |
assignee: | nobody → Zane Bitter (zaneb) |
status: | New → In Progress |
importance: | Undecided → Critical |
importance: | Critical → High |
tags: | added: kilo-backport-potential liberty-backport-potential |
It looks that heat engine asks about VM created in heat created project not in project of user who deployed stack.