RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Running virt-who with "-o -d" options and send the report to stage candlepin2.0, sometimes it will show:
01:11:13 2017-10-15 21:10:52,209 [virtwho.destination_65811457063633981 DEBUG] MainProcess(12857):Thread-3 @subscriptionmanager.py:check_report_state:247 - Job hypervisor_update_ca1d909a-4522-46d5-a502-a374a8886d8a not finished

After each 3600s interval, check_report_state() still feedback WAITING state and the job is always not finished, so virt-who will hang up.

It's difficult to reproduce, but it's really exist, especially when running virt-who in our CI framework, because there are two or more virt-who services running at the same time, maybe there is a blocking when sending all the reports to stage candlepin 

The question is why check_report_state() function always return "WAITING" state? is it a candlepin issue? 

Thanks.

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

As the above described behavior is working as designed (even if not as desired), I'm converting this to an RFE.

The RFE from this will be to add a timeout to job status polling in oneshot mode.
Once virt-who has not seen any change in state of the job for the duration of the timeout, it should cancel the job, and exit (outputting a message to the user that the job was not completed successfully).

One shot no longer waits for status. Closed.