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.

Description of problem:
whenever we create an activation key, something sets the auto-attach to null.
this is visible in audits:
there are 2 audit records created every time:
1st, which reflects the create action (showing auto-attach being pre-set to true) and the 2ndone, which reports an UPDATE action, which sets the true back to N/A.

Visiting the AK page shows null value for the auto-attach. after we change it to either true to false, it's no longer unset.

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

Steps to Reproduce:
1. create AK with minimum parameters
2. check the AK->subscriptions tab for the auto-attach value
3. check audit records and find 2 of them (create and update).


Additional info:
this is a regression since 6.6

Created redmine issue https://projects.theforeman.org/issues/28676 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28676 has been resolved.

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-2020:1454