either u donot install cinder or configure less lvm volume ..bydefault its 20gb

Could you post the details of server resources you used? It seems the service stops responding and this is possibly due to the lack of RAM!!

Hello I get a similar issue with ollinone on CentOS 7.3.1611 installed in Virtulabox with 6GB RAM and 20 GB Disk

Preparing Puppet manifests [ DONE ] Copying Puppet modules and manifests [ DONE ] Applying 10.0.2.15_controller.pp 10.0.2.15_controller.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 10.0.2.15_controller.pp Error: Failed to apply catalog: Execution of '/usr/bin/openstack volume type list --quiet --format csv --long' returned 1: Unable to establish connection to http://10.0.2.15:8776/v2/cf616cd09d044d83b7a595a2af5851f2/types?is_public=None (http://10.0.2.15:8776/v2/cf616cd09d04...): HTTPConnectionPool(host='10.0.2.15', port=8776): Max retries exceeded with url: /v2/cf616cd09d044d83b7a595a2af5851f2/types?is_public=None (Caused by NewConnectionError('<requests.packages.urllib3.connection.httpconnection 0x32e1390="" at="" object="">: Failed to establish a new connection: [Errno 111] Connection refused',)) (tried 22, for a total of 170 seconds) You will find full trace in log /var/tmp/packstack/20170321-221357-Ryx6Vn/manifests/10.0.2.15_controller.pp.log Please check log file /var/tmp/packstack/20170321-221357-Ryx6Vn/openstack-setup.log for more information Additional information: * A new answerfile was created in: /root/packstack-answers-20170321-221358.txt * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for s</requests.packages.urllib3.connection.httpconnection>

someone was able to solve this problem please ?

I had 8 gb of Ram, 4 cores, 1 nic (external), hyper-v (win 10) with Centos 7 1611 build (minimal install). The same issue I can see with RedHat 7.3 activated developers subscription. Nova-scheduler.log shows so many exceptions related with Python 2.7 after install failure. Tried to update it to 3.5 ver. but did not help to solve this issue. Looks like issue is not in hypervisor or os. Any ideas?

4 cores, 6GB RAM, 100G Disk also suffer this pain.

2017-08-31 07:42:58::ERROR::run_setup::1027::root:: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 1002, in main single_step_aio_install(options, logFile) File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 769, in single_step_aio_install single_step_install(options, logFile) File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 800, in single_step_install _main(options, answerfilepath, logFile) File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 678, in _main runSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/run_setup.py", line 645, in runSequences controller.runAllSequences() File "/usr/lib/python2.7/site-packages/packstack/installer/setup_controller.py", line 81, in runAllSequences sequence.run(config=self.CONF, messages=self.MESSAGES) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 109, in run step.run(config=config, messages=messages) File "/usr/lib/python2.7/site-packages/packstack/installer/core/sequences.py", line 50, in run self.function(config, messages) File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 214, in apply_puppet_manifest wait_for_puppet(currently_running, messages) File "/usr/lib/python2.7/site-packages/packstack/plugins/puppet_950.py", line 128, in wait_for_puppet validate_logfile(log) File "/usr/lib/python2.7/site-packages/packstack/modules/puppet.py", line 107, in validate_logfile raise PuppetError(message) PuppetError: Error appeared during Puppet run: 10.140.253.30_controller.pp Error: Failed to apply catalog: Command: 'openstack ["volume type", "list", "--quiet", "--format", "csv", "--long"]' has been running for more than 40 seconds (tried 3, for a total of 170 seconds) You will find full trace in log /var/tmp/packstack/20170831-070418-2MHnaM/manifests/10.140.253.30_controller.pp.log