Description of problem:
While publishing a content view with erratum filter (by date) I had a proxy failure which led to the following error to be displayed in the production log:
==> /var/log/foreman/production.log <==
2015-03-09 09:00:42 [E] ERF12-2749 [ProxyAPI::ProxyException]: No puedo recuperar los entornos para Puppet ([Errno::ECONNREFUSED]: Connection refused - connect(2)) de proxy https://[EDITED]:9090/puppet (ProxyAPI::ProxyException)
The full stacktrace is there but I believe that we want the error to be localized according to the Satellite's default locale (in my case:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. You'd have to perhaps stop foreman-proxy and attempt to publish a content view
The actual task fails but you would get the error already mentioned in /var/log/foreman/production.log in **Spanish**
The error should be localized according to the system's locale.
I am facing a similar issue when trying to publish a content view. Checked on SNAP 14.
ERF12-4115 [ProxyAPI::ProxyException]: Klassen für KT_insights_qNqXuk_Library_new_cv_1605 konnten nicht von Puppet geladen werden ([RestClient::NotAcceptable]: 406 Not Acceptable) für Proxy https://example.com:9090/puppet
Any specific reason for this issue?
*** Bug 1247183 has been marked as a duplicate of this bug. ***
*** Bug 1227715 has been marked as a duplicate of this bug. ***
*** Bug 1273794 has been marked as a duplicate of this bug. ***
Getting this error in a fresh installation of 6.1.7 attempting to publish some content views. Locale is EN/GB and installation is in English, but error is in German:
ERF12-4115 [ProxyAPI::ProxyException]: Klassen für KT_Default_Organization_Library_RHEL7_Rolling_2 konnten nicht von Puppet geladen werden ([RestClient::Forbidden]: 403 Forbidden) für Proxy https://sat.calvinhartwell.com:9090/puppet
Pushed two content views, one with RHEL7 content (Rolling version) and another for Puppet modules (it does not have any modules inside it though).
Note the Trusted hosts section in /etc/foreman-proxy/settings.yml is already correct (with multiple lines of correct hostname) and I've tried restarting all services (katelloo-service restart) but the issue still exists.
Reset docs contact <> daobrien
+1 Same problem. Any idea when this will be fixed?
Hi Bryan, Is the issue tested in sat6.2? I have a new case (01700858, sat6.1) visiting similar error.
Amit, we have not verified this as in or out on 6.2.
I have had this issue many times with 6.0 and 6.1, but since i run 6.2.x i have not seen this issue anymore. And i still use almost the same process to add and publish content in Sat6.x
Still seeing this in 6.1.9, even after the workaround involving the update to the :trusted_hosts: field in /etc/foreman-proxy/settings.yml.
I am having trouble reproducing this in 6.2.7, however.
Internal engineers and a trusted customer can not recreate on 6.2. I am going to close this as resolved in 6.2. If you are still seeing this on 6.2 or later, please feel free to re-open with additional information.