Well this seems not good... I ended up just pointing it back to the DB on
the other server, but it looks like there are other issues...
Specifically, when a repo sync runs:
Dec 28 14:02:31 [redacted] pulp[5543]: pulp.server.event.http:ERROR:
Received HTTP 500 from HTTP notifier to https:
//[red
I also think this is related to the overall problem:
2016-12-28 14:14:37 f101b581 [app] [I] Processing by Katello::Api::Rhsm::
CandlepinProxiesController#upload_package_profile as JSON
2016-12-28 14:14:37 f101b581 [app] [I] Parameters: {"_json"=>"[FILTERED]",
"id"=>"432d04cc-d045-4b7f-9c92-2b4
On 12/28/2016 02:26 PM, nhan...@kayak.com wrote:
> I also think this is related to the overall problem:
>
>
> 2016-12-28 14:14:37 f101b581 [app] [I] Processing by Katello::Api::Rhsm::
> CandlepinProxiesController#upload_package_profile as JSON
> 2016-12-28 14:14:37 f101b581 [app] [I] Paramete
I was able to nail down what I believe was causing this last week with the
help of someone in the irc channel.
Unbeknownst to me, the pulp.conf for Apache was not written correctly, so
api calls for pulp requests were being passed to foreman directly instead
of pulp. I had to rerun the upgrade and
