Hide Forgot
Description of problem: Some error pages, such as sql errors, etc. still point to foreman upstream tracking. Version-Release number of selected component (if applicable): Satellite-6.0.4-RHEL-6-20140806.0 How reproducible: Steps to Reproduce: 1. Do something that can cause a sql error. Right now, this can be achieved with bug #1117554 2. View results 3. Actual results: "If you feel this is an error with Foreman itself, please open a new issue with Foreman ticketing system, You would probably need to attach the Full trace and relevant log entries." Expected results: Should not be pointing folks to upstream trackers, etc. Additional info:
*** Bug 1138793 has been marked as a duplicate of this bug. ***
hi , please provide verification steps thanks
Hi, Any exception should display you the message, as long as the environment is set to production. locally I have run "RAILS_ENV=production rails s", got the system running, and then I have turned off the database service to generate an exception. It can be a bit too drastic... Shimon.
FAILEDQA: # rpm -qa | grep foreman foreman-libvirt-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-postgresql-1.7.2.17-1.el6_6sat.noarch foreman-debug-1.7.2.17-1.el6_6sat.noarch foreman-1.7.2.17-1.el6_6sat.noarch foreman-ovirt-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.3-1.el6_6sat.noarch foreman-proxy-1.7.2.4-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-selinux-1.7.2.13-1.el6_6sat.noarch rubygem-hammer_cli_foreman-0.1.4.9-1.el6_6sat.noarch foreman-compute-1.7.2.17-1.el6_6sat.noarch foreman-vmware-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch ruby193-rubygem-foreman_docker-1.2.0.9-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el6_6sat.noarch foreman-gce-1.7.2.17-1.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.9-1.el6_6sat.noarch # echo $RAILS_ENV production rails s # service postgresql stop Stopping postgresql service: [ OK ] # wget https://qe-sat6-rhel66.usersys.redhat.com/users/login --2015-04-27 05:14:56-- https://qe-sat6-rhel66.usersys.redhat.com/users/login Resolving qe-sat6-rhel66.usersys.redhat.com... 127.0.0.1, 10.8.30.151 Connecting to qe-sat6-rhel66.usersys.redhat.com|127.0.0.1|:443... connected. HTTP request sent, awaiting response... 500 Internal Server Error 2015-04-27 05:14:56 ERROR 500: Internal Server Error.
Found a way to reproduce the error: Spin up a capsule instance with puppet master feature Register it in Foreman(Infrastructure -> Capsules -> new) Go to Configure -> puppet classes shut down the capsule Click on Import and select the capsule you have shut down. This should raise an error: Oops, we're sorry but something went wrong × Warning! ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([SocketError]: getaddrinfo: Name or service not known) for proxy http://XXXXXXXXX:8000/puppet
since we cannot consume content capsule server cannot be setup there bz filed for same reason : id : 1217828 once that is fixed i will restest it
VERIFIED: # rpm -qa | grep foreman ruby193-rubygem-foreman_docker-1.2.0.11-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.11-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch foreman-1.7.2.19-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.13-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch foreman-libvirt-1.7.2.19-1.el7sat.noarch foreman-postgresql-1.7.2.19-1.el7sat.noarch ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-debug-1.7.2.19-1.el7sat.noarch foreman-compute-1.7.2.19-1.el7sat.noarch foreman-vmware-1.7.2.19-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch foreman-ovirt-1.7.2.19-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.5-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.9-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-client-1.0-1.noarch ibm-hs22-05.rhts.eng.brq.redhat.com-foreman-proxy-1.0-2.noarch foreman-gce-1.7.2.19-1.el7sat.noarch steps: Spin up a capsule instance with puppet master feature Register it in Foreman(Infrastructure -> Capsules -> new) Go to Configure -> puppet classes shut down the capsule Click on Import and select the capsule you have shut down. This should raise an error: Oops, we're sorry but something went wrong × Warning! ERF12-2749 [ProxyAPI::ProxyException]: Unable to get environments from Puppet ([RestClient::RequestTimeout]: Request Timeout) for proxy https://ibm-x3650m4-02-vm-04.lab.eng.bos.redhat.com:9090/puppet screenshot attached
Created attachment 1024183 [details] capsule shut down error
*** Bug 1227994 has been marked as a duplicate of this bug. ***
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.