Bug 1132408

Created attachment 929157 [details]
10.35.160.121_keystone.pp.log

I think It's the same issue - happened with staypuft on the controllers when attempted to deploy HA-nova --> It seems that puppet failed to run the command 'keystone-manage db_sync'  and because of that the deployment failed.   

When I ran the command 'keystone-manage db_sync' manually on the controllers it worked fine, then re-run puppet agent and the deployment finished successfully. 

openstack-puppet-modules-2014.1-20.2.el6ost.noarch 


/var/log/messages :
------------------
Aug 21 08:57:53 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Quickstack::Firewall::Keystone/Firewall[001 keystone incoming]/ensure) created
Aug 21 09:59:43 maca25400702877.example.com puppet-agent[3861]: /tmp/ha-all-in-one-util.bash i_am_vip 192.168.0.95 || /tmp/ha-all-in-one-util.bash property_exists keystone returned 1 instead of one of [0]
Aug 21 09:59:43 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Quickstack::Pacemaker::Keystone/Exec[i-am-keystone-vip-OR-keystone-is-up-on-vip]/returns) change from notrun to 0 failed: /tmp/ha-all-in-one-util.bash i_am_vip 192.168.0.95 || /tmp/ha-all-in-one-util.bash property_exists keystone returned 1 instead of one of [0]
Aug 21 09:59:43 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]) Dependency Exec[i-am-keystone-vip-OR-keystone-is-up-on-vip] has failures: true
Aug 21 09:59:43 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]) Skipping because of failed dependencies
Aug 21 09:59:44 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]) Failed to call refresh: keystone-manage db_sync returned 1 instead of one of [0]
Aug 21 09:59:44 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]) keystone-manage db_sync returned 1 instead of one of [0]
Aug 21 09:59:44 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone/Exec[keystone-manage pki_setup]) Dependency Exec[i-am-keystone-vip-OR-keystone-is-up-on-vip] has failures: true
Aug 21 09:59:44 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone/Exec[keystone-manage pki_setup]) Skipping because of failed dependencies
Aug 21 09:59:45 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone/Exec[keystone-manage pki_setup]) Triggered 'refresh' from 27 events
Aug 21 09:59:45 maca25400702877.example.com puppet-agent[3861]: (/Stage[main]/Keystone/Service[keystone]) Dependency Exec[i-am-keystone-vip-OR-keystone-is-up-on-vip] has failures: true

(In reply to Omri Hochman from comment #3)
> I think It's the same issue - happened with staypuft on the controllers when
> attempted to deploy HA-nova --> It seems that puppet failed to run the
> command 'keystone-manage db_sync'  and because of that the deployment
> failed.   
> 

What I had was : https://bugzilla.redhat.com/show_bug.cgi?id=1132155

(In reply to Ofer Blaut from comment #0)
> Created attachment 929156 [details]
> error file1
> 
> Description of problem:
> 
> 
> 
> 
> 10.35.160.121_keystone.pp:                        [ ERROR ]          
> Applying Puppet manifests                         [ ERROR ]
> 
> ERROR : Error appeared during Puppet run: 10.35.160.121_keystone.pp
> err: /Stage[main]/Keystone::Db::Sync/Exec[keystone-manage db_sync]: Failed
> to call refresh: keystone-manage db_sync returned 1 instead of one of [0] at
> /var/tmp/packstack/76c7c7b1302a49ab988019925266f5fb/modules/keystone/
> manifests/db/sync.pp:11
> 
> 
> 
> Re-run packstack failed on
> 
> 
> Applying 10.35.160.121_cinder.pp
> 10.35.160.121_keystone.pp:                        [ ERROR ]          
> Applying Puppet manifests                         [ ERROR ]
> 
> ERROR : Error appeared during Puppet run: 10.35.160.121_keystone.pp
> err: /Stage[main]/Keystone::Roles::Admin/Keystone_role[_member_]: Could not
> evaluate: Execution of '/usr/bin/keystone --os-endpoint
> http://127.0.0.1:35357/v2.0/ role-list' returned 1: An unexpected error
> prevented the server from fulfilling your request. (HTTP 500)
> You will find full trace in log
> /var/tmp/packstack/20140821-122801-B0v0cx/manifests/10.35.160.121_keystone.
> pp.log
> Please check log file
> /var/tmp/packstack/20140821-122801-B0v0cx/openstack-setup.log for more
> information
> 
> 
> 
> Version-Release number of selected component (if applicable):
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:

Provision host with foreman and don't run YUM update

check rpm -qa | grep facter ( check it is lower than 1.7 )
check rpm -qa | grep puppet ( chek it is 2.75 )

> 1.  packstack --gen-answer-file=RHOS-Controller
> 2. packstack --answer-file=RHOS-Controller
> 3.
> 
> Actual results:
> 
> 
> Expected results:
> 
> 
> Additional info:

after clean installation

[root@cougar16 yum.repos.d]# rpm -qa | grep facter
facter-1.6.18-3.el6.x86_64



After packstack 

[root@cougar16 ~]# rpm -qa | grep facter
facter-1.7.4-1.el6.x86_64
[root@cougar16 ~]# rpm -qa | grep puppet

puppet-3.6.2-1.1.el6.noarch



Verified 

openstack-packstack-puppet-2014.1.1-0.40.dev1239.el6ost.noarch

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1124.html