Description of problem: I am facing exact same BUG-947421 on Fedora 20 when I try to execute the command...(the below is the entire command line report of my execution) ===================================== [root@fedora131 conf.d]# packstack --answer-file /root/answers.txt Welcome to Installer setup utility Installing: Clean Up [ DONE ] Setting up ssh keys [ DONE ] Discovering hosts' details [ DONE ] Adding pre install manifest entries [ DONE ] Installing time synchronization via NTP [ DONE ] Adding MySQL manifest entries [ DONE ] Adding QPID manifest entries [ DONE ] Adding Keystone manifest entries [ DONE ] Adding Glance Keystone manifest entries [ DONE ] Adding Glance manifest entries [ DONE ] Installing dependencies for Cinder [ DONE ] Adding Cinder Keystone manifest entries [ DONE ] Adding Cinder manifest entries [ DONE ] Checking if the Cinder server has a cinder-volumes vg[ DONE ] Adding Nova API manifest entries [ DONE ] Adding Nova Keystone manifest entries [ DONE ] Adding Nova Cert manifest entries [ DONE ] Adding Nova Conductor manifest entries [ DONE ] Adding Nova Compute manifest entries [ DONE ] Adding Nova Scheduler manifest entries [ DONE ] Adding Nova VNC Proxy manifest entries [ DONE ] Adding Nova Common manifest entries [ DONE ] Adding Openstack Network-related Nova manifest entries[ DONE ] Adding Neutron API manifest entries [ DONE ] Adding Neutron Keystone manifest entries [ DONE ] Adding Neutron L3 manifest entries [ DONE ] Adding Neutron L2 Agent manifest entries [ DONE ] Adding Neutron DHCP Agent manifest entries [ DONE ] Adding Neutron LBaaS Agent manifest entries [ DONE ] Adding Neutron Metadata Agent manifest entries [ DONE ] Adding OpenStack Client manifest entries [ DONE ] Adding Horizon manifest entries [ DONE ] Adding Swift Keystone manifest entries [ DONE ] Adding Swift builder manifest entries [ DONE ] Adding Swift proxy manifest entries [ DONE ] Adding Swift storage manifest entries [ DONE ] Adding Swift common manifest entries [ DONE ] Adding Provisioning manifest entries [ DONE ] Adding Ceilometer manifest entries [ DONE ] Adding Ceilometer Keystone manifest entries [ DONE ] Adding Nagios server manifest entries [ DONE ] Adding Nagios host manifest entries [ DONE ] Adding post install manifest entries [ DONE ] Preparing servers [ DONE ] Installing Dependencies [ DONE ] Copying Puppet modules and manifests [ DONE ] Applying 192.168.229.131_prescript.pp 192.168.229.131_prescript.pp: [ DONE ] Applying 192.168.229.131_ntpd.pp 192.168.229.131_ntpd.pp: [ DONE ] Applying 192.168.229.131_mysql.pp Applying 192.168.229.131_qpid.pp 192.168.229.131_mysql.pp: [ DONE ] 192.168.229.131_qpid.pp: [ DONE ] Applying 192.168.229.131_keystone.pp Applying 192.168.229.131_glance.pp Applying 192.168.229.131_cinder.pp 192.168.229.131_keystone.pp: [ DONE ] 192.168.229.131_cinder.pp: [ DONE ] 192.168.229.131_glance.pp: [ DONE ] Applying 192.168.229.131_api_nova.pp 192.168.229.131_api_nova.pp: [ DONE ] Applying 192.168.229.131_nova.pp 192.168.229.131_nova.pp: [ DONE ] Applying 192.168.229.131_neutron.pp 192.168.229.131_neutron.pp: [ DONE ] Applying 192.168.229.131_osclient.pp Applying 192.168.229.131_horizon.pp 192.168.229.131_osclient.pp: [ DONE ] 192.168.229.131_horizon.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 192.168.229.131_horizon.pp Error: /Stage[main]/Apache::Service/Service[httpd]: Failed to call refresh: Could not start Service[httpd]: Execution of '/sbin/service httpd start' returned 1: You will find full trace in log /var/tmp/packstack/20141216-161902-xANf3C/manifests/192.168.229.131_horizon.pp.log Please check log file /var/tmp/packstack/20141216-161902-xANf3C/openstack-setup.log for more information Additional information: * Did not create a cinder volume group, one already existed * File /root/keystonerc_admin has been created on OpenStack client host 192.168.229.131. To use the command line tools you need to source the file. * NOTE : A certificate was generated to be used for ssl, You should change the ssl certificate configured in /etc/httpd/conf.d/ssl.conf on 192.168.229.131 to use a CA signed cert. * To access the OpenStack Dashboard browse to https://192.168.229.131/dashboard. Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://192.168.229.131/nagios username : nagiosadmin, password : 56383539d78a4697 ============================================== when I try to debug the problem I found exact same findings reported in BUG-947421, Unfortunately this defect was CLOSED as not reproducible / Environment was not available. How shall I make this httpd service run? As a workaround I try to comment the below lines from "/etc/httpd/conf.d/ssl.conf" file # SSLSessionCache shmcb:/var/cache/mod_ssl/scache(512000) # SSLMutex default And try to start the httpd service then service gets started with success, but then I am failed to see the Dashboard..... And if I try to execute the "packstack --answer-file /root/answers.txt" command again then ssl.conf file gets overwritten and the changes which we do gets vanished ....and we get the same error that is 192.168.229.131_horizon.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] So is there any way to get Dashboard ? and how this packstack utlity shall pickup my ssl.conf changes...is there any way? I also check the module "mod_socache_shmcb module" is getting successfully loaded in /etc/httpd/conf.modules.d/00-base.conf file Please help me in resolving this issue ASAP.. Thanks in advance for your help. Version-Release number of selected component (if applicable): Fedora 20 How reproducible: Steps to Reproduce: 1. Install Fedora 20 ( Linux fedora131.ops.com 3.17.6-200.fc20.x86_64 #1 SMP Mon Dec 8 15:21:05 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) 2. Installed openstack packages by issuing below command yum install -y openstack-packstack 3. Created ssh key by issuing ssh-keygen command 4. created answers file by issuing packstack --gen-answer-file /root/answers.txt 5. Configured this answers file for NTP and Horizen setup 6. executed below command for openstack installation packstack --answer-file /root/answers.txt Actual results: The packstack utility failed to install openstack and displayed below failure results --------------------- 192.168.229.131_horizon.pp: [ ERROR ] Applying Puppet manifests [ ERROR ] ERROR : Error appeared during Puppet run: 192.168.229.131_horizon.pp Error: /Stage[main]/Apache::Service/Service[httpd]: Failed to call refresh: Could not start Service[httpd]: Execution of '/sbin/service httpd start' returned 1: You will find full trace in log /var/tmp/packstack/20141216-161902-xANf3C/manifests/192.168.229.131_horizon.pp.log Please check log file /var/tmp/packstack/20141216-161902-xANf3C/openstack-setup.log for more information Additional information: * Did not create a cinder volume group, one already existed * File /root/keystonerc_admin has been created on OpenStack client host 192.168.229.131. To use the command line tools you need to source the file. * NOTE : A certificate was generated to be used for ssl, You should change the ssl certificate configured in /etc/httpd/conf.d/ssl.conf on 192.168.229.131 to use a CA signed cert. * To access the OpenStack Dashboard browse to https://192.168.229.131/dashboard. Please, find your login credentials stored in the keystonerc_admin in your home directory. * To use Nagios, browse to http://192.168.229.131/nagios username : nagiosadmin, password : 56383539d78a4697 --------------------- Expected results: Openstack should get install and user should be able to view Open Stack Dashboard with all services running with success... Additional info:
I think this is because of non-existing "/var/cache/mod_ssl/scache". In Fedora, we are using following SSLSessionCache by default: SSLSessionCache shmcb:/run/httpd/sslcache(512000) If you supply different directory to your httpd.conf (or if another utility does that), you should created that directory manually (or the utility should do that for you).
(In reply to Jan Kaluža from comment #1) > I think this is because of non-existing "/var/cache/mod_ssl/scache". In > Fedora, we are using following SSLSessionCache by default: > > SSLSessionCache shmcb:/run/httpd/sslcache(512000) > > If you supply different directory to your httpd.conf (or if another utility > does that), you should created that directory manually (or the utility > should do that for you). Thanks for reply ...but I got confused here..you mean to say that I need to create a new directory for "/run/httpd/sslcache(512000)"..? at new location (instead of /run) and supply that path in the ssl.conf file?