Created attachment 972336 [details] openstack-setup.log Description of problem: The installation environment is a Hyper-V VM on Windows 8.1 x64. Version-Release number of selected component (if applicable): openstack-packstack-2014.2-0.9.dev1359.g40f3b9d.el7.centos.noarch How reproducible: reproducible. Steps to Reproduce: 1. Install CentOS 7 minimal server 2. yum -y update 3. reboot 4. yum install -y https://rdo.fedorapeople.org/rdo-release.rpm 5. yum install -y openstack-packstack 6. packstack --allinone --debug Actual results: packstack fails at the <ip-address>_cinder.pp manifest. Snippet from <ip-address>_cinder.pp.log: Debug: Exec[cinder type-create iscsi](provider=posix): Executing check 'cinder type-list | grep -qP '\biscsi\b'' Debug: Executing 'cinder type-list | grep -qP '\biscsi\b'' Debug: Exec[cinder type-create iscsi](provider=posix): Executing 'cinder type-create iscsi' Debug: Executing 'cinder type-create iscsi' Error: Command exceeded timeout Wrapped exception: execution expired Error: /Stage[main]/Main/Cinder::Type[iscsi]/Exec[cinder type-create iscsi]/returns: change from notrun to 0 failed: Command exceeded timeout Notice: /Stage[main]/Main/Cinder::Type[iscsi]/Cinder::Type_set[lvm]/Exec[cinder type-key iscsi set volume_backend_name=lvm]: Dependency Exec[cinder type-create iscsi] has failures: true Warning: /Stage[main]/Main/Cinder::Type[iscsi]/Cinder::Type_set[lvm]/Exec[cinder type-key iscsi set volume_backend_name=lvm]: Skipping because of failed dependencies Expected results: packstack should complete successfully, or at least provide a meaningful error message. Additional info:
Created attachment 972337 [details] 192.168.2.99_cinder.pp.log
is there any resolution to this issue yet as I am stuck in installation due to this error
I was seeing these same errors on a bare metal RDO AIO deployment of both Juno and Kilo. Googling "cinder type-create iscsi" suggested that it may be a proxy problem (my box sits behind a proxy). After configuring the no_proxy env var to include the box's own IP, packstack was able to successfully complete.
As explained in comment #3 this issue seems to be related to the configuration of a http proxy. If proxy is required by yum to access the repositories, the recomended way to configure it is to add following line to /etc/yum.conf file: proxy=http://x.x.x.x:xxxx