Comment 1 for bug 1674770

Revision history for this message
Steven Hardy (shardy) wrote : Re: Timeout passed to overcloud deploy not effective

AFAICT the timeout is repected directly via heat:

(undercloud) [stack@undercloud ~]$ heat stack-create test -f hosts-config.yaml -e hosts_env.yaml -t 333

(undercloud) [stack@undercloud ~]$ heat stack-show test | grep timeout
WARNING (shell) "heat stack-show" is deprecated, please use "openstack stack show" instead
| timeout_mins | 333

And also via tripleoclient:

openstack overcloud deploy --templates --timeout 333

| timeout_mins | 333

Could this be an issue specific to CI, e.g we've messed up the deploy arguments?