Description of problem:
The neutron-server-opendaylight container is based off "neutron-base" docker image instead of "neutron-server" container image. This causes one or more packages to be missing, including httpd. This causes SSL/TLS deployments to fail when httpd is attempted to be configured. Somehow with regular deployments there are no failures and neutron-server starts. Not sure how this is possible without httpd. Going to investigate that further.
Failure with SSL/TLS deployment:
"Error: Could not set 'file' on ensure: No such file or directory - /etc/httpd/conf.modules.d/mime.conf20180422-12-1dfsjky.lock at /etc/puppet/modules/apache/manifests/mod/mime.pp:10",
"No such file or directory - /etc/httpd/conf.modules.d/mime.conf20180422-12-1dfsjky.lock",
"Error: /Stage[main]/Apache::Mod::Mime/File[mime.conf]/ensure: change from absent to file failed: Could not set 'file' on ensure: No such file or directory - /etc/httpd/conf.modules.d/mime.conf20180422-12-1dfsjky.lock at /etc/puppet/modules/apache/manifests/mod/mime.pp:10",
After some more investigation this only fails in SSL/TLS because paste server is still used for neutron-server, and httpd is only used for TLS proxy:
Now the question is, is this correct? I thought services were supposed to move to httpd. Nova and other services are running as part of httpd, but neutron-server (and possibly other neutron agents) are still starting as paste. Brent can you answer this for us?
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.