Pulp

Description of problem:
Updating from Alpha I've encountered a syntax error in `/etc/httpd/conf.d/pulp.conf`
It seems to be caused by the wildcard not being able to match anything in the target directory of the Include statement:
# line53
<VirtualHost :80>
Include /etc/pulp/vhosts80/.conf
</VirtualHost>

A simple workaround is to create a dummy config file:
sudo touch /etc/pulp/vhosts80/empty.conf

Version-Release number of selected component (if applicable):
pulp-server-2.4.0-0.9.beta.git.71.8eb429a.fc20.noarch

How reproducible:
Always

Steps to Reproduce:
1. install pulp-server
2. systemctl restart httpd.service

Actual results:

1. service fails to start due to config file "syntax" error:
   [buildbot@dhcp131-12 workdir]$ sudo systemctl status httpd.service
   httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled)
   Active: failed (Result: exit-code) since Thu 2014-04-24 05:10:42 EDT; 3min 39s ago
   Process: 11297 ExecStop=/bin/kill -WINCH ${MAINPID} (code=exited, status=0/SUCCESS)
   Process: 11294 ExecStart=/usr/sbin/httpd $OPTIONS -DFOREGROUND (code=exited, status=1/FAILURE)
   Main PID: 11294 (code=exited, status=1/FAILURE)
   Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec"

Apr 24 05:10:42 dhcp131-12.brq.redhat.com systemd[1]: Starting The Apache HTTP Server...
Apr 24 05:10:42 dhcp131-12.brq.redhat.com httpd[11294]: httpd: Syntax error on line 353 of /etc/httpd/conf/httpd.conf: Syntax error on line 54 of /etc/httpd/conf.d/pulp.conf: No matches for the wildcard '*.conf' in '/e...nal if required)
Apr 24 05:10:42 dhcp131-12.brq.redhat.com systemd[1]: httpd.service: main process exited, code=exited, status=1/FAILURE
Apr 24 05:10:42 dhcp131-12.brq.redhat.com systemd[1]: Failed to start The Apache HTTP Server.
Apr 24 05:10:42 dhcp131-12.brq.redhat.com systemd[1]: Unit httpd.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

Expected results:

1. httpd service ok to start

Additional info:

+ This bug was cloned from Bugzilla Bug #1090835 +