Unable to install the capsule on a fresh machine.
I encountered an error while installing a capsule on a clean box with
Katello 3.1: *SSLCertificateChainFile: file
'/var/lib/puppet/ssl/ca/ca_crt.pem' does not exist or is empty.*
.
[ WARN 2016-09-09 15:39:43 verbose]
In my production deployment I've noticed that katello can't talk to its own
smart proxy, but can communicate with the capsules. I'm still trying to
debug it, but I haven't had any success.
I think the root of the problem (and I mention it in the ticket) is the
software is designed to assume
t; Thanks! That worked. Here's what I did:
>
> cd /etc/foreman
> cp proxy_ca.pem proxy_ca_bkp.pem
> cp /root/ssl-build/katello-default-ca.crt ./proxy_ca.pem
>
> Regards,
> Prasun
>
> On Mon, Sep 19, 2016 at 8:57 PM, Danny Kimsey <deki...@gmail.com
> > wrote:
>
&g
On Monday, September 19, 2016 at 6:25:04 AM UTC-5, prasu...@gmail.com wrote:
This issue still exists for Katello 3.1. Without the workaround mentioned
by Claran, it's not possible to use custom SSL certificates for katello.
I too have run into this issue. Copying the default-ca into the
me errors.
>
> On Mon, Sep 19, 2016 at 1:25 PM, Danny Kimsey <dekim...@gmail.com> wrote:
>
>>
>> On Monday, September 19, 2016 at 6:25:04 AM UTC-5, prasu...@gmail.com
>> wrote:
>> This issue still exists for Katello 3.1. Without the workaround mentioned
>> by Cl
External certs don't work correctly. Its an outstanding issue. Somewhere on
foreman's issue tracker is a ticket talking about this. I outlined a few
things I did, but found out that at least one step breaks another further
downstream.
Basically comes down to the fact that Katello needs to
.uk>
wrote:
>
>
> On Sunday, November 20, 2016 at 12:54:51 PM UTC-5, Danny Kimsey wrote:
>
> External certs don't work correctly. Its an outstanding issue. Somewhere
> on foreman's issue tracker is a ticket talking about this. I outlined a few
> things I did, but found out th
I recall testing it specifically with Katello and there were some bits that
were painful. In particular I believe it [plugin's reporting] was /very/
slow. Definitely something I'll be looking into in the future and I'll
update you if I have anything useful.
--
You received this message