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 1684707

Summary: Regenerate applicability fails when there is a missing repo
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.5CC: bmbouter, daviddavis, dkliban, egolov, ggainey, ipanova, mmccune, rchan, ttereshc
Target Milestone: 6.4.3Keywords: FieldEngineering, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pulp-2.16.4.2-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1671577 Environment:
Last Closed: 2019-04-29 18:15:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 pulp-infra@redhat.com 2019-03-08 20:01:55 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 2 pulp-infra@redhat.com 2019-03-08 20:01:56 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 3 pulp-infra@redhat.com 2019-03-20 09:31:51 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 5 pulp-infra@redhat.com 2019-04-02 21:01:36 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 6 jcallaha 2019-04-09 15:17:37 UTC
Verified in Satellite 6.4.3 Snap 1

Steps:
Add content to the Satellite
Sync and move it through the content management process
Register a host and align the content to it
Install katello-agent or katello-host-tools, to allow for applicability calculations
Run the mongo shell
Find a repo that is attached to the host
Remove it
Run the reproducer command in foreman-rake console

Results:
irb(main):001:0> ForemanTasks.sync_task(Actions::Katello::Host::GenerateApplicability, Host.all)
=> #<ForemanTasks::Task::DynflowTask id: "24ffe3b4-60a4-47f0-934c-876567f0e618", type: "ForemanTasks::Task::DynflowTask", label: "Actions::Katello::Host::GenerateApplicability", started_at: "2019-04-09 15:16:32", ended_at: "2019-04-09 15:16:33", state: "stopped", result: "success", external_id: "babe68f3-8d43-4578-93f7-cd92494c2f90", parent_task_id: nil, start_at: "2019-04-09 15:16:32", start_before: nil, action: "Generate applicability {\"services_checked\"=>[\"pulp...">
irb(main):002:0>

Comment 8 errata-xmlrpc 2019-04-29 18:15:37 UTC
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, 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/RHBA-2019:0903