Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 122546

Summary:	RFE: Set default for Auto Update Errata to yes
Product:	Red Hat Satellite 5	Reporter:	Jack Neely <jjneely>
Component:	Other	Assignee:	Jan Pazdziora (Red Hat) <jpazdziora>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	elliot, msuchy
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-21 12:18:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jack Neely 2004-05-05 17:26:36 UTC

Request for Enhancement:

I would like to set Auto Update Errata to yes as a default value.  

With the amount of RHEL clients I'm dealing with and other IT folks at
NCSU I'd like to set up RHN so that it requires the least effort from
folks that maintain machines around campus.  I would like to change
the default value of Auto Update Errata to yes for newly registered
machines.  

For example, I have computer labs of 100+ linux workstations. 
Machines don't get fixed if they are broken, they just get
reinstalled.  After they re-register they need to pick up updates
automatically without me or another IT person having to locate the
machine in RHN and change its settings.

I'll note here that I see several duplicate bugs about Auto Update
Errata not working.  I can confirm this as well.


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

Comment 3 Miroslav Suchý 2011-01-20 19:59:12 UTC

This is not going happen. Auto Update Errata can be very dangerous for somebody.

Enabling "Auto Update Errata" for bung of system is easy in few click in System Set Manager.
But it is true that you can not set up this value for newly provisioned systems. Neither using Activation key nor in Kickstart.

Comment 4 Miroslav Suchý 2011-01-21 12:18:19 UTC

Marking as duplicate of 247826. It is newer BZ, but has more info.

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