RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Description of problem:

We started with subscribe --auto, which became attach --auto. This asks the server to figure out the best entitlements and give them to us.

Then we went to add an autoheal module which controls the server side flag, which indicates if this system should try to heal (essentially running "attach --auto" every 24 hours by default). We can't say heal, so this became auto-attach. 

There's also "register --auto-attach", though this is a register followed by an attach --auto, so what to do here will be determined by sorting out the other two.

This is highly confusing as both of these commands do entirely different things. Need to figure out a way to cover the functionality without describing it exactly the same.

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

subscription-manager-1.8.13-1

*** This bug has been marked as a duplicate of bug 1030001 ***