Bug 1964041

Created attachment 1786479 [details]
Traceback bz_1964041

The interesting this is: when you go to the reproducer machine, and click "generate", it generates a report just fine and as a bonus you can't find the old error nowhere in the logs (all tasks related to inventory upload are either successful or failed for completely different reasons).

I am kinda sure this is not a delivery/rel-eng issue, but also not sure what else it could be.

Best guess would be that the job runs at a time where the bundle is "unclean", either because we're currently installing or upgrading a package?
But I have no idea why the job should run at all at that moment.

I see that although the message is reproducible, it does not interfere with the generation process.
I think it has something to do with the context in which the task runs.

As for the "unclean" bundle, is there a chance that the process has loaded some older versions and was upgraded while running?

This is a fresh install, so I'm going with "no" (but that doesn't make the explanation any easier)

@sshtein Hello, sure! I have asked @Chris to confirm if there is any issue while loading foreman_azure_rm based on the latest changes.

@Aditi

Will look today and see what is going on

I can't reach the box anymore in the private comment, i will test with the latest 6.10 snap and report back

Sorry for the delay, had some things come up.

I tested this with snap 14

I do not see any trace backs following the steps provided:

'ErbParser' is ignored.

'RubyParser' is ignored.

I, [2021-08-19T14:51:41.482270 #29860] INFO -- : Started generating hosts report in /tmp/d20210819-29860-wqzsxw

I, [2021-08-19T14:51:41.499772 #29860] INFO -- : Report generation finished

I, [2021-08-19T14:51:41.499806 #29860] INFO -- : Archiving generated report

I, [2021-08-19T14:51:41.508282 #29860] INFO -- : tar: ./

./metadata.json

I, [2021-08-19T14:51:41.508361 #29860] INFO -- : Report archived successfully

Successfully generated /var/lib/foreman/red_hat_inventory/generated_reports/report_for_1.tar.xz for organization id 1

You can try yourself on the satellite I have running. I will post the info in a separate comment as private.

Verified

Verified with:
- Satellite 6.10.0 snap 20
- tfm-rubygem-foreman_rh_cloud-4.0.26-1.el7sat.noarch

Test steps:
1. Install Satellite 6.10.0 snap 20
2. Go to Configure > Inventory upload
3. Click on Default Organization tab

Observation:
- No traceback



'ErbParser' is ignored.

'RubyParser' is ignored.

I, [2021-09-29T06:08:23.756842 #34656] INFO -- : Started generating hosts report in /tmp/d20210929-34656-es4d5p

I, [2021-09-29T06:08:23.774104 #34656] INFO -- : Adding slice 6e1fe781-25cd-444d-be8b-f90fd8f554f1

I, [2021-09-29T06:08:24.858681 #34656] INFO -- : slice 6e1fe781-25cd-444d-be8b-f90fd8f554f1 was created with 1 hosts

I, [2021-09-29T06:08:24.858815 #34656] INFO -- : Report generation finished

I, [2021-09-29T06:08:24.858833 #34656] INFO -- : Archiving generated report

I, [2021-09-29T06:08:24.889784 #34656] INFO -- : tar: ./

./metadata.json

./6e1fe781-25cd-444d-be8b-f90fd8f554f1.json

I, [2021-09-29T06:08:24.890152 #34656] INFO -- : Report archived successfully

Successfully generated /var/lib/foreman/red_hat_inventory/generated_reports/report_for_1.tar.xz for organization id 1

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.10 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:4702