Ok, progress. I've encoded my cert and key to base64 strings and specified them in my haproxy config, and seem to be getting past the padding error. My issue now, is that I am not seeing the cert/key in /etc/ssl/private on the haproxy host once deployed. I'm thinking specifying the ssl cert/key will work for the Openstack charms now that I've got the encoding part squared away. Still stumped by haproxy though ... can't seem to get it provision the cert/key correctly for the life of me. Possibly there is something else I'm missing here ...
On Sat, Jan 28, 2017 at 1:04 PM, James Beedy <jamesbe...@gmail.com> wrote: > I'm having issues with padding when trying to specify key/cert as config > options for Haproxy, and have experienced the same issue in the past, when > trying to specify key/cert for the Openstack charms. Could someone give an > example of what the correct padding of a base64 encoded ssl cert might look > like in the charm config yaml. > > My charm config looks like this -> http://paste.ubuntu.com/23882917/ > > The error I'm getting is this -> http://paste.ubuntu.com/23882921/ > > Thanks >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
