Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 1667545 - Multiple logins for single organization in virt-who causes reporting errors
Summary: Multiple logins for single organization in virt-who causes reporting errors
Keywords:
Status: CLOSED DUPLICATE of bug 1637042
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscriptions - virt-who
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Released
Assignee: satellite6-bugs
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-18 18:52 UTC by William Poteat
Modified: 2023-03-24 14:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-30 20:01:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
warning tasks (162.76 KB, image/png)
2019-01-28 16:07 UTC, Jonathon Turel 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3822222 0 None None None 2019-01-22 03:53:50 UTC

Description William Poteat 2019-01-18 18:52:18 UTC 
Description of problem:

Reporting host/guest relationships in virt-who for a single organization using separate log-ins creates an error condition


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

https://bugzilla.redhat.com/show_bug.cgi?id=1603706#c28

Actual results:

See link

Expected results:

Correct reporting

Additional info:
Comment 8 Jonathon Turel 2019-01-22 19:40:19 UTC 
Hey Waldirio, 

I'm looking for some more information that will ensure I'm addressing the issue properly from the Katello side. When I look at the related code I see that there is a task being run called "Actions::Candlepin::AsyncHypervisors" which polls Candlepin directly until a particular task is completed which in turn takes the response and calls ::Actions::Katello::Host::Hypervisors.parse_hypervisors where the stack trace arises from.

I would like to see the response from Candlepin and I don't think the result will be shown in the task logs. I think you can get the response from Candlepin in your reproducer environment this way:

1) Look at the Actions::Candlepin::AsyncHypervisors action being run by the hypervisor checkin
It should have an input with the candlepin task ID

2) Given $TASK_ID from (1) you can use `foreman-rake console` to run the following: ::Katello::Resources::Candlepin::Job.get($TASK_ID, result_data: true)

Knowing what is inside there will be a great help - please share it with me if you can.
Comment 11 Jonathon Turel 2019-01-24 16:39:07 UTC 
Hi Waldirio - unfortunately the response data you've shown me is totally acceptable and won't reproduce the error. Can you put the machines back into the erroring state so I can investigate further? Thank you
Comment 13 Jonathon Turel 2019-01-28 16:07:00 UTC 
Created attachment 1524283 [details]
warning tasks
Comment 14 Jonathon Turel 2019-01-28 16:09:11 UTC 
Hi again,

The 'warning' tasks are old - I need to see some new ones coming in so that I can monitor the Candlepin responses in real-time because I suspect they are changing by the time we can see them (as above). Can you change the configuration so that the tasks are warning once again?
Comment 16 Jonathon Turel 2019-01-28 19:52:47 UTC 
I was able to create some new tasks and upon investigating the Candlepin response I believe that this is a duplicate of another bug: https://bugzilla.redhat.com/show_bug.cgi?id=1637042

Some of the tasks were in WAITING state and as a result we continue with the action and the exception is raised. #1637042 addresses the issue. I made the change locally on your reproducer and I see that the tasks are now successful.

You can see what I did:

cd /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.7.0.41
git diff

It looks like #1637042 is marked for a 6.4.z so I think this can be closed as a duplicate. Let me know if you agree Waldirio.
Comment 19 Barnaby Court 2019-01-30 20:01:11 UTC 
Closing as dupe of 1637042 per comment 16

*** This bug has been marked as a duplicate of bug 1637042 ***
Note You need to log in before you can comment on or make changes to this bug.