Re: [foreman-users] Re: Katello 3.0 (Saison) Released

2016-06-16 Thread Prasun Gera
Are the repos the same as they were for the RC releases ? I see that some of the packages from that repo still have rc8 in the name. On Thu, Jun 16, 2016 at 11:30 AM, Duncan Innes wrote: > Yay \o/ great news. > > Congratulations for getting this over the finish line. And

Re: [foreman-users] Re: Katello 3.0 (Saison) Released

2016-06-16 Thread Prasun Gera
he > name? > > On Thu, Jun 16, 2016 at 2:02 PM, Prasun Gera <prasun.g...@gmail.com> > wrote: > >> Are the repos the same as they were for the RC releases ? I see that some >> of the packages from that repo still have rc8 in the name. >> >> On Thu, Jun 16, 2

Re: [foreman-users] Re: RestClient::SSLCertificateNotVerified after custom cert setup

2016-09-19 Thread Prasun Gera
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. On Wed, Aug 17, 2016 at 10:40 AM, Ciarán Taog wrote: > I was finally able to resolve this issue by performing the following. >

Re: [foreman-users] Re: [Katello] HandlerNotFound: No handler for: {'type': u'erratum'}

2016-09-21 Thread Prasun Gera
I have the same problem. Server and Client are both RHEL 7. Server is running Katello 3.1. Client's katello-agent and related packages are from the Sat 6.2 client repo. Do they need to be from upstream katello ? Anything else that could go wrong ? On Tue, Sep 13, 2016 at 1:27 PM, Joseph

Re: [foreman-users] Re: [Katello] HandlerNotFound: No handler for: {'type': u'erratum'}

2016-09-21 Thread Prasun Gera
After adding the katello-client repo, it works. It might not be possible or easy, but it would be nice if the the official RHEL client packages can maintain compatibility with Katello. On Thu, Sep 22, 2016 at 12:59 AM, Prasun Gera <prasun.g...@gmail.com> wrote: > I have the same proble

[foreman-users] [Katello 3.1] Client subscription-manager out of sync with server repos, pulp error

2016-09-22 Thread Prasun Gera
I am using Katello 3.1 on a RHEL 7 system to manage RHEL 7 clients. I disabled a RH repository from the main RH subscriptions. However, the client still thinks that it is subscribed to that repo, and it eventually gives a 404 not found error on yum commands. Calling subscription-manger refresh or

Re: [foreman-users] Re: RestClient::SSLCertificateNotVerified after custom cert setup

2016-09-20 Thread Prasun Gera
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

Re: [foreman-users] Re: RestClient::SSLCertificateNotVerified after custom cert setup

2016-09-19 Thread Prasun Gera
Yes, I can confirm that foreman-proxy doesn't start with the same errors. On Mon, Sep 19, 2016 at 1:25 PM, Danny Kimsey 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

Re: [foreman-users] Re: RestClient::SSLCertificateNotVerified after custom cert setup

2016-09-19 Thread Prasun Gera
Hi Danny, 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 <dekim...@gmail.com> wrote: > Prasun Gera, I was working with