Welcome to the Packstack setup utility

The installation log file is available at: /var/tmp/packstack/20150506-110452-VfCfYm/openstack-setup.log

Installing:
Clean Up                                             [ ESC[32mDONEESC[0m ]
Setting up ssh keys                                  [ ESC[32mDONEESC[0m ]
Discovering hosts' details                           [ ESC[32mDONEESC[0m ]
Adding pre install manifest entries                  [ ESC[32mDONEESC[0m ]
Preparing servers                                    [ ESC[32mDONEESC[0m ]
Adding AMQP manifest entries                         [ ESC[32mDONEESC[0m ]
Adding MariaDB manifest entries                      [ ESC[32mDONEESC[0m ]
Fixing Keystone LDAP config parameters to be undef if empty[ ESC[32mDONEESC[0m ]
Adding Keystone manifest entries                     [ ESC[32mDONEESC[0m ]
Adding Glance Keystone manifest entries              [ ESC[32mDONEESC[0m ]
Adding Glance manifest entries                       [ ESC[32mDONEESC[0m ]
Adding Cinder Keystone manifest entries              [ ESC[32mDONEESC[0m ]
Checking if the Cinder server has a cinder-volumes vg[ ESC[32mDONEESC[0m ]
Adding Cinder manifest entries                       [ ESC[32mDONEESC[0m ]
Adding Nova API manifest entries                     [ ESC[32mDONEESC[0m ]
Adding Nova Keystone manifest entries                [ ESC[32mDONEESC[0m ]
Adding Nova Cert manifest entries                    [ ESC[32mDONEESC[0m ]
Adding Nova Conductor manifest entries               [ ESC[32mDONEESC[0m ]
Creating ssh keys for Nova migration                 [ ESC[32mDONEESC[0m ]
Gathering ssh host keys for Nova migration           [ ESC[32mDONEESC[0m ]
Adding Nova Compute manifest entries                 [ ESC[32mDONEESC[0m ]
Adding Nova Scheduler manifest entries               [ ESC[32mDONEESC[0m ]
Adding Nova VNC Proxy manifest entries               [ ESC[32mDONEESC[0m ]
Adding Nova Network manifest entries                 [ ESC[32mDONEESC[0m ]
Adding Nova Common manifest entries                  [ ESC[32mDONEESC[0m ]
Adding OpenStack Client manifest entries             [ ESC[32mDONEESC[0m ]
Adding Horizon manifest entries                      [ ESC[32mDONEESC[0m ]
Adding Swift Keystone manifest entries               [ ESC[32mDONEESC[0m ]
Adding Swift builder manifest entries                [ ESC[32mDONEESC[0m ]
Adding Swift proxy manifest entries                  [ ESC[32mDONEESC[0m ]
Adding Swift storage manifest entries                [ ESC[32mDONEESC[0m ]
Adding Swift common manifest entries                 [ ESC[32mDONEESC[0m ]
Adding Provisioning Demo manifest entries            [ ESC[32mDONEESC[0m ]
Adding Provisioning Glance manifest entries          [ ESC[32mDONEESC[0m ]
Adding MongoDB manifest entries                      [ ESC[32mDONEESC[0m ]
Adding Redis manifest entries                        [ ESC[32mDONEESC[0m ]
Adding Ceilometer manifest entries                   [ ESC[32mDONEESC[0m ]
Adding Ceilometer Keystone manifest entries          [ ESC[32mDONEESC[0m ]
Adding Nagios server manifest entries                [ ESC[32mDONEESC[0m ]
Adding Nagios host manifest entries                  [ ESC[32mDONEESC[0m ]
Adding post install manifest entries                 [ ESC[32mDONEESC[0m ]
Installing Dependencies                           [ ESC[0;31mERRORESC[0m ]

ESC[0;31mERROR : Failed to run remote script, stdout: Loaded plugins: fastestmirror, priorities

stderr: Warning: Permanently added '192.168.128.102' (ECDSA) to the list of known hosts.
+ trap t ERR
+ yum install -y puppet hiera openssh-clients tar nc rubygem-json


 One of the configured repositories failed (Unknown),
 and yum doesn't have enough cached data to continue. At this point the only
 safe thing yum can do is fail. There are a few ways to work "fix" this:

     1. Contact the upstream for the repository and get them to fix the problem.

     2. Reconfigure the baseurl/etc. for the repository, to point to a working
        upstream. This is most often useful if you are using a newer
        distribution release than is supported by the repository (and the
        packages for the previous distribution release still work).

     3. Disable the repository, so yum won't use it by default. Yum will then
        just ignore the repository until you permanently enable it again or use
        --enablerepo for temporary usage:

            yum-config-manager --disable <repoid>

     4. Configure the failing repository to be skipped, if it is unavailable.
        Note that yum will try to contact the repo. when it runs most commands,
        so will have to try and fail each time (and thus. yum will be be much
        slower). If it is a very temporary problem though, this is often a nice
        compromise:

            yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
++ t
++ exit 1
ESC[0m
Please check log file /var/tmp/packstack/20150506-110452-VfCfYm/openstack-setup.log for more information
Additional information:
 * Time synchronization installation was skipped. Please note that unsynchronized time on server instances might be problem for some OpenStack components.
 * File /root/keystonerc_admin has been created on OpenStack client host 192.168.128.102. To use the command line tools you need to source the file.
 * To access the OpenStack Dashboard browse to http://192.168.128.102/dashboard .
Please, find your login credentials stored in the keystonerc_admin in your home directory.
 * To use Nagios, browse to http://192.168.128.102/nagios username: nagiosadmin, password: Secret12
 * Note temporary directory /var/tmp/packstack/1f9c94e59c744d3f8e67ef9fa255847d on host 192.168.128.102 was not deleted for debugging purposes.