Bug 1166889 – As a user, I should be able to set auto attach flag on an activation key when I create it

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1166889 - As a user, I should be able to set auto attach flag on an activation key when I create it

Summary:	As a user, I should be able to set auto attach flag on an activation key when...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	Content Management (Show other bugs)
Sub Component:
Version:	6.0.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium (vote)
Target Milestone:	Unspecified
Target Release:	Unused
Assigned To:	Christine Fouant
QA Contact:	jcallaha
Docs Contact:

URL:	http://projects.theforeman.org/issues...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-21 16:07 EST by Justin Sherrill
Modified:	2017-02-23 15:46 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-08-12 01:19:48 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	8480	None	None	None	2016-04-22 11:47 EDT
Red Hat Product Errata	RHSA-2015:1592	normal	SHIPPED_LIVE	Important: Red Hat Satellite 6.1.1 on RHEL 6	2015-08-12 05:04:35 EDT

Groups: None (edit)

Description Justin Sherrill 2014-11-21 16:07:34 EST

The new feature to set an auto-attach flag on an activation key should be an option upon creation.  Currently, you must update a key if you want to set the auto-attach flag.

Comment 1 Justin Sherrill 2014-11-21 16:07:35 EST

Created from redmine issue http://projects.theforeman.org/issues/8480

Comment 3 Bryan Kearney 2014-11-21 18:05:07 EST

Upstream bug assigned to cfouant@redhat.com

Comment 4 Bryan Kearney 2014-12-11 16:04:49 EST

Moving to POST since upstream bug http://projects.theforeman.org/issues/8480 has been closed
-------------
Christine Fouant
Applied in changeset commit:katello|9b12978171daf71e3df53c635cb0d992da5616f2.

Comment 5 jcallaha 2015-01-08 14:35:51 EST

*** This bug is verified in upstream.  This fix should eventually land in future downstream builds ***

Version Tested:
RHEL 66/7

ruby193-rubygem-katello-2.2.0-1.201501060052git1534a1f.el7.noarch
pulp-katello-0.3-3.el7.noarch
katello-certs-tools-2.0.1-1.el7.noarch
rubygem-hammer_cli_katello-0.0.7-1.201501060107git61a6905.git.0.0143db0.el7.noarch
katello-repos-2.1.1-1.el7.noarch
katello-2.1.0-1.201411061509gitb0b8f43.el7.noarch
katello-server-ca-1.0-1.noarch
katello-installer-2.2.0-1.201412192027git113612b.el7.noarch
katello-default-ca-1.0-1.noarch
katello-installer-base-2.2.0-1.201412192027git113612b.el7.noarch

Comment 6 Bryan Kearney 2015-08-11 09:19:57 EDT

This bug is slated to be released with Satellite 6.1.

Comment 7 errata-xmlrpc 2015-08-12 01:19:48 EDT

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-2015:1592

Note You need to log in before you can comment on or make changes to this bug.