Skip to content

ensure soledad server has access to x509::variables

elijah requested to merge elijah/platform:bugfix/soledad into develop

the file /etc/default/soledad is created by default-soledad.erb:

# this file is managed by puppet
START=yes
CERT_PATH=<%= scope.lookupvar('x509::variables::certs') %>/<%= scope.lookupvar('site_config::params::cert_name') %>.crt
PRIVKEY_PATH=<%= scope.lookupvar('x509::variables::keys') %>/<%= scope.lookupvar('site_config::params::cert_name') %>.key
HTTPS_PORT=<%=@soledad_port%>

but soledad/manifests/server.pp does not include x509::variables, so /etc/default/soledad looked like this:

# this file is managed by puppet
START=yes
CERT_PATH=/leap.crt
PRIVKEY_PATH=/leap.key
HTTPS_PORT=2323

not good! I have only seen this on colnodo, i don't know why it doesn't show up on other servers.

this should be cherry picked into master, unless there is some other way to fix the problem.

Merge request reports