puppet apply sometimes fails with: Could not set 'directory on ensure: File exists - /var/lib/puppet/facts

[meizhifang]

  We use packstack to setup newly openstack, but sometimes it fails with errors :

 example1>err: /File[/var/lib/puppet/facts]/ensure: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/facts
Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/facts

example2>err: /File[/var/lib/puppet/facts]/ensure: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/state
Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/state

example3>err: /File[/var/lib/puppet/facts]/ensure: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/ssl
Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: File exists - /var/lib/puppet/ssl

[Christian Berendt (berendt)]

Same here with a different directory. After re-starting packstack everything is working like expected.

10.0.2.15_prescript.pp: [ ERROR ]
Applying Puppet manifests [ ERROR ]

ERROR : Error appeared during Puppet run: 10.0.2.15_prescript.pp
Error: Could not set 'directory' on ensure: File exists - /var/lib/puppet/lib

# rpm -q openstack-packstack-puppet
openstack-packstack-puppet-2014.2-0.13.dev1395.gaabe0a2.el7.centos.noarch

# rpm -q openstack-packstack
openstack-packstack-2014.2-0.13.dev1395.gaabe0a2.el7.centos.noarch

[Ivan Chavero (imcsk8) (ichavero-ichavero)]

This is an automated cleanup. This bug report got closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce it, please:
* reopen the bug report (set to status "New")
* AND add the steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (TRUNK, TRUNK).
  Valid example: CONFIRMED FOR: TRUNK