Bug 1784454

Summary:	Auto attach option is being set to null after activation key is created
Product:	Red Hat Satellite	Reporter:	Roman Plevka <rplevka>
Component:	Activation Keys	Assignee:	Jonathon Turel <jturel>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	jturel, pcreech
Target Milestone:	6.7.0	Keywords:	Regression, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.14.0.5-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:28:08 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 Roman Plevka 2019-12-17 13:38:19 UTC

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

Comment 4 Jonathon Turel 2020-01-07 21:50:22 UTC

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

Comment 6 Bryan Kearney 2020-01-10 21:02:05 UTC

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

Comment 12 errata-xmlrpc 2020-04-14 13:28:08 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-2020:1454