b1197b3819
Using sudo -u to change users for a command can fail if sudo thinks it needs a controlling TTY as part of its authentication. Since this is the default config, that means that whenever the command is run in an environment that does not have a TTY (such as from init(1)), sudo will die. su does not care or check for a controlling TTY, so it will succeed as long as it is being run by root (which should be the case for all os-refresh-config elements). Therefore, instead of using sudo -u <username> -- <command> to run commands as other users, use su -s /bin/bash -c "<command>" <username> This will allow things to function in the face of a misconfigured sudo as well as allow commands to run against an account that has been locked out or has a shell that otherwise restricts what commands can be run. Change-Id: I5cc518ce42536a09e9f25c6635e191884aaaef92 |
||
|---|---|---|
| .. | ||
| install.d | ||
| os-refresh-config | ||
| element-deps | ||
| README.md | ||
| svc-map | ||
Run the heat-engine service.
Configuration
Example Heat Metadata:
OpenStack::Config:
heat:
rpc_backend: heat.openstack.common.rpc.impl_kombu
sql_connection: mysql://heatuser:heatpass@mysql.server.foo/heatdb
auth_encryption_key: 0123456789abcdef0123456789abcdef
watch_server_url: http://address.of.watch.service:8003
waitcondition_server_url: http://address.of.wc.service:8000/v1/waitcondition
metadata_server_url: http://addr.of.metadta.service:8000
rabbit:
password: abcdefg
host: address.of.rabbitmq
bind_port: 8001
bind_host: 0.0.0.0