I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can't pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
The only way to see the repositories through a web browser that are served
over HTTPS is via a debug certificate that you can download for a given
organization on the organization page. Can you describe your setup and what
you are seeing on the client? Are there error messages? Does yum repolist
show the HTTPS based repositories?
Eric
···
On Tue, Jul 7, 2015 at 7:58 AM, wrote:
Hi together,
I´m new to Katello and Foreman and am trying to access pulp repo content
from one of my subscribed consumer hosts. But neither is it possible to
access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can
somebody maybe help me on this matter? The content is available through
http but our security policy prohibits access to http content.
> Hi together,
>
> I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
>
> I think there is an ssl issue and I currently can't pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it's an SSL issue? Could we see what's logged when
you try to access the content through the url in your web browser or yum?
I'd recommend 'tail -f'-ing Pulp logs when you try to access this
content and see if the Pulp capsule is being reached at all.
···
On 07/07, Markus.Moj@mc.ingenico.com wrote:
>
> Kind regards,
> Markus
>
> --
> You received this message because you are subscribed to the Google Groups "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
Thanks for your reply. Here is a short description of our setup.
I´ve installed katello with necessary dependencies, configured the http proxy and setup an organizational SSL certificate for the webserver. I´ve also disabled SSLv2 v3 as well as TLSv1 and TLSv1.1.
I have created a repo for centos 7.1 and synced it without any issues. Furthermore I have created a composite content view for centos 7, which will in the future hold more repos, and published this content view. I have also registered a host to test if every things configured correctly and here the problems begin. I´ve install katello-agent registered with puppet and see the host as content host in foreman, I´ve also installed the consumer-ca but when I try to update the system I get the following error.
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Eric D Helms
Gesendet: Dienstag, 7. Juli 2015 14:22
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
Hi Markus,
The only way to see the repositories through a web browser that are served over HTTPS is via a debug certificate that you can download for a given organization on the organization page. Can you describe your setup and what you are seeing on the client? Are there error messages? Does yum repolist show the HTTPS based repositories?
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
···
-----Ursprüngliche Nachricht-----
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Daniel Lobato Garcia
Gesendet: Dienstag, 7. Juli 2015 14:55
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.
Do you see errors in the Apache logs on the server from where it is trying
to connect?
···
On Tue, Jul 7, 2015 at 9:09 AM, wrote:
Hi Daniel,
I don´t see a connect not even a try. But when I lookup curl#35 this is
what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the
error buffer and read the message there as it pinpoints the problem
slightly more. Could be certificates (file formats, paths, permissions),
passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content
from one of my subscribed consumer hosts. But neither is it possible to
access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can
somebody maybe help me on this matter? The content is available through
http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when
you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content
and see if the Pulp capsule is being reached at all.
sorry but I dont see any log entries neither in httpd logs nor in other logs.
The only thing I get now is the following error message with yum
[Errno 14] curl#35 - "Encountered end of file"
And in /var/log/messages I see this entry
[WARNING][Thread-2] qpid.messaging:462 - recoverable error[attempt 580]: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
i.A Markus MOJ
IT-Operations /
System-Administrator HP NonStop Servers - Tandem Computers /
Linux Engenieer /
Ingenico Payment Services GmbH
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Eric D Helms
Gesendet: Dienstag, 7. Juli 2015 15:54
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
Do you see errors in the Apache logs on the server from where it is trying to connect?
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Eric D Helms
Gesendet: Dienstag, 7. Juli 2015 15:54
An: foreman-users@googlegroups.com
Betreff: Re: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
Do you see errors in the Apache logs on the server from where it is trying to connect?
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.
Closing connection 0
curl: (35) Encountered end of file
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Moj, Markus
Gesendet: Mittwoch, 8. Juli 2015 08:23
An: foreman-users@googlegroups.com
Betreff: AW: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
Hi,
I also see the following in the rhsm logs
2015-07-08 08:18:08,066 [DEBUG] yum @connection.py:469 - Making request: GET /rhsm/consumers/fde488f5-fd73-47a9-85b0-08adc3297c06/content_overrides
2015-07-08 08:18:08,191 [DEBUG] yum @connection.py:492 - Response: status=200
2015-07-08 08:18:08,193 [DEBUG] yum @cache.py:272 - Started thread to write cache: /var/lib/rhsm/cache/content_overrides.json
2015-07-08 08:18:08,199 [DEBUG] yum @init.py:85 - Searching for content of type: yum
2015-07-08 08:18:08,221 [DEBUG] yum @cache.py:110 - Wrote cache: /var/lib/rhsm/cache/written_overrides.json
2015-07-08 08:18:08,222 [INFO] yum @repolib.py:270 - repos updated: Repo updates
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.
I don´t see a connect not even a try. But when I lookup curl#35 this is
what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the
error buffer and read the message there as it pinpoints the problem
slightly more. Could be certificates (file formats, paths, permissions),
passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content
from one of my subscribed consumer hosts. But neither is it possible to
access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can
somebody maybe help me on this matter? The content is available through
http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when
you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content
and see if the Pulp capsule is being reached at all.
yes I have set custom server certificates with katello-installer but I can revise it to standard if necessary.
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Eric D Helms
Gesendet: Mittwoch, 8. Juli 2015 13:24
An: foreman-users@googlegroups.com
Betreff: Re: AW: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.
I have disabled all necessary repos as well as the proxy and run katello-install --certs-update-all. After this I was able to contact my repo and receive updates and packages.
Thanks you all for your help.
···
Von: foreman-users@googlegroups.com [mailto:foreman-users@googlegroups.com] Im Auftrag von Moj, Markus
Gesendet: Mittwoch, 8. Juli 2015 13:54
An: foreman-users@googlegroups.com
Betreff: AW: AW: [foreman-users] [Katello 2.2.1] Pulp repository access over https not possible
PGP Bad Signature, Signed: 08.07.2015 at 13:54:18
Hi Eric,
yes I have set custom server certificates with katello-installer but I can revise it to standard if necessary.
I don´t see a connect not even a try. But when I lookup curl#35 this is what I get.
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Therefore I wrote that I looks to me like an SSL error.
I´m new to Katello and Foreman and am trying to access pulp repo content from one of my subscribed consumer hosts. But neither is it possible to access the content through the url in my web browser nor through yum.
I think there is an ssl issue and I currently can’t pinpoint it. Can somebody maybe help me on this matter? The content is available through http but our security policy prohibits access to http content.
What makes you think it’s an SSL issue? Could we see what’s logged when you try to access the content through the url in your web browser or yum?
I’d recommend ‘tail -f’-ing Pulp logs when you try to access this content and see if the Pulp capsule is being reached at all.