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 1582221

Summary: Error when changing or refreshing manifest
Product: Red Hat Satellite Reporter: Perry Gagne <pgagne>
Component: Subscription ManagementAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED ERRATA QA Contact: Perry Gagne <pgagne>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: avroy, cduryee, fadamo, fgarciad, inecas, jhutar, jomitsch, kkohli, kmishra, ktordeur, pcreech, pmoravec, sadas, stbenjam, suarora, vwariyal
Target Milestone: 6.4.0Keywords: PrioBumpQA, Regression, Reopened, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.rc1-0.1.rc1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-02 18:11:22 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 Perry Gagne 2018-05-24 15:02:37 UTC
Created attachment 1441078 [details]
foreman debug

Description of problem: Whenever I try to update 


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


How reproducible: Always.


Steps to Reproduce:
1. Upload a manifest
2. Attach some content hosts
3. Attempt to refresh manifest. 

Actual results: Error:
```
Error refreshing manifest. Validation failed: Hostgroups expecting hostgroups used by hosts or inherited (check mismatches report)., Domains expecting domains used by hosts or inherited (check mismatches report)., Subnets expecting subnets used by hosts or inherited (check mismatches report)., Compute resources expecting compute resources used by hosts or inherited (check mismatches report)., ApplicationRecord|Capsules expecting capsules used by hosts or inherited (check mismatches report)., Ptables expecting ptables used by hosts or inherited (check mismatches report).
```


Expected results: Refresh success


Additional info:
Talked to jsherril about this and we looked into this. He found when the update is happening the  User context is nil.

Comment 3 Stephen Benjamin 2018-05-29 18:16:57 UTC
Created redmine issue http://projects.theforeman.org/issues/23733 from this bug

Comment 4 Satellite Program 2018-05-29 20:04:41 UTC
Upstream bug assigned to stbenjam

Comment 5 Satellite Program 2018-05-29 20:04:44 UTC
Upstream bug assigned to stbenjam

Comment 6 Satellite Program 2018-05-31 14:04:35 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23733 has been resolved.

Comment 7 Perry Gagne 2018-06-19 15:18:24 UTC
Verified fix in sat 6.4.0 snap 8. Manifests refresh and changes when content hosts are attached are now successful.

Comment 8 Bryan Kearney 2018-10-16 19:16:26 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/RHSA-2018:2927

Comment 14 Satellite Program 2018-12-06 21:03:36 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23733 has been resolved.

Comment 19 Chris Duryee 2019-01-02 18:11:22 UTC
This BZ fix was shipped in https://access.redhat.com/errata/RHSA-2018:2927, please leave it as closed.

If the issue persists and the errata is already applied to Satellite, please use https://bugzilla.redhat.com/show_bug.cgi?id=1663021.