Description of problem:
ran some test involving creating an org + uploading a subscription manifest in a loop and on of the iterations failed at create organization step:
2018-11-24T14:00:55 [W|app|7b49f] Action failed
RuntimeError: resource have no errors
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.9.0/app/controllers/katello/api/v2/organizations_controller.rb:83:in `rescue in create'
[the rest of the traceback is attached as bug.log]
Version-Release number of selected component (if applicable):
Steps to Reproduce:
i just ran the org create + manifest upload in a loop
it was a clean satellite (upgraded from snap4)
Created attachment 1508372 [details]
Created attachment 1508373 [details]
the whole task got stuck in running state, waiting on candlepin:
9: Actions::Candlepin::Environment::Create (running) [ 0.00s / 0.00s ]
however i doubt this actually got dispatched to candlepin.
the candlepin.log only shows the Owner create request (wit response status=200)
and then 2
Request: verb=GET, uri=/candlepin/owners/Fbtyra
requests (with response status=200)
Based on logs this happens in Katello - Candlepin communication. Looking at the trace, most likely Candlepin didn't respond with 200. The error message in production.log seems to be masking the real error message. Roman if you have the reproducer, I could help adjust the code so that we'd see the real error message. Sadly I don't see anything in candlepin logs. Perhaps someone bit deeper knowledge of candlepin would find out more.
There were no errors in candlepin logs at that timestamp. If katello/foreman was specifying the correlation ID or logging the request id that comes back from Candlepin we could match the direct request.
Without a reproducer I have no way to investigate further.
Without additional information we cannot make progress on this issue.
Closing as insufficient information as it has been waiting on needinfo for 2 months.