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 1435344 - [RFE] Ability to disable auto-attach [auto-heal] per Satellite organization
Summary: [RFE] Ability to disable auto-attach [auto-heal] per Satellite organization
Keywords:
Status: CLOSED DUPLICATE of bug 1549253
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.2.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
: 1324597 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 14:58 UTC by Kathryn Dixon
Modified: 2023-10-06 17:36 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-10 14:19:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 3293541 0 None None None 2017-12-19 20:31:00 UTC
Red Hat Knowledge Base (Solution) 3293541 0 Supportability None How to disable auto-attach [auto-heal] per satellite organization? 2019-03-09 01:57:08 UTC

Description Kathryn Dixon 2017-03-23 14:58:31 UTC 
Description of problem:

Often times we find ourselves needing to fix subscription issues in Satellite 6. The situations can look like...

"my systems are auto-attaching the wrong subs" 

"can't find subscription x" 

"systems keep grabbing the wrong subscription"

To resolve this easier, it would be nice if we could use hammer to disable auto-attach for the entire organization, then fix the subscriptions, then turn it back on ( or remain off depending on the customers need).

This will also help at times of renewel when after you import the new subscriptions systems get excited and want to grab what its think is correct which is not always 100% right. 

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


How reproducible: 100%


Steps to Reproduce:
1. import subscription manifest into satellite
2. systems will start healing themselves with what they think are relevant subscriptions

Actual results: can not prevent systems from healing with relevant subscriptions on an org basis, can only do this per system and its time consuming.


Expected results: can use hammer to turn off auto attach for the entire organization


Additional info:
Comment 1 Barnaby Court 2017-03-23 20:34:09 UTC 
This is already available in candlepin-0.9.54.11-1. I'm moving this to the Subscription Management component so that hammer can be updated with the appropriate command to enable/disable. 

To turn this on/off in candlepin update the owner resource to set autobindDisabled to true/false.
Comment 3 Rich Jerrido 2017-10-08 12:05:14 UTC 
*** Bug 1324597 has been marked as a duplicate of this bug. ***
Comment 5 sthirugn@redhat.com 2018-06-14 18:43:41 UTC 
This bug is currently in backlog due to other priorities. This may be reviewed in future and aligned to a future release.
Comment 6 Hayley Hudgeons 2019-04-10 14:19:12 UTC 

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