Bug 1847464

Summary: ForemanInventoryUpload::Async::UploadReportJob fails with NoMethodError: undefined method `[]' for nil:NilClass
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: RH Cloud - InventoryAssignee: Shimon Shtein <sshtein>
Status: CLOSED DUPLICATE QA Contact: Mirek Długosz <mzalewsk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-17 08:51:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
traceback.log none

Description Lukáš Hellebrandt 2020-06-16 12:38:37 UTC
Created attachment 1697605 [details]
traceback.log

Description of problem:
ForemanInventoryUpload::Async::QueueForUploadJob task (action Dynflow::ActiveJob::QueueAdapters::JobWrapper) failed with the following error after just installing Satellite and not touching anything Inventory related:

NoMethodError: undefined method `[]' for nil:NilClass

Traceback attached

Version-Release number of selected component (if applicable):
Sat 6.8 snap 4.0

How reproducible:
Deterministic

Steps to Reproduce:
1. Just install Satellite and wait
2. Monitoring -> Tasks
3. Filter for tasks with the result of warning

Actual results:
Traceback, task status Warning

Expected results:
No traceback, task status Success

Comment 1 Mirek Długosz 2020-06-16 14:40:59 UTC
Isn't that duplicate of Bug #1842903?

As far as I was able to tell, this happens only for reports for organizations without manifest. Which is probably expected, since there will be no account to assign report to.

Comment 2 Lukáš Hellebrandt 2020-06-17 08:51:11 UTC
Yes, looks like a duplicate indeed.

*** This bug has been marked as a duplicate of bug 1842903 ***