f662bc35fd
If apache is (re)starting while the chef-client installs the cinder-api
package, it may pick up the package-supplied cinder-wsgi apache2 conf
file before chef-client gets around to disabling it which may result in
apache2 failing due to a non-working configuration.
This changeset eliminates the race by creating an empty configuration
file before installing the software. The solution is based on the
assumption that no reasonably configured package manager will overwrite
an existing, user-created configuration file. The empty configuration
file is left in place to avoid its creation and removal during every
recipe run.
backport: queens
Change-Id: I225a30379820e6e033bcea987fbf1a4db33dbd3a
(cherry picked from commit
|
||
|---|---|---|
| .. | ||
| api.rb | ||
| backup.rb | ||
| cinder-common.rb | ||
| identity_registration.rb | ||
| scheduler.rb | ||
| volume.rb | ||
| volume_driver_lvm.rb | ||