Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1205378

Summary:	Subscription Indexing Issue When Deleting Manifest
Product:	Red Hat Satellite	Reporter:	Devan Goodwin <dgoodwin>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
WebUI sub component:	Katello	QA Contact:	Tazim Kolhar <tkolhar>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	unspecified	CC:	bbuckingham, bkearney, bthurber, cwelton, jsherril, tkolhar
Version:	6.1.0	Keywords:	Triaged
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/9899
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 13:56:24 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:

Description Devan Goodwin 2015-03-24 19:30:06 UTC

Description of problem:

After deleting a manifest, several subscriptions remained in Content > Red Hat Subscriptions.

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

6.1.0 Snap 7 Compose 3

How reproducible:

Seems fairly easy to hit.

Steps to Reproduce:
1. Import the attached manifest. 8 pools are visible in the web UI, 11 are actually in the Candlepin db. (suspect this is unmapped guest pools being hidden)

2. Register a virt guest and consume a subscription. In my case I used one of the temporary unmapped guest subscriptions.

3. Delete the manifest.

4. Navigate to Content > Red Hat Subscriptions

Actual results:

In my case there were 4 of the 11 original pools remaining, however Candlepin has no pools in it's database.

Expected results:

All pools gone.

Additional info:

I believe this data is originating from Katello's data index, which is recalculated when pool events are received.

In this case I can confirm that 11 pool deleted events were sent by candlepin, and I can see that all 11 arrived in gutterball, so presumably they made it to katello as well.

Running 'foreman-rake katello:reindex' corrects the issue.

I also have a similar case reporting that entitlement counts are wrong after entitlements are deleted, which I am very suspicious is related:

https://bugzilla.redhat.com/show_bug.cgi?id=1202896

Feels like there may be some kind of issue in the event processing code? Perhaps when multiple events are received at once, could multiple index attempts be trampling each other?

In testing I think I've also seen the counts not reflecting entitlements on systems, just showing me 0 for all pools, even though the guest was consuming a physical entitlement (which wouldn't be hidden). I checked and CPU was quiet so it doesn't appear indexing is running... Running reindex again fixed this issue.

Attempted to delete the manifest a second time, and this time all 8 pools remain visible in the web UI, almost seems like *no* events are moving now. I can still confirm they are making it to qpid and being delivered to gutterball.

Comment 2 RHEL Program Management 2015-03-24 19:33:20 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 4 Justin Sherrill 2015-03-25 18:39:39 UTC

Created redmine issue http://projects.theforeman.org/issues/9899 from this bug

Comment 5 Bryan Kearney 2015-03-26 20:06:04 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/9899 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|7ddbb554891bc89ba39cd29d6c12c223857483f3.

Comment 7 Tazim Kolhar 2015-04-29 09:58:12 UTC

VERIFIED:

# rpm -qa | grep foreman
foreman-proxy-1.7.2.4-1.el7sat.noarch
dhcp201-110.englab.pnq.redhat.com-foreman-client-1.0-1.noarch
dhcp201-110.englab.pnq.redhat.com-foreman-proxy-1.0-2.noarch
foreman-1.7.2.17-1.el7sat.noarch
ruby193-rubygem-foreman_discovery-2.0.0.9-1.el7sat.noarch
foreman-libvirt-1.7.2.17-1.el7sat.noarch
ruby193-rubygem-foreman_bootdisk-4.0.2.10-1.el7sat.noarch
foreman-postgresql-1.7.2.17-1.el7sat.noarch
foreman-vmware-1.7.2.17-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.7-1.el7sat.noarch
ruby193-rubygem-foreman_docker-1.2.0.9-1.el7sat.noarch
ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch
ruby193-rubygem-foreman-tasks-0.6.12.3-1.el7sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el7sat.noarch
foreman-compute-1.7.2.17-1.el7sat.noarch
foreman-ovirt-1.7.2.17-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el7sat.noarch
foreman-selinux-1.7.2.13-1.el7sat.noarch
puppet-foreman_scap_client-0.3.3-7.el7sat.noarch
foreman-gce-1.7.2.17-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.9-1.el7sat.noarch
foreman-debug-1.7.2.17-1.el7sat.noarch
dhcp201-110.englab.pnq.redhat.com-foreman-proxy-client-1.0-1.noarch
ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch
ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch

1. Import the attached manifest.
2. Register a content host and consume a subscription. In my case I used one of the temporary unmapped guest subscriptions.
3. Delete the manifest.
4. Navigate to Content > Red Hat Subscriptions

the manifest deleted succesfully

Comment 8 Bryan Kearney 2015-08-11 13:30:12 UTC

This bug is slated to be released with Satellite 6.1.

Comment 9 Bryan Kearney 2015-08-12 13:56:24 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.