Debugging show, that issue was related with incorrect deploying:
all nodes except node-3 have heat-api process started with correct configuration.
But heat-api on node-3 in start log show, that all specified in config options are None, i.e. it started without configuration file.
I suppose, that root cause is: wrong order (may unexpected fail during deployment), which lead to starting heat-api before configuration file was created (heat.conf).
Victor will post detailed logs, which demonstrate my words.
Debugging show, that issue was related with incorrect deploying:
all nodes except node-3 have heat-api process started with correct configuration.
But heat-api on node-3 in start log show, that all specified in config options are None, i.e. it started without configuration file.
I suppose, that root cause is: wrong order (may unexpected fail during deployment), which lead to starting heat-api before configuration file was created (heat.conf).
Victor will post detailed logs, which demonstrate my words.