Hide Forgot
Description of problem: I received a 500 error when trying to promote a changeset with four errata in it. Version-Release number of selected component (if applicable): katello-0.1.238-4.el6.noarch How reproducible: Not sure. Steps to Reproduce: 1. Create a new changeset. 2. Add Errata 3. Review the changeset 4. Promote the changeset Actual results: 'delayed_job host:katello.atl.salab.redhat.com pid:1964', "locked_at" = '2012-0 2-23 01:19:56.566617', "last_error" = '{Pulp::Package: 500 Internal Server Error <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>500 Internal Server Error</title> </head><body> <h1>Internal Server Error</h1> <p>The server encountered an internal error or misconfiguration and was unable to complete your request.</p> <p>Please contact the server administrator, root@localhost and inform them of the time the error occurred, and anything you might have done that may have caused the error.</p> <p>More information about this error may be available in the server error log.</p> <hr> <address>Apache/2.2.15 (Red Hat) Server at katello.atl.salab.redhat.com Port 443</address> </body></html> (POST /pulp/api/services/dependencies/) Expected results: Changeset is promoted. Additional info: Let me know which logs to attach to the bug.
Please attach /var/log/pulp/pulp.log - devs may want other logs but that one should contain the root cause.
@Michael - The best would be to use katello-debug script, creates a tarball with extensive information for us.
Unable to reproduce, works for me. Can you give us the katello-debug output please? Would be also interesting to reproduce it on the newer puddle. ^^
Putting back the QA contact.
Created attachment 565322 [details] katello-debug output
There is/was an issue with the system. PostgreSQL is/was not running for some time: PGError: no connection to the server also Pulp is not working or is down. It is also reporting: 401 Unauthorized "Invalid OAuth Credentials" while your oauth configuration is correct and installation log is clean. We had some Elastic Search mis-configuration in the build you are using, it was eating all the memory taking other processes down. Could be the cause. I would try to restart everything: service postgresql restart service pulp-server restart service tomcat6 restart service katello-jobs restart service katello restart I would suggest to close if restarting does not help. There is nothing I can focus on. The system is broken for some reason, I am not able to reproduce.
I am unable to repro using the following steps: Steps to Reproduce: 1. Create a new changeset. 2. Add Errata 3. Review the changeset 4. Promote the changeset Michael, please provide me more info about this one. What is the trick to see the error in this case?
Closing, feel free to reopen. Thanks.